Bill Fairchild wrote:
Best reason of all. Time saved is in the order of nanoseconds; time spent on discussing, thinking about, different keystrokes, etc., far outweighs the benefit UNLESS the code is executed thousands of times per second in critical paths, like disabled interrupt processors, the Dispatcher, adding FRRs, etc.
While I don't disagree, once writing efficient code gets to be a habit, it takes no extra time during coding, and might save some time during testing. It's like bathing - some people do it regularly once a week whether they need to or not <G>
Gerhard Postpischil Bradford, VT ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
