CompuServe Messages

Larry, I'd have to say that there was never a time when "most developers were using manx". There was a time when manx was highly touted here on CIS, despite it's backwards inclusion of garbage capabilities like ILAC, it's inability to link in the std Amiga format, the all-in-one (small) data capability, it's far-from compliance with ANSI, and it's default to 16 bit operation when that was NOT the std… I heard a lot of people here singing it's praises – but I rarely ran into code that was actually made with it. I know some of the PD guys use it – Keith, for instance – and I know that some of the developers use it, too. There were some perfectly horrible code examples in Transactor, for instance. But Lattice was never the minority compiler – it only seemed that way to those who had Manx, because they wanted it to be that way. they generated smaller code only with the default options set to non-std – 16 bit. Lattice pointed out (repeatedly) that if you asked for 16 bit stuff and so on with the then-current compiler, you got executable of comparable size. Part of that issue was start-up code, too – the Lattice startup code is much more robust, feature wise, than the Manx, which made it bigger. Faster code? Same issues. Use the same options, you got comparable code. There never was any huge performance gap, except to hopeful Manx owners. I've been generating Amiga applications with Lattice for almost five years now, and I've been completely satisified – my one fling with Manx was truncated by the peculiar proprietary linking, the lousy defaults, the small data capacity, and the fact that it supported ILAC, which I view as the worst C sin going. Ben Amateur Radio Callsign is A A 7 A S