[m-dev.] another interface file?

Zoltan Somogyi zs at csse.unimelb.edu.au
Wed Jun 10 17:08:09 AEST 2009

On 10-Jun-2009, Peter Wang <novalazy at gmail.com> wrote:
> However, when intermodule optimisation is switched off, some abstract
> equivalence types still aren't expanded properly.  Probably just bugs.

No, I don't think they are. At the moment, we include the actual type
definitions of abstract-exported types in .int files only in a carefully
restricted set of cases, just enough to avoid problems in the grades such
as hlc (not java). The rationale for that is that the more such definitions
you include, the more recompilations you force when the type definition,
and hence the content of the .int file, changes.

It seems that you want to find the place where .int files are written out,
and change the condition on WHEN you write out the definitions of
abstract-exported types.

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

More information about the developers mailing list