Lpc2000

Hi David,

> I'd second this.  I see nothing in here to stop a compiler from
> moving stuff around to it's hearts content.  You might want
> to look at adding some barrier() statements to the above code
> to prevent that kind of code rearrangement.

I'm not too familiar with GNU (I presume barrier() is GNU).
Whta's a barrier() statement.
Forgive me if I convey dumb or lazy.
I _do_ want to learn, and I don't expect others to do my homework for me.
I have noticed an "inline" statement in Bill's code, I don't even know what
that's
all about.

I used to be a die-hard IAR fan, and in hindsight I find that using IAR
hasn't made me
as good a programmer as I ought to be by now, seems some things are done
"for you",
giving some sort of "false sense of security".
Using other tools is like a cold shower suddenly.

-- Kris