Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!world!decwrl!bacchus.pa.dec.com!granite.pa.dec.com!mwm From: mwm@raven.pa.dec.com (Mike (My Watch Has Windows) Meyer) Newsgroups: comp.sys.amiga Subject: Compiler support Message-ID: Date: 11 Oct 90 17:45:53 GMT References: <8457@milton.u.washington.edu> <66@screamer.csee.usf.edu> <8587@milton.u.washington.edu> <1990Oct11.174014.17034@csun.edu> Sender: news@wrl.dec.com (News) Distribution: comp Organization: Missionaria Phonibalonica Lines: 29 In-Reply-To: bcphyagi@Twg-S5.uucp's message of 11 Oct 90 17:40:14 GMT In article <1990Oct11.174014.17034@csun.edu> bcphyagi@Twg-S5.uucp (Stephen Walton) writes: I'm not sure what "2.0 support" means in terms of a compiler. In terms of a compiler - little more than the includes & pragmas. In terms of a development environment, you have the CBM-blessed 2.0 preferences facilities to set defaults. WB support - which includes invoking the compiler/editor/debugger/maker from the workbench, as well as automatic creation of icons for compiled programs & source files - get the 2.0 3d look icons. Summary: If you currently have either Lattice or Manx, there is no overriding reason to switch to the other compiler. If you have none yet, there is no reason on the basis of customer support or upgrade availability to prefer one to the other, either. IM not-so-HO of course. I'll agree with that. Manx has clearly emerged from the post-3.6 dormant period, but I'd still be a little leary of a relapse. However, Lattice support just moved inhouse to SAS, and it's not clear exactly how things are going to go. If things continue as they have been in the recent past, both of these factors will be ignorable after a short while.