Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!uunet!bfmny0!tneff From: tneff@bfmny0.UUCP (Tom Neff) Newsgroups: comp.lang.c Subject: Re: optimization (was Re: C vs. FORTRAN (efficiency)) Message-ID: <14564@bfmny0.UUCP> Date: 19 Aug 89 03:51:57 GMT References: <3288@ohstpy.mps.ohio-state.edu> <225800204@uxe.cso.uiuc.edu> <14523@bfmny0.UUCP> <1613@mcgill-vision.UUCP> <14556@bfmny0.UUCP> <484@gistdev.UUCP> <1989Aug18.152547.10774@algor2.uu.net> Reply-To: tneff@bfmny0.UUCP (Tom Neff) Organization: ^ Lines: 27 In article <1989Aug18.152547.10774@algor2.uu.net> jeffrey@algor2.UUCP (Jeffrey Kegler) writes: >A lot of my compiles, and I suspect many other people's, are >recompiles of large systems where we are testing the result of >changing a single define. The change and test require next to no >thought but the recompile involves tens of thousands of lines. To paraphrase my previous award winning aphorism about optimization: Knowing WHEN to compile is as important as knowing HOW to compile. :-) The most annoying single creature in programming's Wild Kingdom is the raging Recompilasaurus. Bellowing its characteristic mating call -- "OH *THAT* MUST BE IT" -- this amazing creature snarls and stomps its way through the Thrashed Systemian jungles, changing one line and then recompiling! changing one line and then recompiling! -- leaving the twisted, still-moving hulks of object and listing files littered across the forest floor. When cornered by enraged packs of other programmer species, but especially by the dreaded Managatherium, its cry changes to the well-known "BUT I ONLY CHANGED ONE THING!" Well, I'll stay here at Base Camp and radio our position while Jim and Bob descend into the valley and put this radio collar on the raging Recompilasaurus... :-) -- "We walked on the moon -- (( Tom Neff you be polite" )) tneff@bfmny0.UU.NET