Modules 3.1.0b modules with "case" statement

[John M. <jo...@sy...>]

Hi,

I have been using modules for a long time and recently ran into a problem
with the Modules 3.1.0b version of modules on Linux. When I use Modules
2.2beta with a module file that has a case statement it seems to work fine.
In the example below the case statement parses out a piece of the "uname"
and sets variables accordingly.

When I use 3.1.0b it seems that the module file will not work with the case
statement unless the case is only for Linux.

Has anyone else seen this behavior ?


Sample code:

case $env(OS_TYPE) {
  { "Linux.2.2*" } {
set arch intel_i686_linux_2.2
  }
{ "SunOS.5.*" } {
set arch sun_sparc_solaris_5.5.1
  }
}
        prepend-path PATH           /path/$arch