Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!ogicse!pdxgate!eecs!bairds
From: bairds@eecs.cs.pdx.edu (Shawn L. Baird)
Newsgroups: comp.sys.amiga.programmer
Subject: On the subject of optimization
Message-ID: <2243@pdxgate.UUCP>
Date: 5 Apr 91 12:53:14 GMT
Sender: news@pdxgate.UUCP
Lines: 17

I think jumping into assembly code where not needed can be a treacherous
mistake.  One method of avoiding wasting time on unnecesaary (who said
comp. science majors had to be able to spell?) optimizations is to
profile your code.  Write some timer routines and throw it in with
Forbid()/Disable() or whatever works for your project.  Then go look at
the slower code and see what you can do to speed it up.  If you're
lucky, you get to the point where you don't need more speed because the
hardware or the user is slowing you down.

And that's everything you'll ever need to know about optimization, and
you heard it here first. ;)  Seriously though, profile, profile,
profile.  Don't assume which part of your code is slowing you down. It's
easy to get it wrong.

---
 Shawn L. Baird, bairds@eecs.ee.pdx.edu, Wraith on DikuMUD
 The above message is not licensed by AT&T, or at least, not yet.