..., and someone pointed out that it had a problem
with code like { some_function_returning_a_hash() }. Should it give a
closure? Or a hash ref? ...
Oh, well now that it's stated this way... (something went wrong in my
brain when I read the actual message) It returns a closure
Back to this again . .
..., and someone pointed out that it had a problem
with code like { some_function_returning_a_hash() }. Should it give a
closure? Or a hash ref? ...
Oh, well now that it's stated this way... (something went wrong in my
brain when I read the actual
Deborah Ariel Pickett:
# ..., and someone pointed out that it had a problem
# with code like { some_function_returning_a_hash()
# }. Should it give a
# closure? Or a hash ref? ...
# Oh, well now that it's stated this way... (something went
# wrong in my
# brain when I read
On Monday 15 July 2002 11:22 pm, Deborah Ariel Pickett wrote:
Besides, does
$hashref = some_function_returning_a_hash()
make $hashref simply refer to the result of the function, or does it
make $hashref refer to a hash containing a *copy* of the result of the
function? If Perl6 is
Brent Dax wrote:
$href = hash { %hash }; #B
Why the curlies? if Chash is a function (ctor), then surely these should
be parentheses. In this context, parentheses are optional, so this could be
written
$href = hash %hash;
Dave.
David Whipp:
# Brent Dax wrote:
# $href = hash { %hash }; #B
#
# Why the curlies? if Chash is a function (ctor), then surely
# these should be parentheses. In this context, parentheses are
# optional, so this could be written
#
#$href = hash %hash;
Chash is not a function. It's a