Path: utzoo!utgpu!attcan!uunet!husc6!rutgers!ucsd!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: What is the Status with SUMACC
Message-ID: <25449@ucbvax.BERKELEY.EDU>
Date: 5 Aug 88 04:58:42 GMT
References: <943@hodge.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Organization: School of Education, UC-Berkeley
Lines: 27

In article <943@hodge.UUCP> adail@pnet06.cts.com (Alan Dail) writes:
>HELP!!!
>I'm writing a DA 

Do not do this! SumacC is completely unacceptable for writing D.A.s.
SumacC generates funky position dependent code that is fixed up at load
time by the SumacC bootstrap routine.  You can crash any Mac with a SumacC
desk accessory by:

1.) open the d.a. in application "a".
2.) close the d.a.
3.) work with application "a", open and close a few files for example.
4.) open the d.a. again

La Bomba!

This happens because the D.  A. remains in memory between the two opens,
but it moves. When it is executed the second time, it is set up for the
wrong memory locations.

Do us all a favor. Get a real C compiler.

(Apologies if you just gave your message the wrong subject line.)

--- David Phillip Oster            --When you asked me to live in sin with you
Arpa: oster@dewey.soe.berkeley.edu --I didn't know you meant sloth.
Uucp: {uwvax,decvax,ihnp4}!ucbvax!oster%dewey.soe.berkeley.edu