From: swedebugia <swedebugia@riseup.net>
To: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Re parse-result
Date: Thu, 17 Jan 2019 10:56:51 +0100 [thread overview]
Message-ID: <87bm4fhajg.fsf@riseup.net> (raw)
In-Reply-To: <257748e7-bc56-573d-c691-c1655947be2a@gmail.com> (Zelphir Kaltstahl's message of "Thu, 17 Jan 2019 08:43:01 +0100")
Hi Swedebugia,
I did not notice a PEG parser has been added. How did you notice this?
Maybe there is another blog for new additions to Guile?
Do you know a good text, which explains differences between the
different approaches to parsing? For example, what is the difference
between PEG parsing and parser combinators? There seems to be a whole
jungle of approaches to parsing out there, including parser generators,
which I believe take a grammar of certain kind and produce a parser from
that. I am never sure what languages I can parse using what approach.
Thanks anyways!
I heard about the PEG addition from Ricardo who mentioned it in
guix-devel. It also is one of very few features who got a nice tutorial
in the guile manual which I read a lot in.
Unfortunately I don't know a good comparison, but I believe PEG is somewhat
superior to guile-parser-combinators.
next prev parent reply other threads:[~2019-01-17 9:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.109.1547658023.1050.guile-user@gnu.org>
2019-01-16 20:31 ` Re: parse-result (Catonano) Zelphir Kaltstahl
2019-01-16 21:47 ` tomas
2019-01-17 7:16 ` swedebugia
2019-01-17 7:43 ` Re parse-result Zelphir Kaltstahl
2019-01-17 9:56 ` swedebugia [this message]
2019-01-17 10:49 ` tomas
2019-01-19 13:23 ` Zelphir Kaltstahl
2019-01-20 8:32 ` tomas
2019-01-20 11:35 ` Zelphir Kaltstahl
2019-01-17 19:47 ` John Cowan
2019-01-16 20:34 ` Tangerine Edition penultimate report: how I voted, how you're, voting (John Cowan) Zelphir Kaltstahl
2019-01-20 2:24 ` John Cowan
2019-01-20 12:02 ` Arne Babenhauserheide
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=87bm4fhajg.fsf@riseup.net \
--to=swedebugia@riseup.net \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@gmail.com \
/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).