#C Compilers: which one?
20-Jul-89 17:20:31
Sb: #57942-#C Compilers: which one?
Fm: Bob Rakosky 75156,336
To: Black Belt Systems 76004,1771
Ben,
Sorry, but Lattice is not yet a solid product. I've been bit by a number of
different compiler bugs during the development of my current project. I've lost
a LOT of time to tracking them down. Granted, some of these bugs were in Beta
patches (that I needed to fix other bugs), and the compiler _is_ getting there,
but it's not quite there yet.
I even got to the point where I went out and _bought_ Manx (bucking the
tides, as usual 🙂 and converted my > 1 meg of source code to Manx, just
because I couldn't lose any more time to chasing bugs that weren't my own (and
compiler bugs are a royal pain to track down to a reproducable sequence of
managably-sized code from 1+ meg). Converting to Manx cost me about 2 days of
work (primarily because "Lattice-style" coding _is_ generally more portable),
but I have not yet tracked down a single bug that I can blame on a compiler bug
(as opposed to a compiler ideosyncracy) with Manx.
In general, I agree that Lattice is a much better product at the design
level. Hopefully, the next release patch-version will make it a stable and
dependable product. I haven't had time to really look at the later beta
patches, so I can't say for sure (although the last level I had tried was
getting there). Only wish that Lattice's compile/link speeds and
debugger-info-handling were on a level with Manx – Manx is a definite win in
those areas.
As usual, Ben, things aren't quite as black-and-white as you portray them.
But you knew that, didn't you? <grin>
…BobR