[m-rev.] Add `.' as a module separator.

Fergus Henderson fjh at cs.mu.OZ.AU
Tue Dec 3 19:13:16 AEDT 2002


On 03-Dec-2002, Ralph Becket <rafe at cs.mu.OZ.AU> wrote:
> @@ -3899,18 +3901,20 @@
>  
> -Currently we also support @samp{__} as an alternative module qualifier,
> -so you can write @code{module__name} instead of @code{module:name}.
> -We are considering changing the module qualifier from @samp{:}
> -to @samp{.} in a future version, so that we can use @samp{:} as
> -a type qualifier instead.  Hence for the time being we recommend
> -that you use @samp{__} rather than @samp{:} as module qualifier.
> +Currently we also support @samp{__} and @samp{:} as an alternative
> +module qualifier,

s/an alternative/alternative/
s/module qualifier/module qualifiers/

> +We are considering changing the use of @samp{:} to being a type
> +qualifier instead in a future version.
> +Hence for the time being we recommend
> +that you use @samp{.} rather than @samp{:} as module qualifier.

Delete "for the time being".

>  Certain optimizations require information or source code for predicates
>  defined in other modules to be as effective as possible.  At the moment,
> @@ -4057,7 +4061,7 @@
>  Each of the named sub-modules in an @samp{:- include_module} declaration
>  must be defined in a separate source file.
>  The mapping between module names and source file names is
> -implementation-defined.  (For a module named @samp{foo:bar:baz},
> +implementation-defined.  (For a module named @samp{foo.bar.baz},
>  The University of Melbourne Mercury implementation requires the source
>  to be located in a file named @file{foo.bar.baz.m}, @file{bar.baz.m},
>  or @file{baz.m}.) 

That part of the language reference manual is no longer correct;
it's been made obsolete by the following NEWS item:

 | * The Mercury compiler can now handle arbitrary mappings from source files
 |   to module names.  If the program contains modules for which the source
 |   file name does not match the module name, before generating the
 |   dependencies the command `mmc -f SOURCES' must be run, where `SOURCES'
 |   is a list of the names of all of the source files.  If the names of the
 |   source files all match the contained module names, `mmc -f' need not be
 |   run.
                                                                                
This problem is not a result of your change, though.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
The University of Melbourne         |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------



More information about the reviews mailing list