CompuServe Messages

There is a method that works somewhat like SetFunction that has been talked about around CBM. Basicly what it does is to leave a small stub of code in memory that contains the vulnerable portion of the routine. While this method does prevent the possibility of crashing, it does have a few non-fatal problems. First, if there are a large number of these installed, there is a definate chance of badly fragmenting memory, especially on a 512K machine. Second, these routines work well for allowing the programmer access to the data being passed to the library function, but cause problems if you want to replace the function. (the idea was to allow multiple 'Wedges' into the lib function, a replacement would confuse any other 'Wedges' installed. They would also be sensitive to installation order.)