On Wednesday 12 May 2010 00:55:13 Lutz Gehlen wrote:
Hello everybody,
recently, I read the following statement in a CPAN Ratings entry:
this package also uses wantarray (a transgression amongst interface
sensibilities).
I also sometimes use wantarray and don't see anything bad about it
if
On Wed, May 12, 2010 at 7:08 AM, Shlomi Fish shlo...@iglu.org.il wrote:
On Wednesday 12 May 2010 00:55:13 Lutz Gehlen wrote:
Hello everybody,
recently, I read the following statement in a CPAN Ratings entry:
this package also uses wantarray (a transgression amongst interface
sensibilities).
# from Hans Dieter Pearcey
# on Wednesday 12 May 2010 08:49:
...just because it's not how arrays work anywhere else in Perl,
This is not about how arrays work, but how functions work. See
localtime(), caller(), each(), glob(), readline(), etc.
But then see sort() and split().
There are
Hello everybody,
thanks for all your comments.
On Wed, May 12, 2010 at 11:49:09AM -0400, Hans Dieter Pearcey wrote:
relatively simple return an array in list context, or an arrayref in scalar
context often ends up irritating me more than it's worth (including when I
wrote the function that
On Wed, May 12, 2010 at 11:32:59AM -0700, Eric Wilhelm wrote:
That might be simple, but no builtins do this, which seems to say
something. If you're still working with lists, you expect them to
behave like lists, and not try to package themselves in a reference
The following comment has
Hello everybody,
recently, I read the following statement in a CPAN Ratings entry:
this package also uses wantarray (a transgression amongst interface
sensibilities).
Hi Lutz,
I've read that too and my reaction was what a totally ridiculous claim!. And
it is based on ... nil or maybe
