Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

Re^2: Yet another set of Perl best practices

by Anonymous Monk
on Aug 24, 2012 at 16:39 UTC ( #989586=note: print w/ replies, xml ) Need Help??


in reply to Re: Yet another set of Perl best practices
in thread Yet another set of Perl best practices

Why is this list called Perl best practices? Only 7, 11, 20 and maybe 18 is related to Perl. The rest is valid for any language.

They're all related to perl since perl is a programming language :)

Perhaps you meant specific to perl ?

But even if they look specific, they all really are generic

7. Perl is a powerful and expressive language, don't be afraid to use it to its maximum.
write idiomatic code
11. Don't use an object when a simple hash or array will do.
Don't use an object when a simple struct will do
Don't use an object when a simple data structure will do
20. use strict, use warnings, selectively disable them when required.
lint that mother hard, maximum warnings -Wall
lint, "use strict";
18. Add lots of debugging code
use assertions, use logging


Comment on Re^2: Yet another set of Perl best practices

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://989586]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (6)
As of 2014-07-25 00:17 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (167 votes), past polls