Path: utzoo!attcan!uunet!lll-winken!brutus.cs.uiuc.edu!psuvax1!psuvm!cunyvm!uupsi!rodan!isr
From: isr@rodan.acs.syr.edu ( ISR group account)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MPW wish list
Keywords: MPW
Message-ID: <2028@rodan.acs.syr.edu>
Date: 9 Feb 90 15:08:25 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>
Reply-To: isr@rodan.acs.syr.edu (Michael S. Schechter - ISR group account)
Organization: Syracuse University, Syracuse, NY
Lines: 22

In article <19240@dartvax.Dartmouth.EDU> 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 recompile
>_only that one line_ instead of compiling the entire program.

Maybe incremental compiling down to the line level would be a bit difficult,
but certainly having it at the routine level would not be that difficult.
That way as long as arguments, return values, and globals all had the
same TYPE as before, all you have to update are the address's whereever
they where referenced.

(just stick the new routine after the last old one, update all
addresses)
Of course, you'd only want to do this a few times before you would
do a real compile/link to prevent nightmares from ocurring.
--
Mike Schechter, Computer Engineer,Institute Sensory Research, Syracuse Univ.
InterNet: isr@rodan.acs.syr.edu   Bitnet: SENSORY@SUNRISE