possible clash between process names and O'Mega variables

[sschmidt]

When using process names that are also used as variables in the O'Mega code, e.g.

  process p1 = e1, E1 => e2, E2

O'Mega will name the module using the process name. The generated code will look like the

module p1
  ...
  type(momentum) :: p1, p2, p3, p4
  ...
end module p1

and thus lead to a compiler error.

The simplest solution should be to rename the module to <process name>_module, then no clashes should be possible (assuming there are no variables called something_module).

[sschmidt]

To quote the WHIZARD manual:

Throughout the program, the process will be identified by its process-id, so
 this is the name of the process object. This identifier is arbitrary, chosen
 by the user. It follows the rules for variable names, so it consists of
 alphanumeric characters and underscores, where the first character is not
 numeric. As a special rule, it must not contain upper-case characters. The
 reason is that this name is used for identifying the process not just within
 the script, but also within the Fortran code that the matrix-element generator
 produces for this process.

As WHIZARD doesn't obey what's written in the manual, it's definitely a defect.

[Juergen Reuter]

Done in r3677.