In article <Pine.LNX.4.44.0409280201390.24573-100000@tarrant>,
John-Mark Bell <jmb202(a)ecs.soton.ac.uk> wrote:
The Run file is working exactly as it is supposed to. The command
that is creating the error message is RMLoad
System:Modules.ModuleName. You would get the same result from any
other application that expects to find modules in the System
resource.
It's a pity ... the !Run file logic is nicely written to provide useful
error messages provided that any problems with required modules are
that there's a version of something, just not the necessary level of it.
Lots of authors don't put any useful error messages in at all. And
yet, having done so, someone's found an occasion when the useful error
doesn't get produced. Yet, "IfThere System:Modules.Modulename" will
produce an indication that the RMLoad would fail. You could expand the
current logic to do that too. Maybe it'd be more efficient if the
whole of the code to test if a module needed to be loaded/was present
to be loaded/had loaded ok/else useful message was encapsulated in a
small utility?
--
Jeremy C B Nicoll - my opinions are my own.