Why I Use Perl: Reliability

Re:Why I Use Perl: Reliability by irahul on Tuesday May 29, 2012 @04:49PM (#4039796)

I don't program in perl now a days. But when I did, I generally used perl's shortcuts a lot.

For example:

    return reduce(sub { $a * $b; }, 1, (1..$n));

would be:

    reduce { $a * $b } 1..$n;

This

    my $output = 1;
        for my $i (1..$n) {
            $output *= $i;
    }

would be:

    $output *= $_ for (1..$n)

So, I have a question for you(assuming you write perl for a living). Is this your preferred style, or you do this to appease readability police which demands programming languages be readable by non programmers? Because really, what kind of programmer programs in perl and is averse to $_?

[ Parent | on HN ]

Re:Why I Use Perl: Reliability by jbert on Tuesday May 29, 2012 @04:58PM (#4039853)

My production style is happy to use:

    $output *= $_ for (1..$n)

and you're right to call me on it. If I am writing a multi-line for loop, I do like to name the loop var though.

I think this is an interesting point (in a discussion about readability), do non-perl coders think the one-liner (with 'for' suffix) is more or less readable?

(I also prefer explicit return for maintenance reasons, except possibly in one-line subs)

[ Parent | on HN ]