From: "Rafael Garcia-Suarez" <rgarciasuarez@gmail.com>
To: "Junio C Hamano" <junio@pobox.com>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Uniquify usage of subroutine prototypes
Date: Tue, 25 Mar 2008 23:06:12 +0100 [thread overview]
Message-ID: <b77c1dce0803251506y443aab5uf0134a47e9cf28de@mail.gmail.com> (raw)
In-Reply-To: <7vlk46lh61.fsf@gitster.siamese.dyndns.org>
On 25/03/2008, Junio C Hamano <junio@pobox.com> wrote:
> I am not saying that Perl prototypes is a bad thing. The point of the
> prototype is to change the syntax and semantics so that you can write a
> function to which arguments are _not_ passed as a flattend list, and
> without them you cannot write something that emulates "push @a, $b, $c".
I would agree with what Junio says here. The primary motivation of
prototypes was to emulate the syntax of perl built-ins, and their
extension (with the _ character) in Perl 5.10 has followed this
general principle. As a general rule, I tend to avoid using prototypes
for 'normal' functions. That's mostly an application of the least
surprise principle.
prev parent reply other threads:[~2008-03-25 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 12:11 [PATCH] gitweb: Uniquify usage of subroutine prototypes Jakub Narebski
2008-03-25 19:47 ` Junio C Hamano
2008-03-25 22:06 ` Rafael Garcia-Suarez [this message]
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=b77c1dce0803251506y443aab5uf0134a47e9cf28de@mail.gmail.com \
--to=rgarciasuarez@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junio@pobox.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).