Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uunet!overload!dillon From: dillon@overload.Berkeley.CA.US (Matthew Dillon) Newsgroups: comp.sys.amiga.programmer Subject: Re: Manx/Lattice ENOUGH IS ENOUGH Message-ID: Date: 29 May 91 02:50:55 GMT Article-I.D.: overload.dillon.8071 References: <4999@orbit.cts.com> Organization: Not an Organization Lines: 35 In article <4999@orbit.cts.com> chucks@pnet51.orb.mn.org (Erik Funkenbusch) writes: >davewt@NCoast.ORG (David Wright) writes: >>In article <1991May26.022108.7901@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >>... > >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. Much of ANSI was standardized long before the final draft. Prototypes, for example. >>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 Unfortunately, they are a problem. It forces you to use Manx's linker which is braindamaged... actually, *all* linkers are braindamaged, so you have to use the one that fits the mixed-language project. Unfortunately, with Manx C you *MUST* use Manx's linker. -Matt -- Matthew Dillon dillon@Overload.Berkeley.CA.US 891 Regal Rd. uunet.uu.net!overload!dillon Berkeley, Ca. 94708 USA