[m-dev.] diff: bootstrap problem with init files in hlc grade

[Zoltan Somogyi]

On 08-Nov-2000, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> Well, that might justify having the functions generated.
> But it doesn't justify them having non-empty contents.
> In particular the calls to MR_init_entry() that do nothing go against
> the MLDS philosophy of not relying on macros and #ifdef.

Where is this philosophy documented? I couldn't find it.

> Also the stuff fooling around with `static int initialized' certainly
> doesn't improve the readability.

I don't know what "fooling around" refers to.

If you want to make the contents of the mercury__<module>__init function
physically empty in grades in which its contents would be #defined to the empty
string anyway, go ahead, but you should document the double maintenance
required.

Zoltan.
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------