Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!endor!olson From: olson@endor.harvard.edu (Eric K. Olson) Newsgroups: comp.sys.mac Subject: Re: C and large data model Message-ID: <3601@husc6.harvard.edu> Date: 18 Dec 87 04:31:36 GMT References: <8712152132.AA10832@decwrl.dec.com> <3566@husc6.harvard.edu> <36709@sun.uucp> Sender: news@husc6.harvard.edu Reply-To: olson@endor.UUCP (Eric K. Olson) Organization: Lexington Software Design Lines: 29 In a recent article Sam Cramer writes: >A couple more advantages of LSC over Manx: ... I use LSC 2.13 (which is fully Mac II capable, as well as compatible) on a Mac II with 5 meg of RAM under MultiFinder 1.0. When I Run the project, it opens up in a MultiFinder partition of its own, with the size determined by the SIZE resource in the Project file; when I compile it down to an application, it uses the SIZE resource in the Project.rsrc file (so those two can be different, which is good). I also run ResEdit at the same time, leaving the window for the disk open (the Project.rsrc file must be closed in ResEdit to Run in LSC, and the project must not be running to open the file in ResEdit. Making either mistake seldom causes a crash.). This has got to be the current ultimate C development system for the Mac. I don't even have to exit the editor to change the resources, something I ALWAYS had to do (until LSC w/Switcher, which I used before). This makes it much easier to write good, portable, Mac Code, since I can easily see what ID's things have, and I can modify the resources easily to help debugging (make my Windows all visible by default so I can see the setup activity, for instance). The only thing LSC doesn't do is compile in the background (or even allow task switching during compiling). That would be nice. -Eric I am not affiliated. Eric K. Olson olson@endor.harvard.edu harvard!endor!olson D0760 (Name) (ArpaNet) (UseNet) (AppleLink)