From:	"Damian Yerrick" <web DOT poison AT pineight DOT 8m DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Mouse Events Problem
Date:	Wed, 20 Oct 1999 15:42:19 -0500
Organization:	Rose-Hulman Institute of Technology
Lines:	11
Sender:	AFSAUTH AT yerricde DOT laptop DOT rose-hulman DOT edu
Message-ID:	<7ul9ig$e2f$1@solomon.cs.rose-hulman.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 991020140024 DOT 22660b-100000 AT is>
NNTP-Posting-Host:	yerricde.laptop.rose-hulman.edu
X-Trace:	solomon.cs.rose-hulman.edu 940452240 14415 137.112.104.64 (20 Oct 1999 20:44:00 GMT)
X-Complaints-To:	news AT cs DOT rose-hulman DOT edu
NNTP-Posting-Date:	20 Oct 1999 20:44:00 GMT
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2314.1300
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
> Anyway, you should never try to optimize the code before you wrote it.
> Once you get the program working, if it runs too slow, profile it and see
> where it spends most of the time.  More often than not, you will be
> surprised by what the profiler shows.  Which means that optimizing early
> generally means you optimize in the wrong place.

Any good HowTo pages on optimization?

- Raw text -