[m-rev.] for review: transparent sub-module documentation

[Peter Ross]

Simon wrote:
> On 28-Nov-2001, Peter Ross <peter.ross at miscrit.be> wrote:
> This also doesn't match the final proposal -- transparent sub-modules
> are imported as if by a `:- use_module' declaration.
>
> I suggest:
> A transparent sub-module is implicitly imported as if by a
> a @samp{:- use_module} declaration whenever the parent
> module is imported
>
Why was this decided?

If you import a module using an import_module than I think you should
use the import_module semantics, or some variant thereof.  I would be
willing to enforce that the only qualifiers that you can drop from a
name are those which are explicitly mentioned by the import_module
declaration.

For example with

:- import_module mscorlib__System.

the following qualifications would be allowed

mscorlib__System__Reflection__Assembly__Load("assembly")
System__Reflection__Assembly__Load("assembly")
Reflection__Assembly__Load("assembly")

however

Assembly__Load("assembly)

would only be allowed if there was an

:- import_module mscorlib__System__Reflection.

Does that sound reasonable?

Pete

--------------------------------------------------------------------------
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
--------------------------------------------------------------------------