From: Ramsay Jones <ramsay@ramsay1•demon.co.uk>
To: Tanay Abhra <tanayabh@gmail•com>, git@vger•kernel.org
Cc: Ramkumar Ramachandra <artagnon@gmail•com>,
Matthieu Moy <Matthieu.Moy@grenoble-inp•fr>
Subject: Re: [PATCH v3 5/6] config: add `git_die_config()` to the config-set API
Date: Mon, 28 Jul 2014 11:55:22 +0100 [thread overview]
Message-ID: <53D62C1A.5000203@ramsay1.demon.co.uk> (raw)
In-Reply-To: <1406543635-19281-6-git-send-email-tanayabh@gmail.com>
On 28/07/14 11:33, Tanay Abhra wrote:
> Add `git_die_config` that dies printing the line number and the file name
> of the highest priority value for the configuration variable `key`.
>
> It has usage in non-callback based config value retrieval where we can
> raise an error and die if there is a semantic error.
> For example,
>
> if (!git_config_get_value(key, &value)) {
> /* NULL values not allowed */
> if (!value)
> git_config_die(key);
> else
> /* do work */
> }
>
> Signed-off-by: Tanay Abhra <tanayabh@gmail•com>
> ---
> Note: git_config_get_string() calls git_config_get_string_const(),
> so no need to check for whether to die or not, as it is done by
> git_config_get_string_const().
>
> Documentation/technical/api-config.txt | 5 +++++
> cache.h | 1 +
> config.c | 24 ++++++++++++++++++++++--
> 3 files changed, 28 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/technical/api-config.txt b/Documentation/technical/api-config.txt
> index 815c1ee..e7ec7cc 100644
> --- a/Documentation/technical/api-config.txt
> +++ b/Documentation/technical/api-config.txt
> @@ -155,6 +155,11 @@ as well as retrieval for the queried variable, including:
> Similar to `git_config_get_string`, but expands `~` or `~user` into
> the user's home directory when found at the beginning of the path.
>
> +`void git_die_config(const char *key)`::
> +
> + Dies printing the line number and the file name of the highest
> + priority value for the configuration variable `key`.
> +
> See test-config.c for usage examples.
>
> Value Parsing Helpers
> diff --git a/cache.h b/cache.h
> index 93bdbab..8512225 100644
> --- a/cache.h
> +++ b/cache.h
> @@ -1406,6 +1406,7 @@ extern int git_config_get_bool(const char *key, int *dest);
> extern int git_config_get_bool_or_int(const char *key, int *is_bool, int *dest);
> extern int git_config_get_maybe_bool(const char *key, int *dest);
> extern int git_config_get_pathname(const char *key, const char **dest);
> +extern void git_die_config(const char *key);
>
> extern int committer_ident_sufficiently_given(void);
> extern int author_ident_sufficiently_given(void);
> diff --git a/config.c b/config.c
> index 2ce3318..136ee9c 100644
> --- a/config.c
> +++ b/config.c
> @@ -1505,8 +1505,12 @@ const struct string_list *git_config_get_value_multi(const char *key)
>
> int git_config_get_string_const(const char *key, const char **dest)
> {
> + int ret;
> git_config_check_init();
> - return git_configset_get_string_const(&the_config_set, key, dest);
> + ret = git_configset_get_string_const(&the_config_set, key, dest);
> + if (ret < 0)
> + git_die_config(key);
> + return ret;
> }
>
> int git_config_get_string(const char *key, char **dest)
> @@ -1547,10 +1551,26 @@ int git_config_get_maybe_bool(const char *key, int *dest)
>
> int git_config_get_pathname(const char *key, const char **dest)
> {
> + int ret;
> git_config_check_init();
> - return git_configset_get_pathname(&the_config_set, key, dest);
> + ret = git_configset_get_pathname(&the_config_set, key, dest);
> + if (ret < 0)
> + git_die_config(key);
> + return ret;
> }
>
> +void git_die_config(const char *key)
> +{
> + const struct string_list *values;
> + struct key_value_info *kv_info;
> + values = git_config_get_value_multi(key);
> + kv_info = values->items[values->nr - 1].util;
> + if (!kv_info->linenr)
> + die("unable to parse command-line config");
> + else
> + die("bad config file line %d in %s",kv_info->linenr, kv_info->filename);
How about including the 'key' string in the error message?
Similar comment applies to an earlier patch in this series.
> + }
> +
> /*
> * Find all the stuff for git_config_set() below.
> */
>
ATB,
Ramsay Jones
next prev parent reply other threads:[~2014-07-28 10:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-28 10:33 [PATCH v3 0/6] Rewrite `git_config()` using config-set API Tanay Abhra
2014-07-28 10:33 ` [PATCH v3 1/6] config.c: fix accuracy of line number in errors Tanay Abhra
2014-07-28 10:33 ` [PATCH v3 2/6] add line number and file name info to `config_set` Tanay Abhra
2014-07-28 10:33 ` [PATCH v3 3/6] rewrite git_config() to use the config-set API Tanay Abhra
2014-07-28 10:33 ` [PATCH v3 4/6] add a test for semantic errors in config files Tanay Abhra
2014-07-28 11:22 ` Matthieu Moy
2014-07-28 11:27 ` Tanay Abhra
2014-07-28 11:38 ` Matthieu Moy
2014-07-28 10:33 ` [PATCH v3 5/6] config: add `git_die_config()` to the config-set API Tanay Abhra
2014-07-28 10:55 ` Ramsay Jones [this message]
2014-07-28 11:02 ` Tanay Abhra
2014-07-28 11:16 ` Matthieu Moy
2014-07-28 11:14 ` Matthieu Moy
2014-07-28 10:33 ` [PATCH v3 6/6] add tests for `git_config_get_string_const()` Tanay Abhra
2014-07-28 11:24 ` [PATCH v3 0/6] Rewrite `git_config()` using config-set API Matthieu Moy
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=53D62C1A.5000203@ramsay1.demon.co.uk \
--to=ramsay@ramsay1$(echo .)demon.co.uk \
--cc=Matthieu.Moy@grenoble-inp$(echo .)fr \
--cc=artagnon@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=tanayabh@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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