There are some subtleties you need to watch out for, though. Even if your submanager retention time is zero (meaning that submanager processed don't "hang around" waitinf for more work to do before they quit), the amount of time a task takes to run is, in principle, unlimited. Most tasks do a single finite piece of work and quit, but you occasionally see long running tasks, and though you wouldn't get an error under GTM just because the code was modified, your task may continue running the wrong code for a long time. Another point, though is that having a submanager live for a long time isn't necessarily bad, because control will return to the submanager after it finishes running the application code. Now, Bhaskar can probably shed some light on how code caching might work in a situation like this, but it should be easy enough to devise a test. Write a routine that runs a long time, repeatedly calling another routine. Something like
FOR I=:1:3600 DO .DO MSG^ZZHELLO .HANG 1 QUIT In another routine (ZZHELLO) write something like MSG ; WRITE !,"Hello, there!" Now, set the first routine running in one window, and in another modify the other to write out a different message. Does the output (in the first window) change? === Gregory Woodhouse <[EMAIL PROTECTED]> "All truth passes through three stages: First, it is ridiculed. Second, it is violently opposed. Third, it is accepted as being self-evident." --Arthur Schopenhauer ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
