From: Matt Wette <matt.wette@gmail.com>
To: guile-user@gnu.org
Subject: Re: Questions about PEG parsing
Date: Tue, 2 Nov 2021 05:44:06 -0700 [thread overview]
Message-ID: <189cc4ee-ec34-8b20-1b67-05a4e8b6d0c1@gmail.com> (raw)
In-Reply-To: <64ff1f637d30dcf9cf9df1c20284698ea33e9c1d.camel@planete-kraus.eu>
On 10/23/21 4:25 PM, Vivien Kraus via General Guile related discussions
wrote:
> Dear guile users,
>
> There are two ways to make a parser with guile: the undocumented
> LALR(1) parser generator, for which I don’t know how to reuse grammar
> elements, and the PEG parser.
>
I'm not sure what your needs are but in my case being not keen on the
lalr parser in Guile I ended up writing my own (for Guile).
https://savannah.nongnu.org/projects/nyacc
If you go to the "Project Homepage" there are some manuals. And the
distribution includes several examples.
Matt
prev parent reply other threads:[~2021-11-02 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 23:25 Questions about PEG parsing Vivien Kraus via General Guile related discussions
2021-11-02 0:44 ` Robin Templeton
2021-11-02 12:44 ` Matt Wette [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=189cc4ee-ec34-8b20-1b67-05a4e8b6d0c1@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).