Re: Writing code that looks nice

in reply to Writing code that looks nice

I avoid using $_ and default arguments even in the shortest programs, except when i have to (in map, for example) or in very particular idioms, such as

for ($string) {
    s/^\s+//;
    s/\s+$//;
}
[download]

(from perlfaq4.)

And i usually avoid postfix conditions.

But as everyone here says, it's a matter of taste.

Comment on Re: Writing code that looks nice Select or Download Code

Replies are listed 'Best First'.
Re^2: Writing code that looks nice by Your Mother (Archbishop) on Apr 12, 2010 at 16:11 UTC
I think that's more idiomatic as `s/\A\s+\|\s+\z//g for @strings; # or $string =~ /\A\s+\|\s+\z//g;` [download] For the OP: I prefer short, natural language code over formal blocks and such any day. But the point you get to at the bottom of it all is, there will be disagreement so consistency is best / don't edit other hackers' code for style; fit in with whatever codebase you have. (update, put in missing "/", thanks webfiend!)	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: Writing code that looks nice
by Your Mother (Archbishop) on Apr 12, 2010 at 16:11 UTC

I think that's more idiomatic as

s/\A\s+|\s+\z//g for @strings;
# or
$string =~ /\A\s+|\s+\z//g;
[download]

For the OP: I prefer short, natural language code over formal blocks and such any day. But the point you get to at the bottom of it all is, there will be disagreement so consistency is best / don't edit other hackers' code for style; fit in with whatever codebase you have. (update, put in missing "/", thanks webfiend!)

[reply]
[d/l]

In Section Seekers of Perl Wisdom