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!
Jack Sprat wrote: "Given that new posts are highlighted I don't see how that would offer any real benefit, but I'm willing to give it a try."
The highlight only lives a short time. If you get a call after you have started to read updated threads, the highlights may disapear. And the highlights only shows unread posts, it doesn't show them in chronological order.
Dan Henry wrote: "I am too late for the party, so as an aside, how does one 'post at the bottom'?"
I normally press the 'Reply' button on the bottom-most post in the thread. It doesn't always work, since I can't see what other posts are in the process of being written.
It is a bad thing that this forum doesn't indent discussion branches. Opening a heavily branched thread a day or two late makes it very, very confusing to try and understand who responded to what.
Quite a number of times I have had to hunt time stamps just to locate new posts that has lost their highlighting, or what post was a reaction to what post. It really is a big pest.
Keil: Either make this forum linear, or style the threads to show tree-view branches. Or at least number the posts, and add a little reference: "In response to post #x from yyyy-mm-dd hh:mm".