From: Michele Martone <michelemartone@users.sourceforge.net>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: cocci@inria.fr
Subject: Re: [cocci] EBNF for Coccinelle file formats?
Date: Mon, 11 Nov 2024 17:12:32 +0000 [thread overview]
Message-ID: <20241111171232.GE10291@localhost> (raw)
In-Reply-To: <1ecbac88-9afe-42a4-bb46-de3abe59b500@web.de>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On 20241111@18:01, Markus Elfring wrote:
> >> Will grammar descriptions become available as extended Backus–Naur
> >> form for involved input files?
> >
> > Such descriptions would have half a thousand of productions
> It is probably unclear how big a related grammar would become.
> > and still be incomplete,
If you
grep '^[a-z_]*:'
through the *.mly files you get a few hundred non-terminals,
each with a handful of production rules.
In a few words: LOTS of rules.
> Can such a development concern be clarified better?
>
> > because missing token-level
> > manipulations, which escape that notation.
>
> Which details would you find problematic so far?
As I wrote:
"because missing token-level manipulations, which escape
that notation." ("that" referring to BNF forms)
> > Would that be desirable?
>
> Would you dare to look for alternatives besides tools like
> “ocamlyacc” and “Menhir”?
Not now: not enough resources for that.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-11-11 17:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 13:14 [cocci] EBNF for Coccinelle file formats? Markus Elfring
2024-11-11 16:24 ` Michele Martone
2024-11-11 17:01 ` Markus Elfring
2024-11-11 17:12 ` Michele Martone [this message]
2024-11-11 17:19 ` Markus Elfring
2024-11-11 17:31 ` Michele Martone
2024-11-11 17:36 ` Markus Elfring
2024-11-11 17:59 ` Michele Martone
2024-11-12 6:36 ` Markus Elfring
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241111171232.GE10291@localhost \
--to=michelemartone@users.sourceforge.net \
--cc=Markus.Elfring@web.de \
--cc=cocci@inria.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.