they used to say that globals were too volatile to rely on very long, so i have been saving to disk after each change.
I don't know if I'd call them volatile, particularly. The only danger is if another stack uses the same variable name, which would allow it to change the value when you might not expect it. If you give your globals distinctive names and don't reuse those names in other stacks, there isn't any danger. Richard's stack-naming example works well with globals too; if your stack's name is "MyStack," then prefix all its globals with "gMS" or some other identifier, which reduces the chance that some other stack will reuse it.
-- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
