Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!cs.umn.edu!kksys!orbit!pnet51!chucks
From: chucks@pnet51.orb.mn.org (Erik Funkenbusch)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Manx/Lattice ENOUGH IS ENOUGH
Message-ID: <4999@orbit.cts.com>
Date: 27 May 91 07:25:03 GMT
Article-I.D.: orbit.4999
Sender: news@orbit.cts.com
Organization: People-Net [pnet51], Minneapolis, MN.
Lines: 54

davewt@NCoast.ORG (David Wright) writes:
>In article <1991May26.022108.7901@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes:
>>conversions of Lattice programs (and getting ticked off at Lattice for
>>not following the ANSI spec all the way). I'm sure other people are doing
>	They do much more so than Manx, who only recently added any kind of
>ANSI compliance. I don't use many esoteric features of the ANSI standard,

What do you call recently?  the ANSI standard wasn't finalized until may of
'90 and Manx gave full ANSI in january of '90, with an update in june to fix
things that changed in the finalization.  that isn't "recent" (a year and a
half ago?)  anybody claiming an ANSI compliant compiler before may was working
of of a draft proposal, and most of them haven't updated their compilers to
that point since it was finalized.

>but I have yet to find something that SAS/C does incorrectly.
>>Hows about some of us get together and write a couple of libraries that
>>automate this? We'd also need blink--make and make--blink tools, and something
>>to convert Lattice's __chip declarations and Manx' #pragmas.
>>
>>Alternatively, we could hold some Manx and SAS emplyees to ransom until
>>they bury the hatchet... :->
>	Or even more alternatively, you could just have people throw Manx C
>into the circular file (where IMHO it has belonged for more than 3 years)
>ASAP :-)
>	(For the humour impared: :-))
>What can you say about a C compiler that produces non-standard object modules
>so you can't link with modules produced with other languages? I have been able

Manx's object modules are not a problem if you use Manx's linker.  the Manx
linker has an option to link standard Amiga object modules in with the Manx
ones.  Manx uses their object modules format to standardize all their comilers
together, for instance, you can use a module generated on a Mac and link it
into your amiga module as long as no system dependencies are involved.  *I*
like that option much more, because you can have people working on the same
program for different machines WITHOUT having to give out your source code for
common modules.

>to link in AL modules created with a wide variety of assemblers, modules from
>a version of Forth, modules from Draco, and modules from a couple of other
>languages with Lattice/SAS C since day one. You can't say the same thing
>for Manx. For me, the question is: Why in this day and age would anyone
>continue to BUY the Manx compiler? (no :-))
>
>
>				Dave

.--------------------------------------------------------------------------.
| UUCP: {amdahl!tcnet, crash}!orbit!pnet51!chucks | "I know he's come back |
| ARPA: crash!orbit!pnet51!chucks@nosc.mil        | from the dead, but do  |
| INET: chucks@pnet51.orb.mn.org                  | you really think he's  |
|-------------------------------------------------| moved back in?"        |
| Amiga programmer at large, employment options   | Lou Diamond Philips in |
| welcome, inquire within.                        | "The First Power".     |
`--------------------------------------------------------------------------'