Hi Richard,

I understand absolutely not your negative posting. It looks, we read not the same article ?

I found it great again and agree in most aspects, e.g.:

"I also strongly suggest that writing C for a micro you haven't mastered in assembly is a bad idea,
since you won't be able to spot the inevitable compiler bugs and write efficient code."

or:

"Reliability: New families (and even new parts in established families) can have problems, usually in hardware rather than software.
Don't use a new part if you can't accept some risk. Micros dating from the late 70s are still in widespread use, and the chance of your
finding a new bug is pretty damn small."

or:

"Designate a couple of registers as
scratch - used to pass and return values to/from routines, and not guaranteed to be preserved by any routine."

Especially this last note I realized also. And after using A, B, DPTR, R0..R7 as scratch, reduces the stack growing and the code size dramatically.


Its really worth to be read many times to avoid overlooking important things.


Peter