|
in reply to Re^2: Perl bug ?
in thread Perl bug ?
the first call of ok():
the first argument is $errors && ($errors->[0] =~ /.../i) which results in $errors being passed as the first argument. before it is passed, array element 0 gets autovivivied though by usage in the second argument.
the second call:
$errors is now true, so the matching is executed and its result would the empty string ("false"). but since the matching is executed in list context, the result is an empty list, so what you wrote as a second argument becomes now the first argument. |
Re^4: Perl bug ?
by vsespb (Chaplain) on Feb 06, 2013 at 12:36 UTC
|
[[[ARRAY(0x137cd48)]]] [[[some text 1 ]]]
then ?
First argument should be true only if $errors->[0] contains string /Journal file not found/
no ?
| [reply]
[d/l] |
|
|
like I said. the first argument passed to ok() is $errors && ($errors->[0] =~ /.../i).
what gets really passed is $errors. it's like saying: my @foo = $errors && ($errors->[0] =~ /.../i)
the pattern match isn't executed at all at the first time.
but after processing the first argument, you use $errors->[0] in your second argument. now $errors is autovivified to an array ref before ok() is actyally executed. since $errors is passed as the first argument as an alias, it prints ARRAY(0x137cd48)
| [reply]
[d/l]
[select] |
|
|
what gets really passed is $errors
Why? I would expect the result of the && operation to be passed.
| [reply]
[d/l] |
|
|
|
|
| |
|
|
