From: Alexander Holler <holler@ahsoftware.de>
To: Patrick McHardy <kaber@trash.net>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
netfilter-devel@vger.kernel.org,
Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>,
Eric Leblond <eric@regit.org>
Subject: Re: [PATCH v2] parser: add kludges for "param-problem" and "redirect"
Date: Mon, 06 Apr 2015 10:44:38 +0200 [thread overview]
Message-ID: <55224776.4040108@ahsoftware.de> (raw)
In-Reply-To: <20150406015128.GA20515@acer.localdomain>
Am 06.04.2015 um 03:51 schrieb Patrick McHardy:
> On 05.04, Alexander Holler wrote:
>> Am 05.04.2015 um 14:11 schrieb Patrick McHardy:
>>> On 05.04, Patrick McHardy wrote:
>>
>>>> Basically this involves splitting the expression types into lhs (non-const)
>>>> and rhs (const) parts. Keywords on the RHS side can be caught using an
>>>> error statement and deferred to resolution during runtime.
>>
>> Sounds like trial and error. ;)
>
> The approach is, the patch isn't, it changes the grammar to have
> these kinds of errors in a defined state. The patch I sent
> however is, but I'm quite sure i understand the implications.
Just to mention it, there is still the possibility to define and use
keywords for all the icmp type names.
next prev parent reply other threads:[~2015-04-06 8:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 7:58 nft parser and problems with icmp type names (redirect and param-problem) Alexander Holler
2015-04-01 13:15 ` Alexander Holler
2015-04-03 17:50 ` [PATCH] parser: add kludges for "param-problem" and "redirect" Alexander Holler
2015-04-03 18:06 ` Alexander Holler
2015-04-04 10:50 ` Alexander Holler
2015-04-04 11:13 ` [PATCH v2] " Alexander Holler
2015-04-04 11:55 ` Pablo Neira Ayuso
2015-04-04 12:30 ` Alexander Holler
2015-04-05 11:42 ` Patrick McHardy
2015-04-05 11:32 ` Patrick McHardy
2015-04-05 12:11 ` Patrick McHardy
2015-04-05 19:07 ` Alexander Holler
2015-04-06 1:51 ` Patrick McHardy
2015-04-06 8:44 ` Alexander Holler [this message]
2015-04-06 9:01 ` Alexander Holler
2015-04-06 9:14 ` Alexander Holler
2015-04-06 11:25 ` Patrick McHardy
2015-04-06 20:41 ` Alexander Holler
2015-04-09 10:52 ` nft parser and names for constants (was [PATCH v2] parser: add kludges for "param-problem" and "redirect") Alexander Holler
2015-04-09 11:07 ` Patrick McHardy
2015-04-09 17:50 ` Alexander Holler
2015-04-09 19:15 ` Patrick McHardy
2015-04-10 5:38 ` Alexander Holler
2015-04-06 7:12 ` [PATCH v2] parser: add kludges for "param-problem" and "redirect" Arturo Borrero Gonzalez
2015-04-06 11:23 ` Patrick McHardy
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=55224776.4040108@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=arturo.borrero.glez@gmail.com \
--cc=eric@regit.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 NNTP newsgroup(s).