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?Good point. 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" or "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?
In Section
Meditations