Re: Issue: references to an external grammar

What I refer to below as <export> should probably be called <parentDefine> 
since is has the same relationship to <define> that <parentRef> has to 
<ref>.

--On 14 July 2001 08:23 +0700 James Clark <> wrote:

> Another possible approach to this is to allow <grammar> inside <grammar>
> and add a new <export> element.
>
> <grammar>
> ...
> <grammar>
>   <export name="foo"> p </export>
>   ...
> </grammar>
> ...
> </grammar>
>
> is equivalent to
>
> <grammar>
> ...
> <define name="foo">
>   <grammar>
>      <start>p</start>
>      ...
>   </grammar>
> </define>
> ...
> </grammar>
>
> except, of course, that you can multiple exports in a single <grammar>.
>
> You wouldn't be able to have both an <export> and a <start> in the same
> <grammar>.  An <export> inside an <include> would replace a <start> in
> the included file and vice-versa.
>
> James
>
>
>
> ------------------------------------------------------------------
> To unsubscribe from this elist send a message with the single word
> "unsubscribe" in the body to: 
>
>