Re: Re: scalar my vs list my

Hmm. Nope, you ended up with a few broken ones:

# Local variables: SCALAR,SCALAR,... 
my $x, $y, $z; 
...
my $filename = "/path/to/file", 
        $filemode = "immolate", 
        $opmode   = "seek", 
        $filetype = "image/gif";
[download]

Neither of those declare locally anything but the first var. You'd have to do something like:

my $x, my $y, my $z;
[download]

Just think of my as a really high precedence prefix operator that must appear before an lvalue, and you'll have the right mental model. But to figure the scalar-vs-arrayness of the rest of the expression, throw away all the my's first.

My preference is one variable per my declaration, unless it's a bunch of scalars and an optional terminating array being fed from a list (like a subroutine argument grab).

-- Randal L. Schwartz, Perl hacker

Comment on Re: Re: scalar my vs list my Select or Download Code

Replies are listed 'Best First'.
Re: Re: Re: scalar my vs list my by $code or die (Deacon) on Apr 27, 2001 at 01:56 UTC
At the risk of straying further, its ok to do this isn't it: `my ($filename, $filemode, $opmode, $filetype) = ("/path/file", "immolate", "seek", "image/gif");` [download] Ignore me: I really should get into the habbit of reading the last paragraph of peoples' posts. `$ perldoc perldoc`	[reply] [d/l]
Re^4: scalar my vs list my by tadman (Prior) on Apr 27, 2001 at 02:12 UTC
What about this unruly specimen: `(my ($filename, my ($filemode, my ($opmode, my $filetype)))) = "/path/file", "immolate", "seek", "image/gif";` [download] The one thing that has bugged me about my() was the way it used to cling to the real block, and not the virtual block. As in: `for (my $n = 0; $n < 100; $n++) { # ... (Stuff) } # ... (More Stuff) for (my $n = 0; $n < 100; $n++) { # ... (Stuff) }` [download] IIRC, there used to be a condition that generated an error for the second declaration. This seems to have been fixed, thankfully.	[reply] [d/l] [select]