Module names should end in
They should have at least one and at most two underscores indicating
the module group name and subgroup name like
Contained routines are then named
Routine names should contain at least one, at most three underscores.
Thus, the name should indicate the module the routine belongs to.
Short names like
should not be used to avoid name-space pollution
and be called
Ideally, all routines should have a globally uniq name even if that
not strictly necessary because modules are never used together or
some subroutines are kept private in the modules.
The use of CamelCase for the subroutine name is encouraged.
If unit-test routines for a
are collected in a separate module
this should be called