Hallo User, ein besch... Tool

You always have to be a bit careful comparing C and Pascal, because you are not really comparing like with like. For example, during initialsation, in AVRCo variable are initialised to zero. In C that operation is simply missing.

Similarly in loops, AVRCo does boundary checking, but C does not.

Another thing to be aware of is that I specifically do not do all optimisations on the system area, at Rolf's request, so there are sometimes gains to be made there that are not done. For example, some functions have multiple options, but only one path is executed. Typically variations account for pointers to different spaces (EEPROM/RAM/FLASH) where only one is actually used.

I did a poll at one stage to see whether loops with global variables should be optimised the way local variables are, and the answer came back 'no', so some optimisations are possible but deemed to be not worth it.

Like Rolf, I prefer safety first, so sometimes I do not do an optimisation because is is theoretically possible that a variable could changed where in practice it does not.

But I am always looking for new optimisation ideas, and any suggestions are always welcome, even if sometimes they turn out not to be practical.