git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Thomas Rast <trast@student.ethz.ch>,
	Suraj Kurapati <sunaku@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH] add -p: import Term::ReadKey with 'require'
Date: Fri, 06 Feb 2009 23:50:00 -0800	[thread overview]
Message-ID: <7v8woiznx3.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090207045401.GA21135@sigill.intra.peff.net> (Jeff King's message of "Fri, 6 Feb 2009 23:54:02 -0500")

Jeff King <peff@peff.net> writes:

> On Sat, Feb 07, 2009 at 12:21:13AM +0100, Thomas Rast wrote:
>
>> > (note that you could also skip the import and just call
>> > Term::ReadKey::ReadKey by its full name).
>> 
>> I tried that but couldn't get either Term::ReadKey::ReadKey or
>> Term::ReadKey->ReadKey to work.  In retrospect, I suppose it requires
>> parentheses too.
>
> Right, you would still need the parentheses. But note that the second
> syntax (with the "->") would always be wrong. The "::" syntax just says
> "find this name not in the current namespace, but in this absolute
> namespace I am giving you". But "X->Y" is actually a syntactic shorthand
> for "look up X::Y (or Z::Y, where Z is the blessed package of X), and
> then call X::Y(X, @_)".
>
> Which makes sense for object-oriented stuff. You get the object or the
> classname as the first parameter to a method. But for a regular package
> function, you would be calling
>
>   Term::ReadKey::ReadKey('Term::ReadKey', 0)
>
> which of course makes no sense.
>
> But I think doing the import makes more sense (and is how Term::ReadKey
> is intended to be used), so the patch you posted is best.

Ok, will queue.

  reply	other threads:[~2009-02-07  7:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-01 20:35 [RFC PATCH] add -p: prompt for single characters Thomas Rast
2009-02-02  3:31 ` Suraj Kurapati
2009-02-02  8:34   ` Thomas Rast
2009-02-02  8:50     ` Junio C Hamano
2009-02-02 21:46       ` [PATCH 0/4] add -p: Term::ReadKey and more Thomas Rast
2009-02-02 21:46       ` [PATCH 1/4] add -p: change prompt separator for 'g' Thomas Rast
2009-02-02 21:46       ` [PATCH 2/4] add -p: trap Ctrl-D in 'goto' mode Thomas Rast
2009-02-02 21:46       ` [PATCH 3/4] add -p: optionally prompt for single characters Thomas Rast
2009-02-03  6:24         ` Jeff King
2009-02-03  8:54           ` [Illustration PATCH] add -i: accept single-keypress input Thomas Rast
2009-02-03  9:05             ` Junio C Hamano
2009-02-03  9:35               ` Thomas Rast
2009-02-04  5:10                 ` Junio C Hamano
2009-02-04  8:51                   ` Thomas Rast
2009-02-04 19:42           ` [PATCH 3/4] add -p: optionally prompt for single characters Thomas Rast
2009-02-04 20:08             ` [PATCH v2 3/4] add -p: " Thomas Rast
2009-02-04 20:08             ` [PATCH v2 4/4] add -p: print errors in separate color Thomas Rast
2009-02-04 20:12             ` [PATCH v3 3/4] add -p: prompt for single characters Thomas Rast
2009-02-04 20:12             ` [PATCH v3 4/4] add -p: print errors in separate color Thomas Rast
2009-02-04 20:40             ` [PATCH 3/4] add -p: optionally prompt for single characters Junio C Hamano
2009-02-05  8:28               ` [PATCH v4 3/4] add -p: " Thomas Rast
2009-02-06 14:01                 ` Jeff King
2009-02-06 19:30                   ` [PATCH] add -p: import Term::ReadKey with 'require' Thomas Rast
2009-02-06 20:30                     ` Jeff King
2009-02-06 23:21                       ` Thomas Rast
2009-02-07  4:54                         ` Jeff King
2009-02-07  7:50                           ` Junio C Hamano [this message]
2009-02-05  8:28               ` [PATCH v4 4/4] add -p: print errors in separate color Thomas Rast
2009-02-02 21:46       ` [PATCH 4/4] add -p: print errors in help colors Thomas Rast
2009-02-02 13:19 ` [RFC PATCH] add -p: prompt for single characters Jeff King

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=7v8woiznx3.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sunaku@gmail.com \
    --cc=trast@student.ethz.ch \
    /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).