[mercury-users] scope resolution operator

[Michael Day]

> Search for the keywords "mercury-users module qualifier" on the Mercury
> mailing list archive search, which is at
> <http://www.cs.mu.oz.au/mercury/mailing-lists/search.html>.

Ah thank you, I will have to get into the habit of Reading The Docs before
asking foolish questions.

Must admit a . module qualifier makes me a little nervous, going to have
to get used to string.append *not* being a method call acting on the
variable "string". Still I guess it fits nicely with module.sub.sub-sub.m
filenames. Incidentally a .m extension creates unending strife when GNU
tools "recognize" it as being an Objective-C file, but no doubt that's not
exactly news. Is there a way for mmc to be persuaded into accepting
filenames with arbitrary extensions? At present it assumes that foo.bar is
a module name and tacks on .m regardless... (just exploring ways to
include Mercury modules in projects making heavy use of automake).

Michael

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