From Chris Downs · 1996-04-07 19:18 · #73646 in EMULATE
In reply to Re: Help! Wizard needed! by Chris Downs
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. EB> Some of us work with interrupt driven embedded systems projects which EB> have such tight time and code space budgets that even using C at all is EB> in question (vs. assembly language). Chris' statements may be true *in EB> his domain*, but they're certainly not universally true. Clock ticks don't matter very often still rings true to me. But you seem to be admitting above that it's YOUR domain that's exceptional. And please Ed, don't mischaracterize my views. Turning "don't matter very often" into "universally true" isn't anything close to accurate. If I'm doing a miserable interpretation of your comment, then I apologize. Otherwise here's a thanks in advance for your consideration in the future. EB> I was trying EB> to explain why what he might construe as "an obsession with clock EB> ticks" is, in other areas, simply sound engineering practice. Yes there are plenty of exceptions to the "not very often" criteria. "Sound engineering practice" is to know where you should devote your efforts to achieve maximum results. If the 90-10 rule that so many others have noticed doesn't fit your particular (and seemingly out of the norm) problem domains, then you have to adjust. --- þ Blue Wave/QWK v2.12 þ --- WILDMAIL!/WC v4.12 * Origin: (1:100/4.0)