Gabriel Sechan wrote:
It actually tends to be a loss- you're now going through 2 levels of compilation, which may destroy optimizations available at the original level, and takes away almost all ability of the developer to actually optimize (asside from the high level optimization of picking the best algorithm).
Nowadays the consensus (which I agree with) seems to be that developers should not be worrying about optimization of anything but their own algorithms. And in the rare cases where they do need to optimize other things they should be writing in high level languages and then linking in their own optimized C or even further optimized assembly code. The price you pay for such optimization is increased complexity and time and loss of portability.
I am reading "Programming From The Ground Up" and it is a very good intro to assembly and how things really work under the hood. I have had it on my bookshelf for over a year before actually getting around to reading it. Chris Seberino's assembly language presentation got me to pick it up and finally go through it. Assembly on Linux is so much easier and nicer than it was back in my DOS days when I last really messed with it.
-- Tracy R Reed http://ultraviolet.org A: Because we read from top to bottom, left to right Q: Why should I start my reply below the quoted text -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
