From: Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
To: swedebugia <swedebugia@riseup.net>,
"catonano@gmail.com >> Catonano" <catonano@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Re parse-result
Date: Thu, 17 Jan 2019 08:43:01 +0100 [thread overview]
Message-ID: <257748e7-bc56-573d-c691-c1655947be2a@gmail.com> (raw)
In-Reply-To: <5E629D82-0023-489F-9A0A-63ACF1A520B1@pretty.Easy.privacy>
On 1/17/19 8:16 AM, swedebugia wrote:
> Zelphir Kaltstahl <zelphirkaltstahl@gmail.com> skrev: (16 januari 2019
> 21:31:13 CET)
>
> Perhaps I should put a link into the source code whenever I follow a
> tutorial. Sorry for the confusion!
>
> I am also only following Amirouche Boubekki's tutorial ; ) Good that you
> already found it.
>
> There is a paper about parser combinators (which I did not completely
> implement, because I had a bug somewhere, where I did not find it at
> some point), about parser combinators:
> http://www.cs.nott.ac.uk/~pszgmh/monparsing.pdf
>
> It takes some time to get used to the Gopher code syntax, but from the
> part of the paper, that I read, it is quite clever stuff, all this
> parser combinator stuff.
>
> I am still unsure about the theoretical CS stuff: What kind of parsers
> one can possibly write with parser combinators? Which language class is
> that? I have language X can I parse it completely using parser
> combinators? etc. Theoretical CS and the proofs were not my strongest area.
>
> On 1/16/19 6:00 PM, guile-user-request@gnu.org wrote:
>
> Ok I found this
> https://hyperdev.fr/blog/getting-started-with-guile-parser-combinators.html
>
>
>
>
> Hi.
> Have you looked at the PEG parser recently added to guile? It does
> everything the combinators do with an added compressor.
> Its quite powerful and seems to work well.
> --
> Sent from my p≡p for Android.
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!
Regards,
Zelphir
next prev parent reply other threads:[~2019-01-17 7:43 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 ` Zelphir Kaltstahl [this message]
2019-01-17 9:56 ` Re parse-result swedebugia
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=257748e7-bc56-573d-c691-c1655947be2a@gmail.com \
--to=zelphirkaltstahl@gmail.com \
--cc=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=swedebugia@riseup.net \
/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).