On Wed, 15 Jul 2009, Dario Greggio wrote:

> Gerhard Fiedler ha scritto:
> 
> > Sergio's example a while ago was that since the compiler knows what
> > remove(), insert() and replace() do (because they are part of the
> > language rather than a library), it is possible for the compiler to
> > replace a sequence of remove() and insert() with an appropriate
> > replace(), making the code more efficient.
> 
> Just my .0002c :) into this interesting topic:
> 
> won't this make the programmer "lazier", while OTOH C lets you use your 
> brain better?

You could say the same about moving from C to assembler.

But as I keep saying, the main point isn't about optimisation it's about 
understaning the intent of the programmer. The better you understand the 
intent the better you can catch mistakes. It just so happens that the 
better you understand the intent the better you can ALSO optimise the 
generated code.

Friendly Regards
Sergio Masci
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist