[mercury-users] Help: generic tree predicates; modules

[Simon Taylor]

On 09-May-2002, Bob McKay <bob_mckay at mac.com> wrote:
> Hi folks; I'm just getting my feet wet(ter) with mercury, and I have
> a couple of questions which I can solve, but maybe there are easier
> ways (this is in the context of a generic evolutionary computation
> system that Raymee Chau and Daryl Essam have previously posted about).

> .I'd like to segment the source into different directories (currently
> 	it's all in one flat directory structure). I'm doing it using
> 	libraries, but this involves creating libraries (for
> 	example, for the problem-specific code) whose only purpose
> 	is to permit the code to reside in a separate directory.
> 	Is this the intended method for splitting up Mercury code?

Recent release-of-the-day versions of the Mercury compiler allow
user-specified mappings from module names to file names.
If your source files are in subdirectories `dir1' and `dir2'
of the current directory, you would run the command
`mmc -f dir1/*.m dir2/*.m' to generate the mapping, and then
run `mmake main_module.depend' and `mmake main_module' as normal.

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