Forum unknown
· Modula-2
#Contd.. Modula-2/Amiga
5 messages in this thread
Since I seem to have started the thread that produced the flames (TDI bug)
that led to this more rational thread I'd like to throw in my comments.
Despite all the bug reports on the modules that have been flying around I've
not been bitten seriously since the original InOut problems. I've had a few
hassles with the spec changes but nothing I couldn't fix with a glance at the
DEF's (which is what they are for). The compiler has occasionally been
irritating, like the problem with not getting a nice exit code but it doesn't
crash my machine even with expanded ram. On the other hand I do keep getting
odd GURU's with Manx 3.4a, the development environments are identical except
for the different libraries in the VDK: disk.
Overall I've found that I can develop software of good quality with TDI and,
after porting the code to C, license it into a production ennvironment. Maybe
I'm not ambitious enough, I certainly avoid the low-level Amiga stuff (under
Intuition and the basic graphics calls).
The package could certainly be improved but for the price it has been useful
and I've no regrets. Compare it with Borlands much advertised (in 1985,6)
Turbo Pascal for the Amiga.
Kevin
I feel that the price TDI gets for the "regular" version is fairly
reasonable. But the cost for the other two versions are a bit out of line for
what you get. I haven't had all that much trouble with the product either. I
use the compiler and linker from a batch file using a rather larger "FAILAT"
code with no problems. Most of the later bugs they introduced are by and
large avoidable. If one isn't used to the system/language, though, it could
be quite a problem trying to figure out if it's the program or the system
causing the problem. Sounds like Phil Camp is going to try and get it all
fixed up. Too little, too late maybe?
I have had a copy of TDI(um) since the first version of the Modula-2
compiler. I think that there are basic problems with the compiler. I have
the developer version and it still crashes and GURUs. There are still
programs that I have written in TDI(um's) Modula-2 compiler that just won't
compile. Some that just won't execute!
It is one thing for TDI to say hey we're new and we're here to help. It is
another to actually supply that help to your customers whom you have treated
VERY POORLY! When you finally put out a working product I would like to see
it. But I probably won't use it, since I will have converted everything to
some other compiler by then. Could you guys please attempt to inform people
of the changes of the compiler AFTER you have gone through some quality
control?
These comments are meant for TDI folks. But sent with the rest of these
replys, to encourage the "customers" of TDI to shoot back! I do appreciate
you giving my chance!
I have had a copy of TDI(um) since the first version of the Modula-2
compiler. I think that there are basic problems with the compiler. I have
the developer version and it still crashes and GURUs. There are still
programs that I have written in TDI(um's) Modula-2 compiler that just won't
compile. Some that just won't execute!
It is one thing for TDI to say hey we're new and we're here to help. It is
another to actually supply that help to your customers whom you have treated
VERY POORLY! When you finally put out a working product I would like to see
it. But I probably won't use it, since I will have converted everything to
some other compiler by then. Could you guys please attempt to inform people
of the changes of the compiler AFTER you have gone through some quality
control?
These comments are meant for TDI folks. But sent with the rest of these
replys, to encourage the "customers" of TDI to shoot back! I do appreciate
you giving my chance!
I feel that the price TDI gets for the "regular" version is fairly
reasonable. But the cost for the other two versions are a bit out of line for
what you get. I haven't had all that much trouble with the product either. I
use the compiler and linker from a batch file using a rather larger "FAILAT"
code with no problems. Most of the later bugs they introduced are by and
large avoidable. If one isn't used to the system/language, though, it could
be quite a problem trying to figure out if it's the program or the system
causing the problem. Sounds like Phil Camp is going to try and get it all
fixed up. Too little, too late maybe?