git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: "Michał Kiedrowicz" <michal.kiedrowicz@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>,
	Martin Langhoff <martin.langhoff@gmail.com>
Subject: Re: [PATCH V2 4/5] git-grep: Learn PCRE
Date: Thu, 5 May 2011 09:43:50 +0200	[thread overview]
Message-ID: <BANLkTinXoDFyb9U0RJVb8eH269zj+XvBdQ@mail.gmail.com> (raw)
In-Reply-To: <1304546421-25439-5-git-send-email-michal.kiedrowicz@gmail.com>

2011/5/5 Michał Kiedrowicz <michal.kiedrowicz@gmail.com>:
> +#ifdef NO_LIBPCRE
> +static void compile_pcre_regexp(struct grep_pat *p, struct grep_opt *opt)
> +{
> +       die("cannot use Perl-compatible regexes when libpcre is not compiled in");
> +}

Looks like these two functions below can be just left empty, because you will
exit when calling compile_pcre_regexp in compile_regexp.

> +static int pcrematch(struct grep_pat *p, char *line, char *eol,
> +               regmatch_t *match, int eflags)
> +{
> +       die("cannot use Perl-compatible regexes when libpcre is not compiled in");
> +}
> +
> +static void free_pcre_regexp(struct grep_pat *p)
> +{
> +       die("cannot use Perl-compatible regexes when libpcre is not compiled in");
> +}
> +

These will be never called, because...

> @@ -70,6 +135,11 @@ static void compile_regexp(struct grep_pat *p, struct grep_opt *opt)
>        if (p->fixed)
>                return;
>
> +       if (opt->pcre) {
> +               compile_pcre_regexp(p, opt);
> +               return;
> +       }

... you die here, if PCRE not available.

  parent reply	other threads:[~2011-05-05  7:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-04 22:00 [PATCH V2 0/5] Add PCRE support to git-grep Michał Kiedrowicz
2011-05-04 22:00 ` [PATCH V2 1/5] Documentation: Add --line-number to git-grep synopsis Michał Kiedrowicz
2011-05-04 22:00 ` [PATCH V2 2/5] contrib/completion: --line-number to git grep Michał Kiedrowicz
2011-05-04 22:00 ` [PATCH V2 3/5] grep: Put calls to fixmatch() and regmatch() into patmatch() Michał Kiedrowicz
2011-05-04 22:00 ` [PATCH V2 4/5] git-grep: Learn PCRE Michał Kiedrowicz
2011-05-05  1:09   ` Junio C Hamano
2011-05-05  5:47     ` Bert Wesarg
2011-05-05 16:55       ` Junio C Hamano
2011-05-05  6:19   ` Johannes Sixt
2011-05-05  7:41     ` Michal Kiedrowicz
2011-05-05  7:49       ` Johannes Sixt
2011-05-05  8:38         ` Michal Kiedrowicz
2011-05-05  6:28   ` Johannes Sixt
2011-05-05  7:43     ` Michal Kiedrowicz
2011-05-05  7:43   ` Alex Riesen [this message]
2011-05-04 22:00 ` [PATCH V2 5/5] configure: Check for libpcre Michał Kiedrowicz

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=BANLkTinXoDFyb9U0RJVb8eH269zj+XvBdQ@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.langhoff@gmail.com \
    --cc=michal.kiedrowicz@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).