Path: utzoo!attcan!uunet!dino!ux1.cso.uiuc.edu!brutus.cs.uiuc.edu!apple!claris!drc
From: drc@claris.com (Dennis Cohen)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW wish list
Keywords: MPW
Message-ID: <10865@claris.com>
Date: 8 Feb 90 22:06:55 GMT
References: <1990Jan23.065751.29303@peace.waikato.ac.nz> <6310@internal.Apple.COM> <55359@hobbit.UUCP> <1990Jan25.191441.26280@oracle.com> <416@dbase.A-T.COM> <19240@dartvax.Dartmouth.EDU>
Organization: Claris Corporation, Santa Clara CA
Lines: 26

erics@eleazar.dartmouth.edu (Eric Schlegel) writes:

>>In article <1990Jan25.191441.26280@oracle.com> omullarn@oracle.com (Oliver Mullarney) writes:
>>>- Incremental linking would be nice. Waiting 15 minutes to relink after
>>>  a change of one object file is very boring.
>>


>Even better - incremental compilation. Forget to put a semicolon after one
>line in your 2000 line MacApp include file? No problem. The compiler recompiles
>_only that one line_ instead of compiling the entire program.

I think that a better solution for such simple errors would be one that was
in one of the first Pascal compilers I ever used (1979). The University of
Wisconsin's Univac 1100 compiler gave a warning message with the context and
continued to compile, treating the source as though the semicolon were there.
If Fischer and LeBlanc could do that on a Univac 11 or 12 years ago, it seems
that we should have compilers that do that now.  Some errors were non-
recoverable; however, I've missed that "friendliness" in every compiler I've
used since then.

Dennis Cohen
Claris Corp.
 ****************************************************
Disclaimer:  Any opinions expressed above are _MINE_!
 ****************************************************