Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!snorkelwacker!mit-eddie!bu.edu!bu-cs!dartvax!eleazar.dartmouth.edu!erics
From: erics@eleazar.dartmouth.edu (Eric Schlegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW wish list
Keywords: MPW
Message-ID: <19267@dartvax.Dartmouth.EDU>
Date: 9 Feb 90 17:06:48 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> <10865@claris.com>
Sender: news@dartvax.Dartmouth.EDU
Organization: Dartmouth College, Hanover, NH
Lines: 27

In article <10865@claris.com> drc@claris.com (Dennis Cohen) writes:
>erics@eleazar.dartmouth.edu (Eric Schlegel) writes:
>>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.


That would also be a nice feature to have. Incremental compilation really gets
nice, though, when you consider this: change the implementation of a function,
and only the function is recompiled. Change the function interface,
and the compiler is smart enough to recompile the function and every statement
that calls the function - but nothing else.

And another wish for MPW - I want a faster editor! The editor is very easy
to type ahead of, even on a II-class machine. This is especially a problem
when the text displayed in a window is wider than the window - this seems
to slow down the editor drastically. 

-eric
--
Eric Schlegel '90             |   "Never underestimate the bandwidth of a
eric.schlegel@dartmouth.edu   |    station wagon full of tapes."