On Fri, Aug 01, 2003 at 11:01:15PM +0100, Simon Cozens wrote:
: [EMAIL PROTECTED] (Damian Conway) writes:
: > The last thought on the problem that Larry's shared with me was that there
: > may need to be a special case for allowing a single &block parameter after
: > the slurpy
: And the Rubyometer creeps up another few notches...

It's long been planned to allow blocks anywhere in the signature,
particularly at the end, because of endweight considerations.  It's
been on my Perl 5 wish list since long before I ever heard of Ruby.
In fact, the first thing I thought when I saw how Ruby did it was,
"Gee, why did he restrict it to only be the last thing?"  In Ruby
it's a special case syntax.  We're making a general capability to put
the block anywhere in the argument list.  If that makes Perl more
like Ruby, so be it.  But Perl is not terribly worried about where
it fits on the Rubyometer.  Ruby will need to worry about where it
fits on the Perlometer.

: (Gosh, you'd almost think that Matz had already thought through some of these
: issues, wouldn't you? ;)

Certainly Matz thought about some of these issues.  Whether he would
claim to have thought them "through" is another matter.  There are
many throughways, and they don't all lead the same place.  It's easy
to tunnel into a false minimum and think you're "through".


Reply via email to