From: Eric Sunshine <sunshine@sunshineco.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Karthik Nayak <karthik.188@gmail.com>,
Git List <git@vger.kernel.org>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: Re: [PATCH v3 5/9] ref-filter: add option to match literal pattern
Date: Mon, 20 Jul 2015 14:12:11 -0400 [thread overview]
Message-ID: <CAPig+cSu7-wegGd90WHeppt8inHSBxrakzuJSvcRV7OocJHAgg@mail.gmail.com> (raw)
In-Reply-To: <CAP8UFD0kaqSUGMbWrim+59H8CweO-MKSyeQr+3q2cYdJ-+D-Mw@mail.gmail.com>
On Mon, Jul 20, 2015 at 4:01 AM, Christian Couder
<christian.couder@gmail.com> wrote:
> On Mon, Jul 20, 2015 at 8:24 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
>> On Sat, Jul 18, 2015 at 3:12 PM, Karthik Nayak <karthik.188@gmail.com> wrote:
>>> +static int filter_pattern_match(struct ref_filter *filter, const char *refname)
>>> +{
>>> + if (!*filter->name_patterns)
>>> + return 1;
>>> + if (filter->match_as_path)
>>> + return match_name_as_path(filter->name_patterns, refname);
>>> + return match_pattern(filter->name_patterns, refname);
>>> +}
>>> @@ -1034,7 +1057,7 @@ static int ref_filter_handler(const char *refname, const struct object_id *oid,
>>> - if (*filter->name_patterns && !match_name_as_path(filter->name_patterns, refname))
>>> + if (!filter_pattern_match(filter, refname))
>>> return 0;
>>
>> I find it much more difficult to grok the new logic due to
>> '*filter->name_patterns' having moved into the called function and its
>> negation inside the function returning 1 which is then negated (again)
>> upon return here. This sort of twisty logic places a higher cognitive
>> load on the reader. Retaining the original logic makes the code far
>> simpler to understand:
>>
>> if (*filter->name_patterns &&
>> !filter_pattern_match(filter, refname))
>> return 0;
>>
>> although it's a bit less nicely encapsulated, so I dunno...
>
> I think a comment before filter_pattern_match() and perhaps also one
> inside it might help. For example something like:
>
> /* Return 1 if the refname matches one of the patterns, otherwise 0. */
> static int filter_pattern_match(struct ref_filter *filter, const char *refname)
> {
> if (!*filter->name_patterns)
> return 1; /* No pattern always matches */
> if (filter->match_as_path)
> return match_name_as_path(filter->name_patterns, refname);
> return match_pattern(filter->name_patterns, refname);
> }
Yes, the comments do improve the situation and may be a reasonable compromise...
next prev parent reply other threads:[~2015-07-20 18:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 19:12 [PATCH v3 0/9] Port tag.c to use ref-filter APIs Karthik Nayak
2015-07-18 19:12 ` [PATCH v3 1/9] ref-filter: add option to align atoms to the left Karthik Nayak
2015-07-19 23:49 ` Eric Sunshine
2015-07-20 15:06 ` Karthik Nayak
2015-07-20 16:12 ` Junio C Hamano
2015-07-20 17:47 ` Eric Sunshine
2015-07-20 16:37 ` Junio C Hamano
2015-07-20 17:04 ` Karthik Nayak
2015-07-20 17:22 ` Karthik Nayak
2015-07-20 18:01 ` Eric Sunshine
2015-07-20 18:23 ` Karthik Nayak
2015-07-20 17:29 ` Junio C Hamano
2015-07-21 18:00 ` Karthik Nayak
2015-07-22 18:44 ` Matthieu Moy
2015-07-23 14:32 ` Karthik Nayak
2015-07-18 19:12 ` [PATCH v3 2/9] ref-filter: add option to filter only tags Karthik Nayak
2015-07-18 19:12 ` [PATCH v3 3/9] ref-filter: support printing N lines from tag annotation Karthik Nayak
2015-07-20 0:02 ` Eric Sunshine
2015-07-20 15:17 ` Karthik Nayak
2015-07-18 19:12 ` [PATCH v3 4/9] ref-filter: add support to sort by version Karthik Nayak
2015-07-20 1:39 ` Eric Sunshine
2015-07-20 16:34 ` Karthik Nayak
2015-07-18 19:12 ` [PATCH v3 5/9] ref-filter: add option to match literal pattern Karthik Nayak
2015-07-20 6:24 ` Eric Sunshine
2015-07-20 8:01 ` Christian Couder
2015-07-20 18:12 ` Eric Sunshine [this message]
2015-07-21 19:27 ` Karthik Nayak
2015-07-22 19:20 ` Matthieu Moy
2015-07-18 19:12 ` [PATCH v3 6/9] tag.c: use 'ref-filter' data structures Karthik Nayak
2015-07-18 22:00 ` [PATCH v3 7/9] tag.c: use 'ref-filter' APIs Karthik Nayak
2015-07-18 22:00 ` [PATCH v3 8/9] tag.c: implement '--format' option Karthik Nayak
2015-07-22 19:38 ` Matthieu Moy
2015-07-18 22:00 ` [PATCH v3 9/9] tag.c: implement '--merged' and '--no-merged' options Karthik Nayak
2015-07-19 19:20 ` Christian Couder
2015-07-21 19:28 ` Karthik Nayak
2015-07-22 19:40 ` Matthieu Moy
2015-07-23 16:20 ` Karthik Nayak
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cSu7-wegGd90WHeppt8inHSBxrakzuJSvcRV7OocJHAgg@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).