From Chris Downs · 1996-04-07 19:07 · #73645 in EMULATE
In reply to Help! Wizard needed! by Jerry Coffin
CD> It seems that part of the "culture of C" is CD> to be intimately concerned with each clock tick. I think 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> Maybe what you perceive as the "culture of C" is simply EB> a problem domain other than whatever it is you do. Maybe so, but there's some strong empirical evidence to the contrary. Heck, I'm not the first dude on the planet to have noticed the 90-10 rule for code optimization. And I'm sure not the first dude to have noticed the obsession with speed that is common among C and assembler programmers. I've worked on a mighty wide range of projects from real time process control, communications, shrink wrap stuff to batch stuff too. I've never had to worry about optimizing for speed anything other than those certain sections of code that required that each clock tick be conserved regardless of whatever else. And amazingly enough, all those programs worked "fast enough". Like I said, the 90-10 rule has been empirically validated for me. Since I've never heard of a 40-60 rule nor have I experienced it, my guess is that it's your problem domains that are regularly falling outside the norm. --- þ Blue Wave/QWK v2.12 þ --- WILDMAIL!/WC v4.12 * Origin: (1:100/4.0)