Modified:
/wiki/SigSyntax.wiki
=======================================
--- /wiki/SigSyntax.wiki Thu Jun 10 13:01:18 2010
+++ /wiki/SigSyntax.wiki Thu Jun 10 13:02:37 2010
@@ -86,7 +86,7 @@
* Each signature is expected to be presented in a distinct file. This
file must have the name `<modname>.sig` where `<modname>` is the name of
the relevant module and signature. This name should also coincide with the
name indicated in the signature header, generated by the rule for
`<SigHeader>`.
- * A signature may accumulate or use another signature via an
_accum`_`sig_ or `use_sig` declaration. Before it becomes meaningful to
deem a given signature as well-formed, each of its accumulated and used
signatures should be determined to be so by the same rules that are
described in this commentary. Notice, in particular, that a modularity
principle for signatures is implied by this: each signature must be
understood independently and completely, i.e., the context of its
accumulation or use has no impact on this understanding.
+ * A signature may accumulate or use another signature via an
_accum`_`sig_ or _use`_`sig_ declaration. Before it becomes meaningful to
deem a given signature as well-formed, each of its accumulated and used
signatures should be determined to be so by the same rules that are
described in this commentary. Notice, in particular, that a modularity
principle for signatures is implied by this: each signature must be
understood independently and completely, i.e., the context of its
accumulation or use has no impact on this understanding.
* The intended effect of _accum`_`sig_ declarations is to include the
declarations in the named signatures in the signature being generated from
the text in the present file. Thus, _accum`_`sig_ functions in a manner
similar to _#include_ in C. The possible interactions between sibling
accumulated signatures and the accumulating signature are discussed further
below.