There is a new 8051 C compiler in beta test that beats Keil's compiler by 35% code size, and 14% speed, on the Dhrystone benchmark. And, there is no need to select a memory model or use special keywords to control data placement.
More details here: www.htsoft.com/.../silabs8051beta
If you find yourself reaching for the ICE or stepping through compiler output on a regular basis you are either working with 3rd party junk rather than decent development tools or libraries, or the code you have written is junk.
I think I have to agree with that. Most code either works on the first run, or reading the code is enough to see what ails it. A bit of guard code can help in case I have made an incorrect assumption about the value range of the input, or in case I'm inserting the new code in already broken code.
I think I have to agree with that. Most code either works on the first run, or reading the code is enough to see what ails it Try, for instance to write an interface to a FTDI vinculum and debug it by the above method, you will die before the program runs.
there are beautiful debugging theories based on all information given is complete and correct just one comment male cow manure.
Erik
You are always so poetic.