Fix a problem with the new initialise declarations and sub-modules.

Estimated hours taken: 1.5
Branches: main

Fix a problem with the new initialise declarations and sub-modules.

compiler/modules.m:
	Don't write `:- initialise' declarations to private interfaces.
	The compiler cannot read them back in and in any case child
	modules don't need to know about them.

tests/hard_coded/sub-modules/Mmakefile:
tests/hard_coded/sub-modules/initialise_parent.m:
tests/hard_coded/sub-modules/initialise_child.m:
tests/hard_coded/sub-modules/initialise_parent.exp:
tests/hard_coded/sub-modules/initialise_parent.exp2:
	Test case for the above.  (There are two expected outputs
	because the ordering of calls to module initialisers between
	a parent and its children is arbitrary.)

vim/syntax/mercury.vim:
	Highlight initialise declarations appropriately.
This commit is contained in:
Julien Fischer
2005-08-31 04:29:12 +00:00
parent 0d46d03cb8
commit 2baa270817
7 changed files with 59 additions and 7 deletions

View File

@@ -34,6 +34,7 @@ else
endif
syn keyword mercuryKeyword module use_module import_module
syn keyword mercuryKeyword include_module end_module
syn keyword mercuryKeyword initialise
syn keyword mercuryKeyword interface implementation
syn keyword mercuryKeyword pred mode func type inst solver
syn keyword mercuryKeyword is semidet det nondet multi erroneous failure