On Wed, 29 Sep 2004, Jeremy C B Nicoll wrote:
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
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.
And would fail on any system that doesn't have IfThere present.
You could expand the current logic to do that too.
Care to submit a patch (preferably one that works on a vanilla 3.1
Maybe it'd be more efficient if the whole of the code to test if
module needed to be loaded/was present to be loaded/had loaded ok/else
useful message was encapsulated in a small utility?
Great, that "solves" the "problem" for NetSurf but not for any other
out there (and you'll find the vast majority do exactly the same thing as
NetSurf does at present).
To be honest, I see little point in spending time on this. If the user
can't be bothered to at least read the download page and ascertain the
requirements (which are extremely clearly documented), I can't be bothered
to provide a fix for such a trivial issue. Either way, the error message
details the problem exactly (not necessarily in user-friendly language
but that's hardly an issue - "all" they've got to do is quote it
to the developers).
Also bear in mind that a release version of NetSurf would have the
appropriate modules bundled with it (though the user might not bother to