From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Trenton D. Adams" To: "'Grant Edwards'" Cc: "'Jonathan Larmour'" , "'Andrew Lunn'" , "'eCos discussion'" Subject: RE: [ECOS] Network programming for eCos under linux Date: Wed, 08 Aug 2001 08:43:00 -0000 Message-id: <003001c12020$c6da1d70$090110ac@TRENT> References: <20010808103411.B13989@visi.com> X-SW-Source: 2001-08/msg00239.html > > > I've claimed for many years that C, as a systems language, > should provide a way for the user to specify data layout in > memory when it is require for meeting external requirements > such as memory mapped hardware, comm protocols, etc. This > would allow the user to control data layout in a static, > declaritive approach, similar to the way C deals with data > types and scoping: all three would be could declared at > compile-time. > > The C language mavens reply that C _could_ do something like > that, but they prefer to leave it up to the user to shovel > individual bytes around to get them arranged as desired. (That > way it's much more error prone and uses up more CPU cycles!) > They seem to prefer an imperitive approach, where you layout > data at run-time rather than at compile time, even though > everything else about data objects (type, scope) is defined at > compile time. > > I don't understand their reasoning, but there's no way I'm ever > going to convince them to change things now. :) > > > Well apparently Microsoft's compiler doesn't follow the standard then! Oh, that's a big surprise!!!! ;) LMAO. Anyhow, it allows you to specify alignment for compile time. I would have to say that in this case, I agree with Microsoft not following the standard! :)