Why is this list called Perl best practices?
I prefer to have two separate lists: one for general
programming practices, another for language-specific ones.
The general, language-independent list tends to be
the more important and interesting of the two IMHO.
Most language-specific items, such as
"start each file with use strict"
"use three-argument open and lexical file handles"
are easily detected by a tool, such as Perl::Critic.
The general list, OTOH, usually requires a human with
good taste to adjudicate.
The point that sound programming is mostly language
independent was well made by chromatic in
response to a
reddit post extolling Python's "readability":
Pray tell, how precisely does Python prevent you
from using bad variable names?
How does Python enforce good encapsulation?
How does Python detect methods and functions that are too long?
How does Python help you avoid poor coupling and
promote wise decomposition?
Does Python write good documentation for you?
Does Python require comprehensive testing?
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||