Xref: utzoo comp.os.msdos.programmer:5295 comp.lang.c:39539
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!rice!uw-beaver!fluke!ssc-vax!coy
From: coy@ssc-vax (Stephen B Coy)
Newsgroups: comp.os.msdos.programmer,comp.lang.c
Subject: Re: Summary of C Compilers from INFOWORLD
Message-ID: <4022@ssc-bee.ssc-vax.UUCP>
Date: 23 May 91 18:51:50 GMT
References: <28483@uflorida.cis.ufl.EDU> <3992@ssc-bee.ssc-vax.UUCP> <1991May21.175117.4101@rivm.nl>
Sender: news@ssc-vax.UUCP
Reply-To: coy@ssc-vax.UUCP (Stephen B Coy)
Organization: Boeing Aerospace & Electronics
Lines: 29

In article <1991May21.175117.4101@rivm.nl> epiren@rivm.nl (I.A.Kreis) writes:
>You don't have to specify the LIB variable. You don't have to link either.
>It is a compiler, not a linker. They DO give away alinker with the compiler
>package, which in my case works well. The LMB (linker) accepts full pathnames,
>which can be easily found in the first of T4FM's, but I agree, 
>just experimenting with it is a quicker way to find out. Flaming is even
>quicker.

Yes this works just fine but why should I have to explicitely
specify the path to the library I want to link with?  On the command
line I've already specified the memory model I want so why can't
Lattice figure out which library that corresponds to?  Every other
compiler on the market can.  As I also noted, Lattice has fixed this
behavior in their 286 (and I assume 386) developer's kits.  Since
Lattice is no longer providing updates I assume it will never be
fixed in the basic package.  I find this kind of behavior
unacceptable in a compiler especially in light of InfoWorld's
recommendation of Lattice as a good package for beginners.

Sorry if I touched a nerve but I stand by my assertion that if you
are going to buy a compiler, Lattice is not a good choise.

>Adriaan van Kessel
>epiren@rivm.nl

Stephen Coy
coy@ssc-vax.UUCP

				BDIF