It's always good to learn more about how your C gets translated into machine
language and exacuted. That said, if you really want to get your code to run
faster, you've got to profile it. There is no substitute. Intuition is
useless more often than not. Optimizing everything is equally futile. You've
got to find out where the bottlenecks are.
For example, I worked on an application that used the IR library to do
bidirectional communication between Palms. We added code to simulate
multiple devices all within the one application running on the emulator.
That allowed us to run gremlins over the bulk of the code for automated
testing, and it allowed us to find many of the performance bottlenecks. Of
course, real communication has it's own bottlenecks, so the technique isn't
foolproof.
--
Peter Epstein
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
