From Ed Beroset · 1996-04-05 18:34 · #73538 in EMULATE
In reply to Re: Help! Wizard needed! by Darin McBride
In a msg on <Apr 05 12:34>, to Ed Beroset, Darin McBride writes: CD>> that's truly misguided. Clock ticks matter only when clock CD>> ticks matter and clock ticks don't matter very often. EB>> I don't know the kinds of projects on which you EB>> typically work, but the generalization "clock ticks EB>> don't matter very often" isn't accurate in my world. DM> Perhaps Chris didn't mean it this way, but I'll give an example DM> that shows what he said. DM> One project at the company I'm doing contract work for is DM> building a 32-bit data manager/server for networking their 16-bit DM> software for real-time data sharing. [...] I'm sure any of us could come up with a dozen examples of cases in which "clock ticks don't matter." I write code like that myself on occasion, but while it doesn't make much sense to count every clock tick in, say, an OS/2 based icon editor where the typical system is running with 16M of RAM on a 486-33 or better, not everyone does that sort of work. That was my point. Some of us work with interrupt driven embedded systems projects which have such tight time and code space budgets that even using C at all is in question (vs. assembly language). Chris' statements may be true *in his domain*, but they're certainly not universally true. I was trying to explain why what he might construe as "an obsession with clock ticks" is, in other areas, simply sound engineering practice. -> Ed <- --- Squish v1.01 * Origin: = Psychotronic BBS // 919-286-4542 // Durham, NC = (1:3641/1.250)