|Perl: the Markov chain saw|
Suggested templates for Perlby tirwin (Initiate)
|on Apr 28, 2008 at 04:57 UTC||Need Help??|
tirwin has asked for the
wisdom of the Perl Monks concerning the following question:
O Ye Gatherers of Knowledge -
I have a simple enough question, although the replies may not be so. :)
I have been searching for 'best practice' recommendations on what should be included in a minimum template for new perl scripts and cannot find anything on the subject (most of my searches using the keywords 'perl' and 'template' take me to links on template processing using perl or HTML::Template).
I would like to create a template for my favorite editor so that I can start new projects easily with all of the boring-yet-useful bits already filled out. For example: path to the perl interpreter, date created, author, program name, description, changelog, license, etc.
What bits of information do best practices dictate should be included? Anyone have a template they're willing to share?
Thanks in advance.