[m-dev.] include in Mercury.options

[Simon Taylor]

On 25-Jan-2007, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> Currently this doesn't work because the compiler doesn't treat includes in
> Mercury.options files as being relative to the directory in which the 
> options
> file currently being processed is in but rather as being relative to the
> directory in which mmc was invoked.  (Incidentally, this is also the
> behaviour that GNU make has with similarly structured makefiles.)
> 
> I would like to change the way the compiler treats include directives
> so that it would include Mercury.options files relative the the .options
> file currently being processed.  This seems to be a more useful behaviour.
> Can anyone think of any problems with this proposal?

The include directive is compatible with Make so that Mercury.options
files can be included from M(m)akefiles without surprises.  I would
have no problem with you adding a different include directive that
works the way you want.

Simon.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au
--------------------------------------------------------------------------