> > > One reason such things aren't as noticable is because most network > > > protocols put the members in decreasing order of size, in an attempt > > > to satisty the requirements for alignment and such, and inhibit any > > > such compiler-specific :) things. > > > > ? Low level network protocols have no idea about the semantics of > > bytes from higher layers. They won't do any reordering. > The structure members of eg. a TCP packet are laid out such that > compilers won't need to do any padding; /usr/include/netinet/tcp.h.
Yes, but that is a header with a fixed design. This has nothing to do with the actual encapsulated data, which of course the low level protocol does not understand... M -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/, read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
