Re: [PATCH] Make builtin-tag.c use parse_options.

From

Jakub Narebski <jnareb@gmail.com>

Date

Nov 9, 2007, 13:57 UTC

Message-ID

<fh1p10$nta$1@ger.gmane.org>

In-Reply-To

<473463E0.7000406@gmail.com>

Carlos Rica wrote:

> +     struct option options[] = {
> +             { OPTION_STRING, 'l', NULL, &list, "pattern", "list tag names",
> +                     PARSE_OPT_OPTARG, NULL, (intptr_t) no_pattern },

> +             OPT_STRING('F', NULL, &msgfile, "file", "message in a file"),

Does it matter that you use OPTION_STRING here and OPT_STRING macro there?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git