in reply to Re^2: shift vs @_
in thread shift vs @_

Actually, I think I will claim it is better. In theory it should be easier to notice changes since there is less clutter -- no leading "my" and no trailing "= shift" that someone eyeballing the code has to filter out so the variables themselves should stand out better.

Replies are listed 'Best First'.
Re^4: shift vs @_
by tomhukins (Curate) on Oct 02, 2006 at 20:44 UTC
    Perhaps, but consider the starting point of one argument: 
    my(
    $foo,
) = @_;

    [download]
    compared to: 
    my $foo = shift;

    [download]
    I use the shift approach because it gives me a clean starting point and lets me extend my methods (or subroutines) easily. Having said that, I try to avoid extending public methods and prefer to create new methods when appropriate. But perhaps I'm drifting away from the original question a little..
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom