From: Rutger van Beusekom <rutger.van.beusekom@verum.com>
To: Ekaitz Zarraga <ekaitz@elenq.tech>,
Janneke Nieuwenhuizen <janneke@gnu.org>,
"guile-devel@gnu.org" <guile-devel@gnu.org>
Cc: Rutger van Beusekom <rutger@dezyne.org>
Subject: Re: [PATCH v2 5/5] peg: Add fall-back parsing.
Date: Wed, 16 Oct 2024 06:44:09 +0000 [thread overview]
Message-ID: <DU0PR08MB741473B7C344CFF2ABEB3A10BB462@DU0PR08MB7414.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <4c1b640b-41f8-4d74-9889-1c1d69a845be@elenq.tech>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
________________________________
From: Ekaitz Zarraga <ekaitz@elenq.tech>
Sent: Monday, 14 October 2024 17:58
To: Janneke Nieuwenhuizen <janneke@gnu.org>; guile-devel@gnu.org <guile-devel@gnu.org>
Cc: Rutger van Beusekom <rutger@dezyne.org>
Subject: Re: [PATCH v2 5/5] peg: Add fall-back parsing.
Hi Ekaitz,
> I think this change is not compatible with the PEG syntax. In PEG # is a
> line comment:
I am not attached to # as the PEG expect operator. At the same time the
expect operator is not part of https://bford.info/pub/lang/peg.pdf. I think
we should consider choosing another name for the expect operator, do you
have a suggestion Ekaitz?
I was considering "reusing" the she-bang, i.e. #!, since the expect operator
throws an exception, but Janneke pointed out that ! as a modifier on the #
comment is not very intuitive and I tend to agree.
Regtur
[-- Attachment #2: Type: text/html, Size: 3817 bytes --]
next prev parent reply other threads:[~2024-10-16 6:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:41 [PATCH] ice-9/peg: Extend PEG for production use Rutger van Beusekom
2024-10-14 7:26 ` [PATCH v2 0/5] " Janneke Nieuwenhuizen
2024-10-14 7:31 ` [PATCH v2 1/5] Remove trailing whitespace in PEG texinfo Janneke Nieuwenhuizen
2024-10-14 7:31 ` [PATCH v2 2/5] peg: Add debug tracing Janneke Nieuwenhuizen
2024-10-14 7:31 ` [PATCH v2 3/5] peg: Add expect Janneke Nieuwenhuizen
2024-10-14 7:31 ` [PATCH v2 4/5] peg: Add whitespace and comment skip parsers Janneke Nieuwenhuizen
2024-10-14 7:31 ` [PATCH v2 5/5] peg: Add fall-back parsing Janneke Nieuwenhuizen
2024-10-14 7:36 ` Janneke Nieuwenhuizen
2024-10-14 15:58 ` Ekaitz Zarraga
2024-10-16 6:44 ` Rutger van Beusekom [this message]
2024-10-18 9:58 ` Ekaitz Zarraga
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=DU0PR08MB741473B7C344CFF2ABEB3A10BB462@DU0PR08MB7414.eurprd08.prod.outlook.com \
--to=rutger.van.beusekom@verum.com \
--cc=ekaitz@elenq.tech \
--cc=guile-devel@gnu.org \
--cc=janneke@gnu.org \
--cc=rutger@dezyne.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).