Path: utzoo!mnetor!uunet!nuchat!peter
From: peter@nuchat.UUCP (Peter da Silva)
Newsgroups: comp.sys.amiga
Subject: Re: Feeping Creaturism
Message-ID: <722@nuchat.UUCP>
Date: 3 Mar 88 02:55:02 GMT
References: <655@nuchat.UUCP> <657@sandino.quintus.UUCP> <670@nuchat.UUCP> <714@sandino.quintus.UUCP>
Organization: Public Access - Houston, Tx
Lines: 31

In article <714@sandino.quintus.UUCP>, pds@quintus.UUCP (Peter Schachte) writes:
> > > And after you compile and link your program, and you edit it and change
> > > one variable name somewhere, how long does it take you to compile and
> > > link again.

If I changed a variable name, and the incremental compiler *didn't* go
back and recompile quite a lot, I'd be real wary about trusting it. Changing
declarations tend to have far reaching consequences.

> > Maximum of 5 minutes for a sizable program. More like a minute if I was
> > being totally cool about modularization, and none of the files were over
> > the 6K of copy.c.

And of course it took more than that to find the bug, make the change,
document it, look around for anything else that might be hosed, and then
after I've compiled it and run it, about 10% of the time, guru and reboot.

> > If you have an incremental compiler, that goes down to 47 seconds, absolute
> > minimum.

> Where'd the 47 number come from, anyway?

That was the amount of time Browser spent linking.

> > > 	1.  editing

This is the big time consumer. Really.
-- 
-- a clone of Peter (have you hugged your wolf today) da Silva  `-_-'
-- normally  ...!hoptoad!academ!uhnix1!sugar!peter                U
-- Disclaimer: These aren't mere opinions... these are *values*.