AWCTTYPA@UIAMVS.BITNET ("David A. Lyons") (03/21/89)
>Date: Sun, 19 Mar 89 12:34:03 CST >From: "Jeremy G. Mereness" <jm7e+@ANDREW.CMU.EDU> >Subject: Re: The Nifty //GS and Apple Support > >One thing... I understand that the GS is a pain to write anything big >on, but much of that is because there is as yet not that many good >development systems for it. GS/OS is still buggy, APW is buggy, and >the C language isn't very good either. Hang on.... (1) How did you decide that GS/OS is "buggy"? How come I'm not having problems with it? There are a lot of buggy applications whose bugs become more obvious under GS/OS, but that doesn't make GS/OS buggy itself. (2) APW could certainly stand some improvement, but it gets the job done. We have Tim Swihart's word (in the APDAlog that came out a couple months ago) that the improvements _are_ on the way, by the way. (3) I assume you are referring to APW C, not to C in general. APW C has a worse reputation than it deserves. Its biggest problem is speed, but it works. >[...] If decent development systems were made for the GS (on the same >level as ThinkC, TurboC and Turbo Pascal) then developers would not >be complaining as much. But not even Apple has done this, and as with >the Mac, they have to make the first move. WHY does Apple need to make the first move? Anyway, have you seen TML Pascal (standalone version) and Merlin 16+? Both of these are perfectly usable. I wrote DIcEd in 4200 lines of TML Pascal. ORCA/C is on the way, too. By the way, I would certainly not describe writing DIcEd as "a pain," although it isn't all that big, either (under 100K). >jeremy mereness >jm7e+@andrew.cmu.edu (arpa) --David A. Lyons bitnet: awcttypa@uiamvs DAL Systems CompuServe: 72177,3233 P.O. Box 287 GEnie mail: D.LYONS2 North Liberty, IA 52317 AppleLinkPE: Dave Lyons