[comp.sys.mac.programmer] What is the Status with SUMACC

mdh@linus.UUCP (Mike Houle) (07/21/88)

   I have just discovered a thing called SUMACC.  I assume it is a
 cross compiler for 68000 code to be compiled on something like a SUN,
 and than ported over to a MAC.  Does anyone know where or what it is.

   I have looked on sumex-aim, and I can't find it there.

   Is there anyway I can get my little hands on such a wonderful thing
 such as this.  It could improve my developing by days, or even weeks...


  Thanks...
 
-- 
  Mike  Houle                         |
                                      | If I really had an opinion, and you 
  ! UUCP ->   decvax!linus!mdh        | believed it.  Then it's your fault..
  ! ARPA ->   mdh%linus@mitre-bedford |             not mine.

tedj@hpcilzb.HP.COM (Ted Johnson) (07/22/88)

>   I have just discovered a thing called SUMACC.  I assume it is a
> cross compiler for 68000 code to be compiled on something like a SUN,
> and than ported over to a MAC.  Does anyone know where or what it is.
>
>   I have looked on sumex-aim, and I can't find it there.

I thought it was on SUMEX.  I also thought it was obsolete.

>   Is there anyway I can get my little hands on such a wonderful thing
> such as this.  It could improve my developing by days, or even weeks...

Why not just invest the $100.00 it takes to get a REAL compiler (LSC, LSP)?


-Ted

cck@cunixc.columbia.edu (Charlie C. Kim) (07/25/88)

In article <730045@hpcilzb.HP.COM> tedj@hpcilzb.HP.COM (Ted Johnson) writes:
>
>>   I have just discovered a thing called SUMACC.  I assume it is a
>> cross compiler for 68000 code to be compiled on something like a SUN,
>> and than ported over to a MAC.  Does anyone know where or what it is.
>>
>>   I have looked on sumex-aim, and I can't find it there.
>
>I thought it was on SUMEX.  I also thought it was obsolete.
>
Sumacc was included as part of the 4.3 distribution.   I would not
exactly consider it obsolete, but it certainly less than useful right
now because the libraries are very much out of date.  In addition, the
library trap code uses self-modifying code which makes it useless on a
Mac II.

It is still useful for compiling general 68000 code direct.  Also, it
only runs on vaxen.

>>   Is there anyway I can get my little hands on such a wonderful thing
>> such as this.  It could improve my developing by days, or even weeks...
>
>Why not just invest the $100.00 it takes to get a REAL compiler (LSC, LSP)?
>...

It was great using sumacc to develop code for the 128k macs though --
the download phase usually took longer than the compile-link phase on
a 750.

Charlie C. Kim
User Services
Columbia University

adail@pnet06.cts.com (Alan Dail) (07/26/88)

HELP!!!
I'm writing a DA than can create a new window during accRun.  Everything works
fine unless you are running MF and switched to another layer. If this is the
case when the window is created, it shows up in the Layer of the currently
running Application rather than the DA handler layer.  I think that this is a
bug in MF because other programs that open windows work fine when switched
out.  Can anyone provide a workaround to this problem.  I have tried
everything I can think of with no success.  I need to get this fixed before
the MacWorld Expo.  I would appreciate it if someone could pass this question
to the Tech support people at Apple.  I am a certified developer, but my
AppleLink account hasn't gotten here yet.  I can be reached at (804)766-3904.

Thanks
Alan Dail

UUCP: {crash uunet}!pnet06!adail
ARPA: crash!pnet06!adail@nosc.mil
INET: adail@pnet06.cts.com

oster@dewey.soe.berkeley.edu (David Phillip Oster) (08/05/88)

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