Clear questions and runnable code
get the best and fastest answer
Seems to be a Win32 thing
As I said earlier, I get this same behaviour under HP/UX. Unix isn't windows, so it's not a "Win32" thing. :-)
even though I cannot see how to provide any sort of indication of where the problem might occur?
Well, you seem to be ignoring my conjectures about substr() being treated like an lvalue subroutine in this context.
Maybe I should be clearer about what I suspect is happening.
First of all, from perldoc -f substr: When used as an lvalue, specifying a substring that is entirely outside the string is a fatal error.
substr() is used an lvalue (left value) when it's on the *left* hand side of an equal sign. This isn't usual for function calls, but substr() is an exception.
For example, this code demonstrates a substr() used as an lvalue, where the substring lies entirely outside the string. It generates a fatal error, just like the documentation says it will.
Notice how this fatal error behaviour looks exactly the same as the fatal errors we saw earlier in the thread, back when we passed "substr($x,2,1)" to a function that does nothing. Hmm... suspicious!
Second of all, note that function calls can sometimes modify their callers:
So, let's combine these two ideas.
Now, suppose I were to pass substr($x,2,1) to bar() instead of $x. That would be roughly equivalent to running:
, which treats our substr() call as an lvalue. (It's on the *left* side of an assignment). This is a fatal error, like we saw in point #1 above.
My question to the experts was (and maybe I didn't spell this out clearly enough):
My guess is "yes" (it would explain the behaviour that we both see), and my follow-up question was whether this was a design decision, or a bug.
Now do you see what I was really asking?