Re^2: Using an undefined value as a hashref

I don't think that's totally true. The variable name is not available until the next statement, but the variable itself is. Otherwise, I don't see how the following two statements would work:

open(my $fh, ...);

read($fh, my $buf='', ...);
[download]

I think the problem here is that you can't auto-vivify the lvalue returned by my. Can anyone confirm or deny any of this?

Comment on Re^2: Using an undefined value as a hashref Select or Download Code

Replies are listed 'Best First'.
Re^3: Using an undefined value as a hashref by phaylon (Curate) on Sep 10, 2005 at 20:13 UTC
I'd guess it is because my returns the generated variable. Ordinary morality is for ordinary people. -- Aleister Crowley	[reply]