[Home] [By Thread] [By Date] [Recent Entries]
> Someone wrote: > >the accepted wisdom that premature optimization is evil? > > Here's what that accepted wisdom means: A well-structured program is an > important prerequisite for optimizing dynamic evaluation, because it leaves > you the flexibility to optimize precisely the things that a profiler tells > you are the bottlenecks, and the resulting code is still maintainable. And again. Maybe I should have made my post a couple of days ago? I wonder whether there is an apothegm to be distilled from the fact that resonses on the day I posted it got the joke, and responses on the following day didn't? Maybe "sero advenir semper deducet gravitas"? Where's Bacon when you need him? Oh, lest I forget :-) -- Uche Ogbuji Fourthought, Inc. http://uche.ogbuji.net http://4Suite.org http://fourthought.com Use internal references in XML vocabularies - http://www-106.ibm.com/developerw orks/xml/library/x-tipvocab.html Universal Business Language (UBL) - http://www-106.ibm.com/developerworks/xml/l ibrary/x-think16.html EXSLT by example - http://www-106.ibm.com/developerworks/library/x-exslt.html The worry about program wizards - http://www.adtmag.com/article.asp?id=7238 Use rdf:about and rdf:ID effectively in RDF/XML - http://www-106.ibm.com/develo perworks/xml/library/x-tiprdfai.html Keep context straight in XSLT - http://www-106.ibm.com/developerworks/xml/libra ry/x-tipcurrent.html Using SAX for Proper XML Output - http://www.xml.com/pub/a/2003/03/12/py-xml.ht ml SAX filters for flexible processing - http://www-106.ibm.com/developerworks/xml /library/x-tipsaxflex.html
|

Cart



