CompuServe Messages

I'd prefer not to encourage SetFunction whenever possible, because you never know what will happen when things get combined, or when Commodore revises the OS, or whatever. When there is any possible way to do something not using SetFunction, I'd do it … the humor in this being that both FastFonts and BlitzDisk use SetFunction, because there is no other way. Both are "safe" if other programs sit on the same vectors, and for both I spent much more time considering boundary conditions than I did writing the actual code. For shared screens, I don't think there is any safe way to guarantee existing programs with CUSTOMSCREENS will all work if you open a window in their screen, even if you do SetFunction the screen stuff … that's why I haven't done anything with TxEd on shared screens yet, because I can't support it- …cheath