Re: [liblo] getting reading for 0.28-rc

Thanks Steve!

Is there something we can use to test the ABI? I think I've heard you mentioning a tool for this.

I'm sorry I can't give you a definite answer about the implications of redefining the opaque pointers. I have always compiled liblo sources right into my application and never bothered using it as a dynamic library.

Cam

> On 27 nov. 2013, at 14:20, Stephen Sinclair <rad...@gm...> wrote:
> 
>> On Wed, Nov 27, 2013 at 2:05 PM, Stephen Sinclair <rad...@gm...> wrote:
>> There could be ways to fix this using typedef'd structs instead of
>> void pointers or something like that... I'm not sure whether such a
>> change wouldn't have pretty bad implications for the API though.  I'll
>> look into it.
> 
> I'll just note that I'm experimenting with changing the typedefs in
> lo_types.h from void* to struct{}*, and it's exposing a bunch more
> similar mistakes.
> 
> I've always found the argument ordering in lo_send_message_from() to
> be confusing. :(
> 
> For some reason I always expect these functions to be called
> lo_message_send() and lo_message_send_from(), and take a lo_message as
> first argument.. I get it wrong almost every time.  We should
> definitely try to get the compiler to flag these kind of mistakes, (if
> it's possible without breaking everyone's code.)
> 
> 
> Steve
> 
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT 
> organizations don't have a clear picture of how application performance 
> affects their revenue. With AppDynamics, you get 100% visibility into your 
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel