From: Jeff King <peff@peff.net>
To: Pasha Bolokhov <pasha.bolokhov@gmail.com>
Cc: git@vger.kernel.org, pclouds@gmail.com
Subject: Re: [PATCH] Improve function dir.c:trim_trailing_spaces()
Date: Thu, 29 May 2014 16:13:34 -0400 [thread overview]
Message-ID: <20140529201334.GA17355@sigill.intra.peff.net> (raw)
In-Reply-To: <1401320757-9360-1-git-send-email-pasha.bolokhov@gmail.com>
On Wed, May 28, 2014 at 04:45:57PM -0700, Pasha Bolokhov wrote:
> Move backwards from the end of the string (more efficient for
> lines which do not have trailing spaces or have just a couple).
The original code reads the string from left to right. In theory, that
means we could get away with not calling strlen() at all, over a
right-to-left that must start with a call to strlen().
That being said, I think we already have the length in the calling
function, so you could probably avoid the strlen() altogether, which
makes a right-to-left function more efficient.
However, I doubt it makes that much of a difference in practice, so
unless it's measurable, I would certainly go with the version that is
more readable (and correct, of course).
> Slightly more rare occurrences of 'text \ ' with a backslash
> in between spaces are handled correctly.
Can you add a test for this?
Also, if you are refactoring this function, I think it makes sense to
check that:
"foo\\ "
and
"foo\\\ "
match "foo\" and "foo\ ", respectively (I think they do with your patch,
but it is a tricky case that is not immediately obvious).
-Peff
next prev parent reply other threads:[~2014-05-29 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 23:45 [PATCH] Improve function dir.c:trim_trailing_spaces() Pasha Bolokhov
2014-05-29 20:13 ` Jeff King [this message]
2014-05-29 21:34 ` Pasha Bolokhov
2014-05-30 2:04 ` Jeff King
2014-05-30 18:45 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2014-05-31 15:21 Pasha Bolokhov
2014-06-02 6:47 ` Jeff King
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=20140529201334.GA17355@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=pasha.bolokhov@gmail.com \
--cc=pclouds@gmail.com \
/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).