From: Junio C Hamano <gitster@pobox.com>
To: Bill Pemberton <wfp5p@virginia.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/6] cleanups for git-send-email
Date: Wed, 29 Apr 2009 12:18:50 -0700 [thread overview]
Message-ID: <7vws939skl.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1241010743-7020-1-git-send-email-wfp5p@virginia.edu> (Bill Pemberton's message of "Wed, 29 Apr 2009 09:12:17 -0400")
Bill Pemberton <wfp5p@virginia.edu> writes:
> The following are some code cleanups for git-send-email.perl. They're
> based on suggestions by perlcritc.
>
> Bill Pemberton (6):
> Remove return undef from validate_patch
> Remove function prototypes from git-send-email.perl
> Remove return undef from ask()
> Add explict return to end of subroutines
> Remove mix of high and low-precedence booleans
> Remove bareword filehandles in git-send-email.perl
Perl styles are highly personal.
While I admit that the changes these patches bring in match my personal
taste more or less exactly [*1*], there was somebody (sorry I lost track)
who volunteered to take the maintenance responsibility of that program
over to clean up or even rewrite it, so I would rather have that person
have a say in the overall styles of the (rewritten) program.
[Footnote]
*1* ...except for the "and/or vs &&/||" bits, even though I prefer the
latter myself solely because I am old fashioned.
I think it is simply silly to say "precedence of ! and and/or does not
mix". "!" and "&&" have different precedence and rewriting (A and !B)
into (A && !B) would not make things any better nor worse. After all,
nobody would have problems with "$a + $b * $c" even though + and * have
different precedence.
Oh, I also do not agree with "always explicitly return". If the change
and explanation were limited to the subs whose return values are _used_, I
would agree with the change, though.
next prev parent reply other threads:[~2009-04-29 19:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 13:12 [PATCH 0/6] cleanups for git-send-email Bill Pemberton
2009-04-29 13:12 ` [PATCH 1/6] Remove return undef from validate_patch Bill Pemberton
2009-04-29 13:12 ` [PATCH 2/6] Remove function prototypes from git-send-email.perl Bill Pemberton
2009-04-29 13:12 ` [PATCH 3/6] Remove return undef from ask() Bill Pemberton
2009-04-29 13:12 ` [PATCH 4/6] Add explict return to end of subroutines Bill Pemberton
2009-04-29 13:12 ` [PATCH 5/6] Remove mix of high and low-precedence booleans Bill Pemberton
2009-04-29 13:12 ` [PATCH 6/6] Remove bareword filehandles in git-send-email.perl Bill Pemberton
2009-05-03 20:58 ` Jeff King
2009-05-03 21:34 ` Francis Galiegue
2009-05-04 6:12 ` H.Merijn Brand
2009-05-04 6:53 ` Francis Galiegue
2009-05-04 7:41 ` H.Merijn Brand
2009-04-29 16:54 ` [PATCH 5/6] Re: Remove mix of high and low-precedence booleans Nicolas Sebrecht
2009-04-29 17:00 ` Bill Pemberton
2009-05-03 20:31 ` [PATCH 4/6] Add explict return to end of subroutines Jeff King
2009-05-03 20:26 ` [PATCH 3/6] Remove return undef from ask() Jeff King
2009-05-04 2:26 ` Jay Soffian
2009-05-03 20:27 ` [PATCH 2/6] Remove function prototypes from git-send-email.perl Jeff King
2009-05-03 19:46 ` [PATCH 1/6] Remove return undef from validate_patch Jeff King
2009-04-29 19:18 ` Junio C Hamano [this message]
2009-04-29 19:48 ` [PATCH 0/6] cleanups for git-send-email Bill Pemberton
2009-04-29 20:23 ` Junio C Hamano
2009-04-29 22:27 ` [PATCH 0/6] " Nicolas Sebrecht
2009-04-30 8:11 ` Andreas Ericsson
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=7vws939skl.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=wfp5p@virginia.edu \
/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).