[m-dev.] module system discussion

[Peter Ross]

On Mon, Nov 26, 2001 at 04:36:33PM +1100, Simon Taylor wrote:
> On 22-Nov-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> > I would really like to reach a consensus on this issue, could a decision
> > be made at the Mercury meeting on Monday?  As this is quite important to
> > the work I am doing on bringing the .NET port up to scratch.
> > 
> > I do believe that it is necessary to have one of either :- auto_import
> > or :- import_package implemented.
> > 
> > I am happy with either alternative.  I believe that the auto_import
> > mechanism should only be allowed to refer to sub-modules.
> > 
> > I am opposed to only implementing the :- include declaration, as I think
> > that there are times when you don't want that behaviour. I hope I have
> > highlighted when.  I have no objections to *also* implementing this
> > declaration.
> 
> Here's a summary of the current proposals after that discussion.
> 
> 1. `:- import_hierarchy' and `:- use_hierarchy'
> 	(formerly known as `:- import_package' and `:- use_package')
> 
> `:- import_hierarchy <module>' imports all modules in the hierarchy
> rooted at <module>.
> 
> The name has changed because we might want to use `package' to mean a
> (distributed) package of modules, rather than just any module and its
> sub-modules.
> 
> There was general agreement that this proposal is worthwhile.
> 
I will implement this today, provided no one else has done it.

Pete
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------