> From: Brian > More useful is the fact that UniVerse caches > subroutine object in memory until you exit to TCL, so > the overheads on repeated calling are minimised anyway.
"useful" as long as you aren't dynamically writing/changing the code that you're calling. But then as long as the sub name isn't hardcoded you can simply compile a sub with a different name and dynamically call to the new code if required. For anyone who works with D3, the 'k' option on the compile verb tells the runtime to core-lock object modules in memory to achieve the same performance benefits described here for U2. Caching always has pros and cons, whether it's BASIC object, web pages, CSS, or some OS-level process or data. To suit our varying needs we should all have a good grasp on how to turn cache on _and_ off as required. This sort of information is elusive in this market and I've found Unidata and jBASE to be particularly problematic in this regard. Regards, T ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
