[m-dev.] implementation reserved names

Peter Wang wangp at students.csse.unimelb.edu.au
Mon Aug 14 20:09:37 AEST 2006


On 2006-08-14, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
> 
> Given that the Mercury compiler is now introducing predicates behind
> the user's back so to speak (e.g. in the implementation of constant
> mutables and (shortly) as part of the locking mechanism for mutables)
> it would be preferable if we could document that certain names should
> be avoided in user code (to avoid namespace clashes etc.)
> 
> The proposal is that all names (as defined in section 2.2 of the
> reference manual) beginning with the prefix "mercury_compiler__" would
> be reserved for implementation purposes.

What about using submodules for this? e.g. let each module have a hidden
`implementation' submodule.

Peter

--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at csse.unimelb.edu.au
Administrative Queries: owner-mercury-developers at csse.unimelb.edu.au
Subscriptions:          mercury-developers-request at csse.unimelb.edu.au
--------------------------------------------------------------------------



More information about the developers mailing list