[m-dev.] Mercury.dll one big file, or several functional areas as separate DLLS.
gluon at earthlink.net
Fri Jun 15 06:45:04 AEST 2007
Never mind. I thought the library types would be in a tree hierarchy, but
they are not.
From: owner-mercury-developers at csse.unimelb.edu.au
[mailto:owner-mercury-developers at csse.unimelb.edu.au] On Behalf Of Eric
Sent: Thursday, June 14, 2007 2:17 PM
To: Mercury Developers
Subject: [m-dev.] Mercury.dll one big file, or several functional areas as
This is just a request for some feed back on design goals of the .NET
version of the Mercury library.
Do we want a single Mercry.dll file, or several DLLs based on functionality
or something else?
I am thinking it should be broken down by functional area like with each
area being a separate DLL.
Mercury common objects: bool, char, integer, etc.
Mercury IO: IO, term, dir, etc.
Mercury collections: array, bag, list, etc
Mercury xxx: other functional areas.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the developers