Date:	Sun, 19 Mar 2000 20:13:49 +0600 (LKT)
From:	Kalum Somaratna aka Grendel <kalum AT lintux DOT cx>
X-Sender:	root AT darkstar DOT grendel DOT net
To:	djgpp AT delorie DOT com
Subject:	Re: Compiling with DJGPP.... how can I speed it?
Message-ID:	<Pine.LNX.4.10.10003192013090.970-100000@darkstar.grendel.net>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Sun, 19 Mar 2000, Eli Zaretskii wrote:

> 
> On Sun, 19 Mar 2000, Kalum Somaratna aka Grendel wrote:
> 
> > So it follows that on a p-166 your 10000 line program would take about 10
> > secs to compile. a long time indeed.
> 
> You are kidding, right?  Because 10 seconds is not even enough time to
> reflect upon the bugs you might have left lurking in the code you're
> compiling...

Yes I said it in a light mood ;-) but one habit I, and I'm sure many other
people have developed is that after typing in come code I find that I like
running the compiler to see whether there are any syntax errors like
missing semicolons etc, It's a nice thing to do and it certainly helps a
lot especially if the compile time is short.

But if the source I am writing takes 10 secs to compile, then the above
quick syntax check becomes rather too much, wouldn't you agree.


> 
> Large projects take tens of minutes, sometimes hours, to build.  Now
> *that* is a long time indeed.  Whereas 10 seconds--well, it's just a
> blink ;-).

Yes the Linux Kernel (60MB of source) comes in to mind, but then even the
kernel and the modules etc are compiled in about 5 minutes in a K7 500.

Grendel

Hi, I'm a signature virus. plz set me as your signature and help me spread
:)

- Raw text -