From: Florian Westphal <fw@strlen.de>
To: Stephen Satchell <list@satchell.net>
Cc: netfilter@vger.kernel.org
Subject: Re: BNF for nftables?
Date: Wed, 5 Feb 2020 12:42:04 +0100 [thread overview]
Message-ID: <20200205114204.GE26952@breakpoint.cc> (raw)
In-Reply-To: <416a106d-c649-7a99-0241-389ba6efdafe@satchell.net>
Stephen Satchell <list@satchell.net> wrote:
> Failing a formal lint(1) program, is there a complete BNF description of the
> language?
No, but it should be possible to extract it from the bison grammar
(src/parser_bison.y in nftables source code).
prev parent reply other threads:[~2020-02-05 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 19:25 BNF for nftables? Stephen Satchell
2020-02-05 11:42 ` Florian Westphal [this message]
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=20200205114204.GE26952@breakpoint.cc \
--to=fw@strlen.de \
--cc=list@satchell.net \
--cc=netfilter@vger.kernel.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 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.