Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!rutgers!tut.cis.ohio-state.edu!purdue!decwrl!claris!peirce
From: peirce@claris.com (Michael Peirce)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacApp pascal compiler
Message-ID: <10859@claris.com>
Date: 7 Feb 90 01:15:30 GMT
References: <1990Feb2.154008.17297@isy.liu.se> <38373@apple.Apple.COM> <1990Feb6.204151.26764@asterix.drev.dnd.ca>
Reply-To: peirce@claris.com (Michael Peirce)
Distribution: comp
Organization: Claris Corporation, Santa Clara CA
Lines: 32

In article <1990Feb6.204151.26764@asterix.drev.dnd.ca> louis@asterix.drev.dnd.ca (Louis Demers) writes:
>marc@Apple.COM (Mark Dawson) writes:
>>(2) Programing:
>>    a) Put each method in its own file.  This will mean that you may have many
>>      files (I have about 20 source files).  This will speed up your compiles
>>      (I don't know of any way to speed up your links).
>                                   ^^^^^^^^^^^^^^^^^^^
>
>    I am waiting for my upgrade to MacNosy/TheDebugger which
>    includes an incremental linker which is supposed
>    to speed up links.  I called Jasik Design and the
>    advertised requirements of 4 Mb. is more like 8 Mb
>    if you plan to use MacApp/C++.

I'm currently using Jasik's Debugger and the Incremental Build System with
MacApp/Object Pascal and I'm generally happy with it.

Turn around time is short (less than 10 seconds on short programs, 40 seconds
for a humongous program I'm working on) as long as you don't change the
interface to a routine.  If you do, you have to do normal build.

It's saved me a lot of time and has been well worth the trouble to me.

 Claris Corp. | Michael R. Peirce
 -------------+--------------------------------------
              | 5201 Patrick Henry Drive MS-C4
              | Box 58168
              | Santa Clara, CA 95051-8168
              | (408) 987-7319
              | AppleLink: peirce1
              | Internet:  peirce@claris.com
              | uucp:      {ames,decwrl,apple,sun}!claris!peirce