[m-rev.] for review: submodules in the same assembly

[Peter Ross]

On Thu, Aug 09, 2001 at 06:21:34PM +0200, Peter Ross wrote:
> On Thu, Aug 09, 2001 at 11:19:55PM +1000, Fergus Henderson wrote:
> > On 09-Aug-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> > > Place sub-modules in the same assembly as their parent on the IL
> > > backend.
> > > 
> > > This allowes the user to decide how their application should be
> > > packaged.  If the user wishes their application to be deployed as one
> > > assembly then they should use sub modules.
> > 
> > It would be nice to document that somewhere,
> > e.g. README.DotNet, the user guide, and/or the web page.
> > 

Index: README.DotNet
===================================================================
RCS file: /home/mercury1/repository/mercury/README.DotNet,v
retrieving revision 1.5
diff -u -r1.5 README.DotNet
--- README.DotNet       3 Aug 2001 15:01:35 -0000       1.5
+++ README.DotNet       9 Aug 2001 16:27:39 -0000
@@ -134,6 +134,10 @@
 We are working on a tool that automatically generates a Mercury interface
 for any .NET component, but it is not yet ready for public use.

+Currently each top level Mercury module is placed into its own assembly.
+For example, module.m will be placed into the assembly `module', while
+module.sub.m will also be placed into the assembly `module'.
+
 -----------------------------------------------------------------------------

 RESOURCES
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------