Re: [liblo] liblo version 0.24pre1

[Dave R. <dro...@co...>]

On Fri, 2007-03-09 at 21:13 +0000, Nicholas J Humfrey wrote:
> Hi,
> 
> Sorry it has been so long since the last release. I have been through  
> the Bug Tracker on SourceForge and fixed most of the problems there:
> 
> 	* Changed lo_blob_new() to take const void* (thanks to Lars Luthman)
> 	* Disable getnameinfo() method of getting hostname, when IPv6 is  
> disabled
> 	* Unlink Unix server socket when it is close (thanks to Dominic Sacré)
> 	* Checks size of unix socket path properly
> 	* Now accepts unix socket format osc.unix://localhost/tmp/mysocket.sock
> 	* Added lo_server_thread_new_with_proto(), as suggested by Dave  
> Robillard
> 	* Applied patch from Aron Stansvik to fix bug with FreeBSD/NetBSD  
> systems
> 	* Removed freeaddrinfo() from resolve_address() error case (thanks  
> to Anthony Green)
> 	* Only call connect() for TCP sessions (thanks to Roger B. Dannenberg)
> 	* Applied lo_address_get_url() patch from Sze'kelyi Szabolcs
> 	* Added lo_server_get_protocol() and lo_address_get_protocol()
> 	* Added tests for lo_address_get_* tests to test tool
> 
> A pre-release of version 0.24 is available here:
> http://www.ecs.soton.ac.uk/~njh/liblo/liblo-0.24pre1.tar.gz
> 
> I have also released a new version of the perl bindings on CPAN:
> http://search.cpan.org/~njh/Net-LibLO-0.06/
> 
> It would be great if I could get some feedback before I make the 0.24  
> release. In particular relating to the bug fixes above, and also  
> confirm that I didn't break binary compatibility.
> 
> 
> Thanks,

Working fine here (havn't tested the TCP stuff though).  No more big
delay on lo_server_new, nice.

A few warnings on 64-bit:

address.c:148: warning: cast from pointer to integer of different size

message.c:413: warning: format '%lld' expects type 'long long int', but
argument 2 has type 'int64_t'

pattern_match.c:220: warning: value computed is not used

testlo.c:180: warning: format '%llX' expects type 'long long unsigned
int', but argument 3 has type 'uint64_t'

Cheers,

-DR-