[m-dev.] Determining which grades an installed Mercury compiler supports

[Julien Fischer]

Hi Keri,

On Thu, 19 Jul 2018, Keri Harris wrote:

> On 18/07/2018 20:53, Zoltan Somogyi wrote:
>>
>>>  Strictly speaking, these issues are more related to bundling Mercury
>>>  with package manager than being inherent to Mercury itself. But both of
>>>  these issues make me wonder if there is a more resilient way of
>>>  determining which grades the compiler supports.
>>
>>  We could bake into the compiler the list of the grades that were
>>  configured
>>  to be installed at the time the compiler executable was itself created.
>>  However, that would still be vulnerable to parts of the install directory
>>  being overwritten later.
>
> That would certainly work. Another option would be to follow the same logic 
> as that used for C grades - look for a uniquely identifiable file belonging 
> to the std library for each non-C grade.

Commit 697b677 does that for the erlang grade.  I'll fix the
Java and C# grades shortly.

Julien.