🚀 go-pugleaf

In article <BLUME.95Sep15102347@dynamic.cs.princeton.edu>,
blume@dynamic.cs.princeton.edu (Matthias Blume) writes:
>
> Msg-ID: <BLUME.95Sep15102347@dynamic.cs.princeton.edu>
> References: <4395o4$3mv2@news-s01.ny.us.ibm.net>
> Posted: 15 Sep 1995 14:23:47 GMT
>
> Org.  : Princeton University
>
> In article <43bdus$l2g@nntp.nta.no> ohk@hal.nta.no (Ole-Hjalmar
> Kristensen TF.E/DELAB) writes:
>
>    What worries me is that there does not seem to be a clean way to
> ensure that a
>    record has a specific *physical* layout. If it is to be used for
> systems
>    programming, I think this is an important feature, because there is
> often a need
>    to interface to devices which expect to use a fixed data format.
>
> If you had read the C standard or any of the more popular documents
> describing it then you would know that neither C nor C++ give you such
> a guarantee either.
>
> --
> -Matthias


True enough, but the implementation of RECORD structures should be
documented in the compiler docs for just this purpose. While the
implementation of this is not the same on all platforms (unless it's in
WG-13's papers, and I think it should be) for platform specific code (
device drivers and other OS-type code) it should be alright.

Cheers,

Jan
--
Facts below, opinions above.
The "unfancy" sig...
//       Centurion Services & Wholesale //
//       "Quality from the Start"       //
//       Jan_Walter@mindlink.bc.ca      //
//       Telefax: (604) 279-1800        //