CompuServe Messages

I am happy to hear that TDI is changing for the better. I do agree with Kevin that TDI's price/value ratio is very good. Look for my disks in the mail soon. It looks like I will be taking a second look at TDI when I get back 3.01b. A question for Kevin- If you've developed working programs in M2 why go to the pain of porting them to C? TDI's runtime license policy is very generous (read, free as long as you make mention of them), so…? I also agree with Kevin, I much prefer a more rational level of discussion. Now for one more thing. Although this would be a major project, TDI's system would be much more useful for development if there were *some* way to link with standard Amiga object code. Either through a Linker able to handle both formats, or a utility to convert TDI .lnk files to .o files and like Link with ALink (yuck) or BLink. With all the wonderful libraries popping up, like ARP and the various other things, it would be far easier to just link with libraries or .o(bject) files instead of having to port source (or use lots of CODE statements). A conversion utility would probably be most in line with your goal of a common compiler accross different machines. Also, some greater speed in the compile/link cycle would help. Even with M2: on a 28ms Miniscribe 8425 hard drive a moderate set of imports can take over a minute or two. The linker seems to take an exceptionally long time to generate the load file (does this have to do with differing object code formats between TDI and the Amiga executables?). Well, keep going, Mark Gooderum 76622, 2717 Disclaimer: Going to and working for but in no way taking seriously the University of Kansas and Academic Computing Services. P.S. Glad you are done being ill, seriously.