> Changing an environment variable in a process would not affect the same > variable in the parent and other children's environment.
Thanks, I did not realize that. > The good old > VAX/VMS system developed by DEC had system wide environment variables > but they had no locking mechanism and updating them required specific > privilege usually not granted to the application level. And even if you > foolishly granted this privilege you had the problem of finding a way to > synchronize the access to them through some locking mechanism, which > would bring you back to the problem of finding a consistent IPC > mechanism. > But after all I didn't understand how you hoped to get system wide > symbols by using Tcl global variables I tough of environment variables just as a mean to work to share data across child instances without using disk or more complex IPCs. Not all applications need data access locking. Mine doesn't, because it has a single "writer" updating the variable data. <i>Always striving to honor my word and commitments</i> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
