24 Jun 95 08:29, Paul Edwards wrote to Andrew Clarke:

 AC>> I wrote a small program to report sizeof(EZYMSGHDR).  Borland C++ 
 AC>> 3.1 reported the correct size, 186 bytes; Microsoft QuickC 2.5 
 AC>> reported 188 

 > If you say that 186 is the correct size, then that is because you are 
 > saying that there are 186 CHARACTERS in the structure, and you know 
 > EXACTLY which character is which.  So read a block of 186 characters, 
 > and CONVERT them into the local structure.

Thanks Paul, this makes perfect sense.  The Tobruk source code to deal with
FTN packets is a good demonstration of this.

 AC>> bytes, due to its default of 2-byte structure alignment.  Perhaps it 
 AC>> has something to do with EZYNETADDR being nested inside EZYMSGHDR.  
 AC>> I will investigate when I have some more time, but in my opinion the 
 AC>> behavior of QuickC's default structure aligning is unacceptable, 
 AC>> based on the above structure.

 > No, your code is unacceptable to ISO/IEC 9899:1990.  BFN.  Paul.

Heck, I must be in the wrong echo.  Are you sure this is AUST_C_HERE and
not AUST_ISO_C_HERE? :-)

I suppose it comes under "Platform dependant code".  Does
platform dependancy make code unacceptable to the ISO C standard?  I should
hope the aim of the standard would be to simply point out that it is
platform dependant.  If it was unacceptable then the majority of ANSI/ISO C
compilers would probably refuse to compile it! :-)

andrew

--- Msgedsq/2 3.10