Hello, I was browsing through older posts that deal with the painful issue of portability (http://www.keil.com/forum/docs/thread8109.asp). I was (and still am) a big advocate of programming as much as possible conforming to the C standard, and having a layered structure that allowed "plugging-in" other hardware. But I have come to change my mind recently. I am reading the "ARM system developer's guide" (excellent book by the way. I'm reading it because I want to port some C167 code to an ARM9 environment) in which chapter 5 discusses writing efficient C code for an ARM. The point is, and it is fairly demonstrated, that even common, innocent looking C code can either be efficient of very inefficient on an ARM depending on specific choices made, let alone another processor used! So, if we are talking about squeezing every clock cycle out of a microcontroller - I do not believe that portability without ultimately littering the code is possible!
when quoting me, please quote fully
Coming from the master of quotation abuse himself that's a bit rich.
But if you insist:
re buggy pseudo-code who cares, it did show what I ment.
Says it all, really. Do you write 'real' code with such lack of attention to detail? How about your documentation?
I'm sure your answer will be 'no', but I for one am unlikely to believe that you live this double life.
Perfect engineer by day, illiterate CS101 student by might? I think not.