On Fri, 04 Mar 2005 18:40:55 -0500, you wrote: >Allen wrote: "Nope. Blank Common and Named Common are specific to each user >process. So, if I run a program which initializes common, any other program >run by me during that session has that data available, but that data is NOT >available to any other process." > >Allen it is my understanding that unnamed common is specific to each program >tree, not process. If you get to the TCL prompt, your unnamed common is >disgarded. Any subsequent code that is run, can not access those stored >variables any longer. > >However NAMED Command is different in that you can go to TCL and then later >into other code, and as long as you don't log out of that session, the named >common is still active and available to access what you stored in it >previously. > >So named, and unnamed, common are different imho.
You are absolutely correct. Just wrote a snippet of code under Universe Personal Edition to test it, and the named common persists across programs (as I expected), and the blank common is re-initialized in between program executions. -- Allen Egerton [EMAIL PROTECTED] ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
