1) This is where the fallacy of "Assembler gives tighter code" lies; I've said it many times before - it's not Assembler itself that gives tighter tighter, it requires a skilled & experienced assemlber programmer to do it.

2) The same applies to writing "portable" code in 'C' - as Erik so often says, if you just assume that your code must be inherently portable simple by virtue of writing it in 'C' ("C is C"), then you are seriously mistaken!

1) This is where the fallacy of "C is C" lies; it requires a skilled & experienced assemlber programmer to write "compiler code friendly to the processor" that makes C "tighter and faster". As an example, the "switch" statement is a real 'killer' in '51 C, whereas if (bit) is much more powerful in '51 C than most other environments.

2) since 1) is correct procedure for embedded microcontrollers 2) is automatically void.

re 2) In an environment, such as the PC, where (virtually) no I/O is involved C is, indeed, quite portable. However in a microcontroller environment where, even a thing like finding a cosine, is I/O related (must be done before next input) that does not hold.

Erik

so, it all comes back to my favourite phrase " the '51 ain't no PC"