This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: Network programming for eCos under linux
- To: "'Grant Edwards'" <grante at visi dot com>
- Subject: RE: [ECOS] Network programming for eCos under linux
- From: "Trenton D. Adams" <tadams at theone dot dnsalias dot com>
- Date: Wed, 8 Aug 2001 09:42:48 -0600
- Cc: "'Jonathan Larmour'" <jlarmour at redhat dot com>,"'Andrew Lunn'" <andrew dot lunn at ascom dot ch>,"'eCos discussion'" <ecos-discuss at sources dot redhat dot com>
> <soapbox>
>
> 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. :)
>
> </soapbox>
>
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! :)