CompuServe Thread

My version is 3.01a and yes I do have expaned memory. Come to think of it, the TDI stuff didnt GURU until I added my Starboard II this spring. For you memory eating try checking the allocation/freeing for the main buffer. On smaller files, the memory lost is always equal to the size of the file when I exit the editor. I understand your point about the problems with keeping you product generic. Take a look at my suggestion about using the FD files to update the Amiga bindings. Since they contain ALL the information needed to call a routine for ALL the system calls, if you take that route it doesn't matter how much Commodore messes with the offsets. Keep in mind although that 1.3 is minor, from what most people have heard, 1.4 is going to be such a major revision that your can guarentee problems. You could also look at amiga.lib. Although the original version would have to be licensed from Commodore, there are some PD versions that are smaller who's authors would probably be happy to work with you. What do I need to do to get 3.01b? Just send in my disks with a cover letter? I see your point about the cost of ring binders. However, shipping them with new products at a slightly higher price to cover the cost and making revised documentation available to previous owners for a small fee (say $10) would be a step in the right direction, especially to placate existing ticked off customers. Also if TDI HAS changed for the better (just what is going on, new management?) PUBLICIZE it! I didn't know anything was up until I stumbled accross it here a couple days ago. Also, most of your customers DONT have Compuserve so let them know that TDI has 'changed'. As for my comment about LONGREALs I am fuzzy on that one since it is Rick Pim who so precisely illustrated the problems. He even had an instance where the value of a variable changed somewhere in 6-7 lines of code where it wasn't even referenced. For the problems with typing, I think (cant say for sure since I have Developers and not commercial (ser no. 09859)) that the problems with foo I think the problem is with some system structure pointers being declared as ADDRESSes and some as say POINTER TO FooStructure and the compiler being inconsistant with whether assignment is okey-dokey. However in the case with FooMessage:=WaitPort(FooPort); both FooMessage and FooPort are MessagePtr(s) but sometimes this works and sometimes it doesn't. (This was orginally reported by Rick Pim also.) Lloyd Blankenship at Southwest Texas State University is another person who has long detailed problem lists. (Although he might shoot you on sight, he almost blew a big project and had to purchase Lattice at the last minute because of problems with TDI.) Overall, I think a lot of the problem has to do with inconistancies in the Amiga Modules. TRY to get your modules to match the RKM specs for system calls. (Mortimores Amiga Programmer's Handbook is very good in detailing how system functions are supposed to behave.) For instance I spent an hour trying to track down a problem when I discoverd that the code (ported from C) was calling OpenWindow with a POINTER to a NewWindow record, (as Commodore specifies), where TDI wanted the record itself. Although this was when I first got your product, and a good look at the .DEF file solved the problem, it is little inconsistancies like this that make life tough for a programmer. Well, good luck, Mark Gooderum 76672,2717