At 01:52 AM 12/23/2004, Mladen Turk wrote: >>That's cool, but the handling of in_addr_t is totally bogus and >>has been for some time. Some platforms declare struct in_addr_t as a typedef >>- but others don't. The crossplatform solution is >>to ignore the typedef and use in_addr_t, but instead, the code >>currently does some crap with uint for win32 and ignores HP/UX >>and a host of other platforms. >>I'll offer a patch in the next 24 hours to handle the in_addr_t >>data gracefully and without a host of compiler emits and build >>failures. No functional changes required :) > >OK.
By the way, I agree the code had no emits. It's easy to eliminate compile emits by (cast)ing them away. Yes - the patch keeps one cast, it's necessary due to the bogus definition of the hostent structure which was stillborn, braindead :) However, the code didn't compile on non-win32/netware platforms with no in_addr_t typedef, so it was still quite non-portable. The patch corrects for all platforms, not just one-off cases. Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
