Hi All-- Michael Chermside wrote: > > The REAL lesson here is that you shouldn't follow any "optimization" > rules without actually testing them. If you don't have time to test, > then just don't optimize... write whatever is most readable. If you > NEED more speed, then profiling and testing will show you what to > fix. (Using a better algorithm is a different story... do that > whenever you need it.) >
Tim Peters sayeth, "Premature Optimization is the Root of All Evil." And he is not kidding. Ever try to persuade a boatload of Java programmers that? Metta, Ivan ---------------------------------------------- Ivan Van Laningham God N Locomotive Works http://www.andi-holmes.com/ http://www.foretec.com/python/workshops/1998-11/proceedings.html Army Signal Corps: Cu Chi, Class of '70 Author: Teach Yourself Python in 24 Hours -- http://mail.python.org/mailman/listinfo/python-list
