Re: [boost] Re: sockets2 GenVoca layering for address

From: Iain.Hanson_at_[hidden]
Date: 2002-02-27 10:11:19

Author:  dmoore (dmoore_at_[hidden]) at unix,mime
Date:    27/02/02 14:42

     
>Fair enough, and once I thought about it, this is almost always 
>known as compile time.  Might complicate things like assignment 
>operators or comparisons, but this is worth it to eliminate the 
>common error of missing htons() on a port...

Yes. As far as possible, I would prefer that users do not need to 
concern themselves  with marshalling, except where absolutely 
necessary.
     
     
     
>As for the csocket.h, cinet.h, etc., you'll need one of these for 
>each platform flavor, especially for the older IPv4 stuff....  To 
>pick a specific example, some versions of BSD have an 8 bit length 
>member in the sockaddr_in structure and an 8 bit address_family 
>member, while Winsock and other Unices have a 16 bit address_family 
>and no length member.
     
>I think you *can* reasonably "size" your structures in a common 
>header based on public specifications/standards, but there is no 
>getting around the fact that any platform independent library will 
>need platform specific structure handling code for variations like 
>the one above.

Sigh unfortuneately I see no way around this. Writting my own C 
headers still seems like the simplest way of handling this. A lot 
simpler than including the platform headers with there horrible 
macros.

I think this should be possible in a single set of headers although 
I may need some support from boost::config.

/ikh
     

Visit our website at http://www.ubswarburg.com

This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.