Re^2: push foreach glob

Doh! I'm an idiot. Thanks. I had turned on warnings, but not strict. Surprisingly, warnings showed nothing -- I was expecting to get something from using the return value of /ad/ as an array index when /ad/ failed to match.

But yes, I somehow completely missed the fact that I was using the same array for both purposes. I think my subconscious was thinking that because I was using array refs, I was using $f not @f. Stupid subconscious.

Another case of being blinded by thinking it was too simple for such an obvious problem to hide...

Comment on Re^2: push foreach glob - bug?

Replies are listed 'Best First'.
Re^3: push foreach glob - bug? by ikegami (Patriarch) on Jan 14, 2010 at 02:00 UTC
I was expecting to get something from using the return value of /ad/ as an array index You got lucky. On failure, when called in scalar context, it happens to return a value that's both the number zero and the empty string. On success, when called in scalar context, it happens to return 1. Both results are undocumented and unreliable. You're only guaranteed to get a true or false value. `$f[ /.../ ]` [download] should be `$f[ /.../ ? 1 : 0 ]` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: push foreach glob - bug?
by ikegami (Patriarch) on Jan 14, 2010 at 02:00 UTC

I was expecting to get something from using the return value of /ad/ as an array index

You got lucky.

On failure, when called in scalar context, it happens to return a value that's both the number zero and the empty string.

On success, when called in scalar context, it happens to return 1.

Both results are undocumented and unreliable. You're only guaranteed to get a true or false value.

$f[ /.../ ]
[download]

$f[ /.../ ? 1 : 0 ]
[download]

[reply]
[d/l]
[select]