Darren Duncan wrote:
At 8:32 PM -0400 7/8/06, Joe Gottman wrote:
I have one minor comment about join. You should specify its behavior
when
it is passed an empty list. Does it return undef or the empty string?
I think it makes the most sense for it to return an empty string,
which is a
I've gathered my ducks in a row, used the feedback that I've gotten so
far, and I think I'm ready to officially update S29. For that I need two
things:
1) I'd really like Larry to glance over the changes and $s29.bless but
all comments are welcome
2) I'll need commit rights to whatever
-Original Message-
From: Aaron Sherman [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 08, 2006 6:05 PM
To: Perl6 Language List
Subject: S29 update ready
I've gathered my ducks in a row, used the feedback that I've gotten so
far, and I think I'm ready to officially update S29
At 8:32 PM -0400 7/8/06, Joe Gottman wrote:
I have one minor comment about join. You should specify its behavior when
it is passed an empty list. Does it return undef or the empty string?
I think it makes the most sense for it to return an empty string,
which is a reasonable degenerate case
At 6:25 PM -0700 7/8/06, Darren Duncan wrote:
At 8:32 PM -0400 7/8/06, Joe Gottman wrote:
I have one minor comment about join. You should specify its behavior when
it is passed an empty list. Does it return undef or the empty string?
I think it makes the most sense for it to return an empty
Hi,
Luke Palmer luke at luqui.org writes:
Stevan Little writes:
One tests shows $pair.kv returning an array with two elements (the key
and value of the pair). (This is also how Pugs currently implements
this.)
The former is certainly correct. When all else fails, consider a
Ingo Blechschmidt wrote:
then the S29 draft (http://www.rodadams.net/Perl/S29.html) needs
updating, as currently it states:
What is returned at each element of the iteration varies
with function. values returns the value of the associated
element; **kv returns a 2 element list in (index,
