From: Stephan Beyer <s-beyer@gmx.net>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] alias.c: use git_config_string() to get alias_val
Date: Sat, 5 Apr 2008 19:39:56 +0200 [thread overview]
Message-ID: <20080405173956.GD14565@leksak.fem-net> (raw)
In-Reply-To: <200804051819.46904.chriscool@tuxfamily.org>
Hi,
> Did you see:
>
> "(And no, casting the "char **" into a "const char **" is not a good
> solution either.)"
>
> in the above page ?
Yes.
> > + if (!prefixcmp(k, "alias.") && !strcmp(k+6, alias_key))
> > + return git_config_string((const char**)&alias_val, k, v);
>
> Are you sure this ugly cast to "const char**" is needed ?
> Isn't there a better way to do it ?
Well, because alias_val is not a constant[1], changing
static char *alias_val;
to
static const char *alias_val;
is not an option.
The only other way I see[2] atm is a brain-damaged:
--
static int alias_lookup_cb(const char *k, const char *v)
{
if (!prefixcmp(k, "alias.") && !strcmp(k+6, alias_key)) {
const char *tmp;
int ret = git_config_string(&tmp, k, v);
alias_val = xstrdup(tmp);
/* actually, tmp should be free()'d. */
return ret;
}
return 0;
}
--
But instead of doing that, the original should be kept, because it is
better in code beauty, performance and memory usage. ;-)
So I thought the casting is ugly, but it does no harm. I hope ;)
(Yes, a cast from const char ** to char ** is, indeed, dangerous.)
But if I miss an obvious point, please tell me :)
Regards,
Stephan
Footnotes:
[1] It is no constant because it is returned by alias_lookup(),
and thus could be changed by further instructions.
[2] ...between the many ways that result in compiler warnings ;-)
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-04-05 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-05 12:18 [PATCH] alias.c: use git_config_string() to get alias_val Stephan Beyer
2008-04-05 16:19 ` Christian Couder
2008-04-05 17:39 ` Stephan Beyer [this message]
2008-04-06 5:49 ` Christian Couder
2008-04-06 11:02 ` Stephan Beyer
2008-04-06 13:29 ` Christian Couder
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=20080405173956.GD14565@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
/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).