From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: git@vger.kernel.org, "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: [PATCH 3/5] wildmatch: remove NEGATE_CLASS and NEGATE_CLASS2 macros
Date: Fri, 10 Feb 2023 14:11:36 +0100 [thread overview]
Message-ID: <230210.865yc9wtkx.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <20230210075939.44949-4-masahiroy@kernel.org>
On Fri, Feb 10 2023, Masahiro Yamada wrote:
> The other glob patterns are hard-coded in dowild(). Do likewise.
> [...]
> diff --git a/wildmatch.c b/wildmatch.c
> index a510b3fd23..93800b8eac 100644
> --- a/wildmatch.c
> +++ b/wildmatch.c
> @@ -14,10 +14,6 @@
>
> typedef unsigned char uchar;
>
> -/* What character marks an inverted character class? */
> -#define NEGATE_CLASS '!'
> -#define NEGATE_CLASS2 '^'
Thanks, maybe these made sense in rsync's codebase, but...
> #define CC_EQ(class, len, litmatch) ((len) == sizeof (litmatch)-1 \
> && *(class) == *(litmatch) \
> && strncmp((char*)class, litmatch, len) == 0)
> @@ -137,12 +133,8 @@ static int dowild(const uchar *p, const uchar *text, unsigned int flags)
> return WM_ABORT_ALL;
> case '[':
> p_ch = *++p;
...as the context shows we hardcode most of these tokens.
> -#ifdef NEGATE_CLASS2
> - if (p_ch == NEGATE_CLASS2)
> - p_ch = NEGATE_CLASS;
> -#endif
Hrm, but isn't this a logic error? No it's not, because...
> /* Assign literal 1/0 because of "matched" comparison. */
> - negated = p_ch == NEGATE_CLASS ? 1 : 0;
> + negated = p_ch == '!' || p_ch == '^' ? 1 : 0;
...you're refcatoring thise while at it.
Personally I'd prefer to just see this change without this, and it came
as a surprise given the commit message.
I find the pre-image easier to read (sans the macro check, which you
should be removing).
next prev parent reply other threads:[~2023-02-10 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 7:59 [PATCH 0/5] Clean up wildmatch.c Masahiro Yamada
2023-02-10 7:59 ` [PATCH 1/5] git-compat-util: add isblank() and isgraph() Masahiro Yamada
2023-02-10 13:16 ` Ævar Arnfjörð Bjarmason
2023-02-10 16:56 ` Masahiro Yamada
2023-02-10 19:10 ` Junio C Hamano
2023-02-10 19:25 ` Masahiro Yamada
2023-02-10 22:03 ` René Scharfe
2023-02-11 7:01 ` Masahiro Yamada
2023-02-11 13:48 ` René Scharfe
2023-02-11 14:11 ` René Scharfe
2023-02-10 7:59 ` [PATCH 2/5] wildmatch: remove IS*() macros Masahiro Yamada
2023-02-10 7:59 ` [PATCH 3/5] wildmatch: remove NEGATE_CLASS and NEGATE_CLASS2 macros Masahiro Yamada
2023-02-10 13:11 ` Ævar Arnfjörð Bjarmason [this message]
2023-02-10 17:03 ` Masahiro Yamada
2023-02-10 7:59 ` [PATCH 4/5] wildmatch: use char instead of uchar Masahiro Yamada
2023-02-10 13:09 ` Ævar Arnfjörð Bjarmason
2023-02-10 7:59 ` [PATCH 5/5] wildmatch: more cleanups after killing uchar Masahiro Yamada
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=230210.865yc9wtkx.gmgdl@evledraar.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=masahiroy@kernel.org \
--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 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.