Hendrik,

> Could be but that really sucks :-(
> You cannot just assign in6addr_loopback, you have to memcpy() it.

Hmm, why?  Isn't struct assignment part of C89?  I suppose we can, to keep 
ancient compilers happy.  Also note that C99 initialization for sockaddr 
structures is "wrong".  Implementations can add their own structure members 
to sockaddr*.  Since C99 style initialization doesn't guarantee that these 
members will be initialized to 0 for automatic variables, you might get 
unexpected behaviour on such platforms.

> Should be already solved by the win32 patchset. From other patch lines, I
> clearly see that you did not use it.

Ah sorry, for some reason I thought this was already integrated into CVS.

> For normal cases, uses inttypes.h instead. One of both is present everywhere
> but stdint.h always includes inttypes.h and the latter actually defines what
> we want.
> Doesn't VC++ have inttypes.h?

VC++ doesn't have inttypes.h or stdint.h.

> Is that worth the effort for a _Debug_ message? Isn't there a WSA function
> that comes close to it and could be used?

Well the debug message is useful, and if you look at my implementation it does 
use a Windows function.

> Seperate patch, then, as it's not related to the other stuff.

You're right, too lazy.

> Yes, see win32 patchset. I already suggested that, too.

> A vcproj file could be generated by meta compilers, e.g. CMake. The latter
> doesn't support cross-compiling, yet, though.

Yes, but that's a fairly serious architectural change.  It does seem worth 
investigating though particularly if we're serious about OpenOBEX becoming 
cross-platform again.

-Denis

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Openobex-users mailing list
[email protected]
http://lists.sourceforge.net/lists/listinfo/openobex-users

Reply via email to