From: Patrick McHardy <kaber@trash.net>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: POM Xtables???
Date: Tue, 01 Jul 2008 16:10:30 +0200 [thread overview]
Message-ID: <486A3AD6.7040905@trash.net> (raw)
In-Reply-To: <486A39BF.4090206@riverviewtech.net>
Please don't trim CC lists.
Grant Taylor wrote:
> On 07/01/08 06:43, Patrick McHardy wrote:
>> As for the argument of parsers that might not handle this: any parser
>> needs to expect new things to be added at the end of the line...
>
> *LOL*
>
> Now you are expecting people to do what they should verses what is easy.
>
> Unfortunately, what is considered best practice (at the time) is not
> followed often enough.
We had multiple format extensions over time, you would hope
that people learn from their mistakes. Using scanf or a
lexer+scanner its probably impossible to even make this mistake,
assuming some perl parser someone would have to specifically
match on the (completely useless for parsing purposes) end of
line.
In any case, its unreasonable to expect us to never *extend*
(not change) the output to accomodate buggy parsers. This is
by the way the same way that is often used to extend binary
structures, even though someone stupid might use exact size
checks.
next prev parent reply other threads:[~2008-07-01 14:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 17:54 POM Xtables??? Dave
2008-06-27 18:58 ` Jan Engelhardt
2008-06-27 20:08 ` Dave
2008-06-27 21:16 ` Jan Engelhardt
2008-06-29 2:20 ` Grant Taylor
2008-06-30 16:04 ` Dave
2008-06-30 16:20 ` Patrick McHardy
2008-06-30 20:46 ` Jan Engelhardt
2008-06-30 20:52 ` Patrick McHardy
2008-07-01 9:43 ` Jozsef Kadlecsik
2008-07-01 9:46 ` Patrick McHardy
2008-07-01 11:38 ` Jan Engelhardt
2008-07-01 11:43 ` Patrick McHardy
2008-07-01 11:50 ` Jan Engelhardt
2008-07-01 11:57 ` Patrick McHardy
2008-07-01 14:05 ` Grant Taylor
2008-07-01 14:10 ` Patrick McHardy [this message]
2008-07-01 14:27 ` Grant Taylor
2008-07-01 14:34 ` Patrick McHardy
2008-07-01 14:30 ` Jan Engelhardt
2008-07-23 20:19 ` Jan Engelhardt
2008-07-23 23:21 ` Patrick McHardy
2008-07-24 8:31 ` James King
2008-07-24 9:21 ` Pablo Neira Ayuso
2008-07-24 9:43 ` Patrick McHardy
2008-08-15 8:17 ` James King
2008-08-19 11:35 ` Brent Clark
2008-08-15 8:48 ` James King
2008-06-30 21:11 ` Jozsef Kadlecsik
2008-06-30 21:47 ` Jan Engelhardt
2008-07-01 10:00 ` Jozsef Kadlecsik
2008-07-01 11:19 ` Jan Engelhardt
2008-06-30 20:18 ` Jan Engelhardt
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=486A3AD6.7040905@trash.net \
--to=kaber@trash.net \
--cc=gtaylor@riverviewtech.net \
--cc=netfilter-devel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox