#TID compiler
2 messages in this thread
Just to add my own comment, as I've posted a couple of times recently I too
have been able to do what I want with the TDI compiler. Now that I have enough
ram to keep the M2 modules in memory I am also impressed with the speed. It
isn't that much slower than a large link on a Sun — and I use a Sun 4
workstation at the office.
Kevin
It's true that the TDI compiler is NOT a "totally unusable product" but it
certainly does (did?) have it's share of flaws; many of which should have been
caught before the product was shipped. The fixes I posted here were sent
(verbally) to TDI in Dallas. A few weeks after that I received a new set of
disks and there were the same errors. I'm assuming that they didn't ignore my
comments, just that the word didn't get to the right folks. I think one of the
problems they have is writing code for both the ST and the Amiga and assuming
it will work well in both environments. That apllies to the utilities such as
the editor and debugger. Everyone had the same problems so it wasn't a matter
of bad copies or whatever. Those things should have worked properly from day
one. I haven't written all that much code either but I steal C code like crazy
and translate it. I never had any real problems that I can remember. Anyway,
I've gotten so accustomed to the TDI system that I haven't been inclined to
switch.