Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!caen!uwm.edu!linac!att!rutgers!bagate!cbmvax!bj
From: bj@cbmvax.commodore.com (Brian Jackson)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: Manx/Lattice ENOUGH IS ENOUGH
Keywords: manx lattice conversion compatibility library
Message-ID: <21940@cbmvax.commodore.com>
Date: 27 May 91 06:38:56 GMT
References: <1991May26.022108.7901@sugar.hackercorp.com> <1991May26.172439.2021@NCoast.ORG>
Reply-To: bj@cbmvax.commodore.com (Brian Jackson)
Organization: Commodore, West Chester, PA
Lines: 41

In article <1991May26.172439.2021@NCoast.ORG> davewt@NCoast.ORG (David Wright) writes:

>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
>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

If you say so. 

1. Because it's a good compiler.
2. Personal preference. Despite the fact that I am pretty much up to my
   neck in SAS stuff here, I still prefer The Aztec compiler and I use
   it over SAS for almost all my personal projects.
3. For most peole there is minimal need to link with Forth modules.
   I agree that Blink object module compatibility would be nice but
   it's pretty easy to do most anything you'd want to do and never
   ever have to stare at a convoluted BLINK line or arcane pragma.
   (And I suspect the number of people needing Draco compatibility
   is even smaller than the Forth community :) <<- not a slam on
   either langauge, btw :))
4. The idea of having only one compiler company in the game does not
   make me smile at all. I think it's fair to say that the competition
   between Manx and SAS (nee Lattice) did nothing but good for both of
   the Amiga compilers (and therefore the Amiga users.) 
5. Multiple thought paths. Independant developers will come up with
   different solutions to a problem. Some work better than others. The
   good solutions often end up in both products (this process was very
   evident in the heyday of the Aztec/Lattice competition.)

Brian

 -----------------------------------------------------------------------
 | Brian Jackson  Software Engineer, Commodore-Amiga Inc.  GEnie: B.J. |
 | bj@cbmvax.cbm.commodore.com    or  ...{uunet|rutgers}!cbmvax!bj     |
 |    "Sometimes the hamster falls asleep in the little wheel."        |
 -----------------------------------------------------------------------