From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH libnetfilter_queue] build: add missing backslash to build_man.sh
Date: Mon, 7 Oct 2024 14:24:27 +0200 [thread overview]
Message-ID: <ZwPS-3s2-wUcVBzU@orbyte.nwl.cc> (raw)
In-Reply-To: <ZwMi1knK7rqs+iEy@slk15.local.net>
Hi Duncan,
On Mon, Oct 07, 2024 at 10:52:54AM +1100, Duncan Roe wrote:
> On Fri, Oct 04, 2024 at 03:18:28PM +0200, Phil Sutter wrote:
> > This holds another interesting detail, though: By quoting your
> > delimiter, you may disable expansion entirely which might improve
> > readability in those ed commands?
>
> I did try quoting the delimiter when I was working on speeding up build_man.sh.
> Rather to my surprise, the used CPU went up albeit by a tiny amount. I was
> absolutely focussed on speed so left the delimiter unquoted.
That's odd - while the shell will have to unquote the delimiter, it
should have less work with the content. Are you sure this is not just
noise you were measuring?
> The CPU increase was so small that you might consider the improvement in
> readability to be worth it.
>
> But there is another possible downside to quoting the delimiter. Some of the
> here documents in build_man contain actual parameter substitution so would have
> to be left as_is, leading to inconsistent appearance of here documents.
Sure!
> I'm happy to do it either way, LMK your preference.
I don't have any, just stumbled upon this feature when checking for
when/why unescaped backslashes are interpreted or not.
Cheers, Phil
next prev parent reply other threads:[~2024-10-07 12:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 4:06 [PATCH libnetfilter_queue] build: add missing backslash to build_man.sh Duncan Roe
2024-10-04 13:18 ` Phil Sutter
2024-10-06 23:52 ` Duncan Roe
2024-10-07 12:24 ` Phil Sutter [this message]
2024-10-07 22:50 ` Duncan Roe
2024-10-12 4:08 ` Duncan Roe
2024-10-12 10:31 ` Phil Sutter
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=ZwPS-3s2-wUcVBzU@orbyte.nwl.cc \
--to=phil@nwl.cc \
--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).