At 23:55 -0500 2001_11_11, Tab Julius wrote: >Although people always think the slowest part of their code is the >incredible calculations performed
I have also met that numerous times; Programmers obsessed with performance-considerations, in parts of a program, where optimization can potentially yield a promille of performance. It wouldn't matter, if it only meant that they were spending obsessive amounts of their own time tweaking something. What matters to me is that those misplaced performance-considerations, is often used to propagate a primitive and rigid structure, instead of a more abstracted OOP structure. >, in 25 years of programming I can tell you that it is pratically >never the case. The slowest part has always been I/O, specifically: > >: Accessing a disk >: Putting bits on the screen This is also my experience, and I even thought it was kind of universal; I never expected to hit the code-barrier, until I did a game with lots of objects doing collision checking, in floating points through deeply nested OOP chains. Jakob [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]) Lingo-L is for learning and helping with programming Lingo. Thanks!]
