CompuServe Messages

There are real problems with using the SetFunction routine that have come to light. If you are simply replacing a function, permanentaly, then there is no problem. However, if you attempt to reverse a SetFunction, chances are quite good that you'll crash the machine. (example.. You SetFunction a routine. Someone else SetFunction's it too. You then restore the old pointer value back to what it was when you got it. You have now destroyed the link to the second SetFunction.) SetFunction works fine if a developer understands the problems involved, and is willing to work around them. But what we were discussing is a procedure to allow a USER to customize their system. For that we need a much more robust and friendly solution. You know that when a user gets a new file requester, the first thing that will be done is to switch back and forth between it and the old one, just to get a feel for the new code. With SetFunction, you'd be almost gaurenteed to crash the machine. And THAT is something nobody needs.