Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!wugate!uunet!ingr!phil
From: phil@ingr.com (Phil Johnson)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Help.  Lattice & UnHunk
Message-ID: <6713@ingr.com>
Date: 3 Oct 89 14:03:12 GMT
References: <1602@tellab5.tellabs.CHI.IL.US> <6437@ingr.com> <1259@sas.UUCP>
Reply-To: phil@ingr.UUCP (Phil Johnson)
Distribution: na
Organization: Intergraph Corp. Huntsville, Al
Lines: 56

In article <1259@sas.UUCP> walker@sas.UUCP (Doug Walker) writes:
>What tools are you referring to, and why are they necessary to produce ROMable
>code?

I am talking about cross-compilers et al.

> 
>>Come to

>If you are interested in seeing the SAS system on the Amiga, call SAS Institute
>marketing and request it.  Obviously the Institute is not going to port 2 
>million lines of code without being convinced there is a substantial market
>for the product.

Doug; I called SAS about two years ago and ask if they were considering the
port.  I was told that there was no reason to port the SAS product to an Amiga
class machine.  When I asked the gentleman what he meant, he replied "The
Amiga is a nice game machine, but not business quality."  If it were not for
the quality of John's compiler I would never do business with any business
unit of the SAS institute.   [When I mentioned the above conversation to
Jay Denebem, I was told that it was probably some suit that just picked up the
phone.  Still seems to reflect a strange attitude]


>>
>The code produced by the compiler is perfectly ROMable, but you simply can't
>use the Amiga startup code (c.o and _main.c).  You'll need to provide your
>own code for opening whatever AmigaDOS libraries you need (i.e. dos.library,
>intuition.library, etc) or, if not on AmigaDOS, for getting access to whatever
>system resources you need.  And stdio calls are death.
>
>--Doug

Thanks for the pointers.  I have tried to use the 5.0 compiler once before to
write code for an MC68010-based embedded control system, but could not get
everything coordinated.  I have a fairly large macro library that I was
converting to C, but the code generated just wasn't right.  I didn't use the
Amiga startup code, but maybe I screwed up my libraries.  Another problem
could be in the linking process.  Any suggestions.

The Amiga makes one hell of a development platform.  I built a Write Control
Store that connects to my 1000 expansion port to serve as my download RAM/ROM.
I use emacs in one window to create/edit assembler code and run the Quelo 68K 
cross-assembler to generate the executable.  I use a VT100 emulator in a second
window to connect to the development module.  I can then move assembled code 
to WCS and runs the control system.  If I find a problem I activated the edit/
assembler window and fix the problem the reload the WCS and do it again.  It's
even easier and faster than the VAXs or workstations at work.

It seems that a hugh market for the Amiga is going untapped.
 
 
-- 
Philip E. Johnson                    UUCP:  usenet!ingr!b3!sys_7a!phil
MY words,                           VOICE:  (205) 772-2497
MY opinion!