From: Aleksey Mokhovikov <moxobukob@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH][GSOC] Selection of the verbose message is replaced with generated message in install_branch_config()
Date: Tue, 18 Mar 2014 21:33:29 +0700 [thread overview]
Message-ID: <lg9l22$qto$1@ger.gmane.org> (raw)
In-Reply-To: <loom.20140318T124348-742@post.gmane.org>
This patch replaces if chain with
2 dimensional array of format strings and arguments.
Signed-off-by: Aleksey Mokhovikov <moxobukob@gmail.com>
---
This patch is unrelated with previous one, but related to GSoC.
So I don't know if I should create new thread for this patch.
Compare with original construction
Pros:
1) Remove if chain.
2) Single table contains all messages with arguments in one construction.
3) Less code duplication.
Cons:
1) Harder to associate the case with message.
2) Harder for compiler to warn the programmer about not
enough arguments for format string.
3) Harder to add non-string argument to messages.
If !!(x) is out of the coding guide, then message_id construction
can be rewritten in several other ways.
The guideline tells that !!(x) is not welcome and should not be
unless needed. But looks like this is normal place for it.
P.S.
Thanks to comments I got, so
I've read more GNU gettext manual to get info
about translation workflow. When I posted a first patch
I've passed the same message format strings to gettext /*_()*/
as in original, to save the context of the message. And they
will be translated if every possible string combination
will be marked separately for translation. Because of
xgettext can extract string from source automatically,
it ruins the idea to generate message from parts. Even if the
exaclty same message format string is passed to gettext.
branch.c | 53 ++++++++++++++++++++++++++++++-----------------------
1 file changed, 30 insertions(+), 23 deletions(-)
diff --git a/branch.c b/branch.c
index 723a36b..51a5faf 100644
--- a/branch.c
+++ b/branch.c
@@ -47,12 +47,32 @@ static int should_setup_rebase(const char *origin)
return 0;
}
+
void install_branch_config(int flag, const char *local, const char *origin, const char *remote)
{
const char *shortname = remote + 11;
int remote_is_branch = starts_with(remote, "refs/heads/");
struct strbuf key = STRBUF_INIT;
int rebasing = should_setup_rebase(origin);
+ int message_id = (!!remote_is_branch << 2) | (!!origin << 1) | (!!rebasing);
+ const char *message_table[][4] =
+ {{N_("Branch %s set up to track local ref %s."),
+ local, remote},
+ {N_("Branch %s set up to track local ref %s by rebasing."),
+ local, remote},
+ {N_("Branch %s set up to track remote ref %s."),
+ local, remote},
+ {N_("Branch %s set up to track remote ref %s by rebasing."),
+ local, remote},
+ {N_("Branch %s set up to track local branch %s."),
+ local, shortname},
+ {N_("Branch %s set up to track local branch %s by rebasing."),
+ local, shortname},
+ {N_("Branch %s set up to track remote branch %s from %s."),
+ local, shortname, origin},
+ {N_("Branch %s set up to track remote branch %s from %s by rebasing."),
+ local, shortname, origin}};
+ const char **message = NULL;
if (remote_is_branch
&& !strcmp(local, shortname)
@@ -68,7 +88,7 @@ void install_branch_config(int flag, const char *local, const char *origin, cons
strbuf_reset(&key);
strbuf_addf(&key, "branch.%s.merge", local);
git_config_set(key.buf, remote);
-
+
if (rebasing) {
strbuf_reset(&key);
strbuf_addf(&key, "branch.%s.rebase", local);
@@ -77,29 +97,16 @@ void install_branch_config(int flag, const char *local, const char *origin, cons
strbuf_release(&key);
if (flag & BRANCH_CONFIG_VERBOSE) {
- if (remote_is_branch && origin)
- printf_ln(rebasing ?
- _("Branch %s set up to track remote branch %s from %s by rebasing.") :
- _("Branch %s set up to track remote branch %s from %s."),
- local, shortname, origin);
- else if (remote_is_branch && !origin)
- printf_ln(rebasing ?
- _("Branch %s set up to track local branch %s by rebasing.") :
- _("Branch %s set up to track local branch %s."),
- local, shortname);
- else if (!remote_is_branch && origin)
- printf_ln(rebasing ?
- _("Branch %s set up to track remote ref %s by rebasing.") :
- _("Branch %s set up to track remote ref %s."),
- local, remote);
- else if (!remote_is_branch && !origin)
- printf_ln(rebasing ?
- _("Branch %s set up to track local ref %s by rebasing.") :
- _("Branch %s set up to track local ref %s."),
- local, remote);
+ if ((0 <= message_id) && (message_id < ARRAY_SIZE(message_table)))
+ message = message_table[message_id];
else
- die("BUG: impossible combination of %d and %p",
- remote_is_branch, origin);
+ die("BUG: id is out of range:id=%d (is_branch=%d, origin=%p, rebasing=%d)",
+ message_id, remote_is_branch, origin, rebasing);
+
+ if (!message || !message[0])
+ die("BUG: message is NULL. Fix verbose message table.");
+
+ printf_ln(_(message[0]), message[1], message[2], message[3]);
}
}
--
1.8.3.2
next prev parent reply other threads:[~2014-03-18 14:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 9:55 [PATCH][GSOC] Selection of the verbose message is replaced with generated message in install_branch_config() Aleksey Mokhovikov
2014-03-17 10:01 ` Matthieu Moy
2014-03-18 14:42 ` Aleksey Mokhovikov
2014-03-17 10:53 ` Eric Sunshine
2014-03-18 14:37 ` Aleksey Mokhovikov
2014-03-18 12:22 ` Aleksey Mokhovikov
2014-03-18 14:33 ` Aleksey Mokhovikov [this message]
2014-03-19 9:21 ` Eric Sunshine
2014-03-20 11:56 ` Aleksey Mokhovikov
2014-03-21 4:03 ` Eric Sunshine
2014-03-21 17:09 ` Junio C Hamano
2014-03-21 21:13 ` Michael Haggerty
2014-03-21 21:33 ` Eric Sunshine
2014-03-21 21:45 ` Michael Haggerty
2014-03-24 7:28 ` Aleksey Mokhovikov
2014-03-24 12:22 ` Michael Haggerty
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='lg9l22$qto$1@ger.gmane.org' \
--to=moxobukob@gmail.com \
--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).