From: Noel Maddy <noel@zhtwn.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Noel Maddy <noel@zhtwn.com>, Ryan Anderson <ryan@michonline.com>,
git@vger.kernel.org
Subject: Re: [OT] Perl-ish perl vs. C-ish perl.
Date: Tue, 2 Aug 2005 13:20:40 -0400 [thread overview]
Message-ID: <20050802172040.GA20527@uglybox.localnet> (raw)
In-Reply-To: <7v3bpscn1r.fsf@assigned-by-dhcp.cox.net>
On Tue, Aug 02, 2005 at 09:37:36AM -0700, Junio C Hamano wrote:
> Noel Maddy <noel@zhtwn.com> writes:
>
> >> Please refrain from making this thread "I know more Perl than
> >> you do"; thank you.
> >
> > Sorry. Just trying to help, but suitably chastened.
>
> I realize that what you sent was not _too_ Perlish and being
> helpful. If you feel I overreacted, I am sorry; I _do_ think I
> did overreact, attempting to be preemptive.
No, I don't think you overreacted. Well, maybe a _little_ bit. ;)
I think you're focused on making git good (as in reliable and
maintainable), and that strong focus is admirable.
Your clarification on the expected developer profile, and how to target
the code to those developers helps, too.
For those of us who've spent years living in Perl, the idioms come much
easier than those who are coming from other languages like C. But if
the expected maintainers are not perl weenies (like me, I guess), then
you're right, it's better to stay away from the more perl-y stuffy.
Again, thanks.
>
--
If we can't define the user experience of Windows so that all Windows
machines operate the same way, then the Windows brand is meaningless.
-- Bill Gates
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Noel Maddy <noel@zhtwn.com>
next prev parent reply other threads:[~2005-08-02 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 8:17 [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 8:17 ` [PATCH 2/3] Add documentation for git-send-email-script Ryan Anderson
2005-07-31 8:17 ` [PATCH 3/3] Add new dependencies caused by git-send-email-script to debian/control Ryan Anderson
2005-07-31 8:24 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-07-31 9:36 ` Matthias Urlichs
2005-07-31 9:45 ` Junio C Hamano
2005-07-31 19:13 ` Junio C Hamano
2005-07-31 23:52 ` Ryan Anderson
2005-08-01 0:40 ` Junio C Hamano
2005-08-01 7:59 ` Matthias Urlichs
[not found] ` <20050801220800.GA12331@uglybox.localnet>
[not found] ` <20050801224308.GB12331@uglybox.localnet>
[not found] ` <7vk6j52qhn.fsf_-_@assigned-by-dhcp.cox.net>
2005-08-02 12:48 ` [OT] Perl-ish perl vs. C-ish perl Noel Maddy
2005-08-02 16:37 ` Junio C Hamano
2005-08-02 17:20 ` Noel Maddy [this message]
2005-08-03 1:30 ` [PATCH 1/3] Add git-send-email-script - tool to send emails from git-format-patch-script Ryan Anderson
2005-08-03 7:32 ` Matthias Urlichs
2005-07-31 10:25 ` Johannes Schindelin
2005-07-31 23:54 ` Ryan Anderson
2005-07-31 10:50 ` Sergey Vlasov
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=20050802172040.GA20527@uglybox.localnet \
--to=noel@zhtwn.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=ryan@michonline.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).