[m-rev.] for review: tighten up checks for invlaid grade in mgnuc script etc

Julien Fischer jfischer at opturion.com
Fri Apr 24 09:46:01 AEST 2015

Hi Zoltan,

On Thu, 23 Apr 2015, Zoltan Somogyi wrote:

> On Thu, 23 Apr 2015 10:26:36 +1000 (AEST), Julien Fischer <jfischer at opturion.com> wrote:
>>> and its helpers out of the user guide and into a separate document;
>>> I think we can reduce confusion by moving the documentation for mmake
>> Agreed.   The main reason I think we haven't done that is (1) the
>> replacement documentation for "mmc --make" is not really up to scratch
>> and (2) a lot of the documentation for "mmc --make" is tangled up with
>> that of mmake.
> I agree that the documentation of grades needs to be improved, and that
> this documentation should be common for mmake and mmc --make. However,
> not having documentation of grades in the user guide is a bad idea.

No-one is proposing moving any documentation concerning grades out of
the user's guide.  (Indeed, if various threads on the users list over
the years are anything to go by, there should be more of it and it
should be in a more prominent place.)

> Move it to a separate file if you must, but only if you can include a (possibly
> processed) version of it in the user guide.
>>> and, to a lesser degree, moving the helper scripts out of the main bin
>>> directory and into lib/mercury/bin or something.
>> I have an alternative suggestion, which is that we simply don't install
>> mmake (and its associated dependencies) by default.
> I would object to that. I still use mmake. It is still more controllable
> for diagnosing problems than mmc --make.

Fair enough.  Are you also objecting to Peter's proposal?

Out of curiosity: are there features missing from mmc --make that would
make it as controllable for diagnosing problems as mmake?


More information about the reviews mailing list