CompuServe Thread

#TDI "UPGRADES"

11 messages in this thread
#115891From: Mar 27, 1988 12:25 PM
Erv, Is it the 3.00b version ? I received that one in September last year and no file dates were more recent than January 1987. Regards, J0RGEN
#116017From: Erv ThompsonMar 27, 1988 9:47 PM
Only occasionally do they change a date when changing a file. It'd be a nice way to keep track. The problems I've found are rather minor – unless you just happen to need to use a procedure with a bug in it. If found problems with a handfull of procedures and am uploading the
#116114From: Mar 28, 1988 12:14 PM
My compiler displays the version no 3.01a and unfortunately they reintroduced the bug from 2.00: writing randomly into memory just a few instructions prior to exiting the compiler. In 2.00 it usually destroyed the system time. Now it GURUs quite often. J0RGEN
#116186From: Kevin NorthoverMar 28, 1988 9:27 PM
I received my disks today, they also say 3.01a. Problem is after I complained at TDI last November I got a set of disks which said 3.01a !! 🙁 I couldn't get that one to behave nicely, it didn't like compiling out of ram:, vdk: … The latest one is slightly differ, different file dates, different file sizes. I haven't had time to run it and I doubt I will if it has this GURU bug. My customer wants C source so it's back to Manx, pity I prefer developing in Modula but I can't afford so many crashes or three or more compilers.
#116237From: Erv ThompsonMar 28, 1988 10:43 PM
I haven't had too many gurus from the compiler but the linker sometimes exits quite rudely. I'm running it all from VD0: so that may have something to do with it. The editor, I finally found out, looks for syntax.ind in the C: dir. I just took a peek; the compiler still says "3.01a" but the byte count is different than the previous "version" I received.
#116539From: Mar 30, 1988 3:20 PM
Oh, you also noticed the Linker GURUs. It is my theory, that they use the same code for exiting the compiler and now also the linker, and that it has a bug in it. I am compiling from my HD. My compiler size is 162904 bytes (3.01a).
#116755From: Erv ThompsonMar 31, 1988 6:37 AM
The compiler file in the "newest" release is now 163252 bytes. Each time I receive new disk from TDI the compiler and linker files sizes are different than the previous. Never a mention of changes, though.
#116920From: Mark OlbertMar 31, 1988 10:52 PM
Pardon the interruption, but I wonder if that could be why GOMF2 keeps flagging a low memory trash error when I run the compiler… >>>>Mark>>>>
#116132From: Steve FaiwiszewskiMar 28, 1988 5:09 PM
Hey J0ergen! Are you back in the States, or are you calling from Europe? – Steve –
#116537From: Mar 30, 1988 3:16 PM
Nope, I am not back in the States. Actually I am "back" in Copenhagen, Denmark, which explains my only occasionally leaving a message here.Reaching across the "pond" is not exactly low-cost !
#117007From: Steve FaiwiszewskiApr 1, 1988 2:07 PM
Have you checked out the Benchmark M2 compiler yet? Blows TDI a-w-a-y-y-y… – Steve –