From: Hendrik Tews <tews@tcs.inf.tu-dresden.de>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: "nested" parsers
Date: Fri, 3 Dec 1999 14:31:03 +0100 [thread overview]
Message-ID: <199912031331.OAA13008@ithif20.inf.tu-dresden.de> (raw)
In-Reply-To: <38467330.86DA3330@inrets.fr>
Georges Mariano writes:
Date: Thu, 02 Dec 1999 13:25:04 +0000
Subject: "nested" parsers
It appears that we can divide the language L in a few "sub"-languages.
Let's say that L3 <: L2 <: L1 = L ('<:' included in )
And we would like to have one entry point for each language
in our parser.
ocamlyacc generates a parsing function for echa start symbol that
you declare in the grammar file. Therefore the easiest way (if
possible) is that you rewrite your grammar, such that for each of
the languages Ln you have one metasymbol, which generates this
language. Then you include several start directives in the header
of the grammar file.
Bye,
Hendrik
next prev parent reply other threads:[~1999-12-03 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-02 13:25 Georges Mariano
1999-12-03 13:31 ` Hendrik Tews [this message]
1999-12-03 18:18 ` skaller
1999-12-03 14:32 ` Remi VANICAT
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199912031331.OAA13008@ithif20.inf.tu-dresden.de \
--to=tews@tcs.inf.tu-dresden.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).