unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: 73188@debbugs.gnu.org
Subject: bug#73188: PEG parser does not support full PEG grammar
Date: Sun, 22 Dec 2024 22:22:09 +0100	[thread overview]
Message-ID: <87seqffm66.fsf_-_@gnu.org> (raw)
In-Reply-To: <20241222200128.13782-1-ekaitz@elenq.tech> (Ekaitz Zarraga's message of "Sun, 22 Dec 2024 21:01:06 +0100")

Hi Ekaitz,

Apologies for applying the wrong version of the patch series!

I pushed the 3 patches you just sent:

  6750f6cc8 * PEG: string-peg: Add HTML5 grammar test.
  38ad26497 * PEG: string-peg: Better support for escaping.
  c86a48a92 * PEG: string-peg: Fix [^...] interpretation.

I added commit logs that follow the project’s conventions (same as
Guix).

In the future, when a patch fixes a bug, please include a test case that
reproduces the bug being fixed; possibly add information in the commit
log about the commit that introduced the bug/regression.  This is useful
to get a good understanding of the situation.  (I understand in this
case the problem was mostly me applying an earlier version.)

And bonus points if you provide commit logs.  :-)

Thank you!

Ludo’.





  parent reply	other threads:[~2024-12-22 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11 22:03 bug#73188: PEG parser does not support full PEG grammar Ekaitz Zarraga
2024-09-12 20:57 ` bug#73188: [PATCH v2] PEG: Add full support for PEG + some extensions Ekaitz Zarraga
2024-10-13 20:29   ` bug#73188: PEG parser does not support full PEG grammar Ludovic Courtès
2024-10-13 20:59     ` Ekaitz Zarraga
2024-10-14 11:56       ` Ludovic Courtès
2024-10-14 14:00         ` Ekaitz Zarraga
2024-10-20 10:10           ` Ludovic Courtès
2024-10-20 20:18             ` Ekaitz Zarraga
2024-12-09 17:23               ` Ludovic Courtès
2024-10-11 12:31 ` bug#73188: [PATCH] PEG: Add support for `not-in-range` and [^...] Ekaitz Zarraga
2024-10-30 19:04 ` bug#73188: PEG: Fix bugs and add complex PEG for testing Ekaitz Zarraga
2024-12-22 17:45 ` bug#73188: PEG parser does not support full PEG grammar Ekaitz Zarraga
2024-12-22 20:09   ` Ekaitz Zarraga
2024-12-22 20:01 ` bug#73188: [PATCH 1/3] PEG: fix [^...] Ekaitz Zarraga
2024-12-22 20:01   ` bug#73188: [PATCH 2/3] PEG: string-peg: better support for escaping Ekaitz Zarraga
2024-12-22 20:01   ` bug#73188: [PATCH 3/3] PEG: add large string-peg patch Ekaitz Zarraga
2024-12-22 21:22   ` Ludovic Courtès [this message]
2024-12-23 22:04     ` bug#73188: PEG parser does not support full PEG grammar bokr
2024-12-23 22:13       ` Ekaitz Zarraga
2024-12-28 20:30         ` Bengt Richter
2024-12-28 20:44           ` 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=87seqffm66.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=73188@debbugs.gnu.org \
    --cc=ekaitz@elenq.tech \
    /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).