[m-dev.] Link before or after back end code generation.

[Peter Ross]

On 6/26/07, Eric Taucher <gluon at earthlink.net> wrote:
> I am just looking for comments and feedback.
>
> For the IL backend we currently have multiple dll files making up the
> library. To upgrade to .NET 2.0 the library is more easily created as one
> file. There are two methods that I see are possible to create the one file:
>
> After the code is converted to the IL backend form, by using illink to link
> the separate modules into one assembly.

This is what should be done.  Just a note, this is what is currently
done today for .NET 1.0, they have the extension .dll, but they are
not assemblies.

> Before the code is converted to the backend form, by merging the separate
> *.m files and then converting into the IL backend form.
>
No don't do that, otherwise you will lose separate compilation.  ie
you change one file and then you have to recompile everything, very
time consuming.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------