All,
I am using modules 3.1.4. I have a module file, standard, that has
several module load commands in it. If some of the modules which are
loaded by the 'standard' module are not present, the modulecmd program
will sometimes delete the setenvHashTable after the module load
command fails. This appears to happen only when the version of the
module file being loaded is _NOT_ specified. The result of this is
that not all the environment changes make it into the calling
environment. In fact only those which happened after the last
Tcl_DeleteHashTable() call.
I know I could fix this by supplying the rest of the module files (and
I will eventually), but it seems to me that the hash table should
never be deleted on a failed module load command.
I would be glad to supply more information on this issue.
Thanks.
Eric
|