From: Junio C Hamano <gitster@pobox.com>
To: "dsal3389 via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, dsal3389 <dsal3389@gmail.com>
Subject: Re: [PATCH 2/2] removed else statement
Date: Thu, 06 Oct 2022 10:16:44 -0700 [thread overview]
Message-ID: <xmqqbkqolvnn.fsf@gitster.g> (raw)
In-Reply-To: c107ad9f6ff2d5e00134eb1348f24737774edbac.1665056747.git.gitgitgadget@gmail.com
"dsal3389 via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: dsal3389 <dsal3389@gmail.com>
>
> there is no need for the else statement if we can do it more
> elegantly with a signle if statement we no "else"
Some people seem to use subjective words like "elegantly" but they
weaken your justification. You are better off avoiding them.
As to the change in the patch, I do find it easier to read to have a
check for an error condition whose body unconditionally exits first,
and then the special casing of "version" and "help" as part of the
preparation for the "normal codepath".
Side note: yes, you can steal from the last paragraph when you
are redoing the justfication of this patch.
Thanks.
> - if (argc > 0) {
> - if (!strcmp("--version", argv[0]) || !strcmp("-v", argv[0]))
> - argv[0] = "version";
> - else if (!strcmp("--help", argv[0]) || !strcmp("-h", argv[0]))
> - argv[0] = "help";
> - } else {
> +
> + if (argc <= 0) {
> /* The user didn't specify a command; give them help */
> commit_pager_choice();
> printf(_("usage: %s\n\n"), git_usage_string);
> @@ -907,6 +903,12 @@ int cmd_main(int argc, const char **argv)
> printf("\n%s\n", _(git_more_info_string));
> exit(1);
> }
> +
> + if (!strcmp("--version", argv[0]) || !strcmp("-v", argv[0]))
> + argv[0] = "version";
> + else if (!strcmp("--help", argv[0]) || !strcmp("-h", argv[0]))
> + argv[0] = "help";
> +
> cmd = argv[0];
>
> /*
next prev parent reply other threads:[~2022-10-06 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 11:45 [PATCH 0/2] Minor Refactors: remove useless else dsal3389 via GitGitGadget
2022-10-06 11:45 ` [PATCH 1/2] python file more pytonic, adjust "if" and "for" dsal3389 via GitGitGadget
2022-10-06 16:02 ` Victoria Dye
2022-10-06 17:16 ` Junio C Hamano
2022-10-06 11:45 ` [PATCH 2/2] removed else statement dsal3389 via GitGitGadget
2022-10-06 16:14 ` Victoria Dye
2022-10-07 18:35 ` Junio C Hamano
2022-10-06 17:16 ` Junio C Hamano [this message]
2022-10-06 17:06 ` [PATCH 0/2] Minor Refactors: remove useless else Junio C Hamano
2022-10-07 14:38 ` [PATCH v2 0/2] git.c: improve readability | git-p4: minor optimization Daniel Sonbolian via GitGitGadget
2022-10-07 14:38 ` [PATCH v2 1/2] git-p4: minor optimization in read_pip_lines Daniel Sonbolian via GitGitGadget
2022-10-07 15:17 ` Phillip Wood
2022-10-07 17:28 ` Junio C Hamano
2022-10-07 14:38 ` [PATCH v2 2/2] git.c: improve code readability in cmd_main Daniel Sonbolian via GitGitGadget
2022-10-08 16:21 ` [PATCH v3] " Daniel Sonbolian via GitGitGadget
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=xmqqbkqolvnn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=dsal3389@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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).