[m-dev.] another interface file?

Peter Wang novalazy at gmail.com
Wed Jun 3 15:41:39 AEST 2009

The java (and il) grades need to be able to expand out imported abstract
equivalence types, which is currently achieved by simply enabling
intermodule optimisation.  However this is overkill, increasing compile
times significantly, and would be very frustrating for program development.
(Also, intermodule optimisation might not be all that useful as the JVM can
do its own intermodule optimisations at runtime.)

My idea is to introduce another type of interface file, say .int4, exposing
the equivalence types which were abstractly exported in the interface (and
types necessary to make sense of those).  Unlike the other .int* files,
these would be grade dependent, as C grades don't need them.

Does anyone see problems with this idea, or have an alternative suggestion?

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