Re: C embedded programming books?


Andreas Schwarz wrote:
Le Chaud Lapin schrieb:
Steve at fivetrees wrote:
- Hardware I/O will again be user-supplied. (Avoid bit-fields; use masks.)

Why?

Because it depends on the compiler how the elements of a bit field are
aligned in memory.

I suspected that this is the reason. Certainly you will agree that
this is hardly an issue if you're already comitted to the idea that you
are doing hardware-based I/O?

-Le Chaud Lapin-

.

Relevant Pages

  • Re: Typedef-ing structs
    ... every time the compiler sees 'edge' it replaces those four ... If you are referring to your own article, ... This assumes that the jogging is being applied to a normal memory. ... There is a good reason, however, to assume that they are very, very, ...
    (comp.lang.c)
  • Re: MALLOC: TYPE NAME EXPECTED
    ... I presume without getting memory overflow or application frozen????? ... Your problems are entirely compiler specific, ... If for some reason you must use this compiler, ... post to it on Borland's server newsgroups.borland.com, ...
    (comp.lang.c)
  • Re: Why does this not work: PChar(@Name[0]) := Pchar(String);
    ... I really couldn't care less how the string is stored in memory. ... Would be nice if the compiler or runtime can figure it out itself. ... Only reason why I had to "tell" the compiler the pchar typecast is precisely ...
    (alt.comp.lang.borland-delphi)
  • Re: question on const
    ... the compiler probably eliminated a fetch from memory by using the ... There's always a good reason to try to know how things really works. ... Now we had discovered that that compiler is broken. ... According to the standard that piece of code ...
    (comp.lang.c)
  • Re: WWDC -- MacBook Pro?
    ... ....but once the program has loaded it into its program memory, ... boundaries, int16 are aligned on 2 byte boundaries, int32 are ... people are always able to come up with the compiler ... Case B, same glass, same ice code water.  ...
    (comp.sys.mac.system)