use strict;
use warnings;
[download]

'nuff said. :-D

See (tye)Re: Stupid question. Glancing at it, it still is pretty much the template I use after all of these years. Some justifications are still collecting on my scratchpad I have moved into that node.

Nice. Very nice! I'll steal that...

#!/usr/bin/perl

use strict;
use warnings;

use Data::Dumper;
use Getopt::Long;
use Pod::Usage;
use Log::Log4perl;
use Log::Dispatch::FileRotate;

my $conf = undef;
my $log  = undef;
my $help = undef;
my $test = undef;
my $file = undef;

$conf = q(
  log4perl.category.Script          = INFO, ScreenAppender, ScriptFile
+RotateAppender

  log4perl.appender.ScreenAppender         = Log::Log4perl::Appender::
+Screen
  log4perl.appender.ScreenAppender.stderr  = 1
  log4perl.appender.ScreenAppender.layout  = PatternLayout
  log4perl.appender.ScreenAppender.layout.ConversionPattern=[%p] %d %F
+:%L - %m%n
  log4perl.appender.ScreenAppender.Threshold  = DEBUG

  log4perl.appender.ScriptFileRotateAppender           = Log::Dispatch
+::FileRotate
  log4perl.appender.ScriptFileRotateAppender.filename  = script.log
  log4perl.appender.ScriptFileRotateAppender.mode      = append
  log4perl.appender.ScriptFileRotateAppender.size      = 100000
  log4perl.appender.ScriptFileRotateAppender.max       = 5
  log4perl.appender.ScriptFileRotateAppender.layout    = PatternLayout
  log4perl.appender.ScriptFileRotateAppender.layout.ConversionPattern=
+[%p] %d %F:%L:- %m%n


);
Log::Log4perl::init( \$conf );
$log = Log::Log4perl::->get_logger(q(Script));

$log->debug("start") if $log->is_debug();

# GetOptions
GetOptions("help|?" => \$help,
           "test"   => \$test,
           "file=s" => \$file) or pod2usage(2);
pod2usage(1) if $help;

# ------ main ------

$log->debug("end") if $log->is_debug();

exit(0);

__END__

=pod

=head1 NAME

=head1 SYNOPSIS

=head1 OPTIONS

=head1 DESCRIPTION

=head1 TODO

=head1 SEE ALSO

=head1 AUTHOR

=cut
[download]

You should check out Perl Best Practices, it's an increadibly good book. Boilerplates on pp 133-139.

I have a very flexible three-part system that turns Vim (my favorite editor) into the perfect Perl IDE for me. Part 1 is a shell script that creates the file, adds a shebang, a dated comment with the author's name, and a 'use strict;' -

#!/bin/bash
# Created by Ben Okopnik on Mon Apr 28 11:41:01 EDT 2008

# Enter your name here; otherwise, your login name will be used
name=""

[ -z "$1" ] && { printf "Usage: $0 <file_to_create>\n"; exit; }
[ -f "$1" ] && { printf "File already exists!\n"; exit; }

printf "#!`which perl` -w\n" > $1
printf "# Created by ${name:-$USER} on `date`\nuse strict;\n\n\n" >> $
+1
chmod +x $1
vi + $1
[download]

The next two parts are Vim keymaps which live in my "~/.vimrc":

map <silent> <F2> :set filetype=perl<CR>:set kp=perldoc\ -f<CR>:0<CR>:
+-r!which perl<CR>I#!<ESC>$a -w<ESC>o# Created by Ben Okopnik on^[:r!d
+ate<CR>-J^<CR>iuse strict;<CR><CR>
map <F5> :w<CR>:![ -x "%:p" ]\|\|chmod +x "%:p"<CR>:!"%:p"
[download]

The 'F2' key inserts the same content as the script would plus sets up a few useful things in Vim - e.g., hitting the 'K' key now runs 'perldoc -f ' instead of 'man ' on the word under the cursor. Perl syntax highlighting is also enabled. The 'F5' key saves the file, makes it executable if it's not already, then presents you with the command line dialog where hitting the 'Enter' key will execute the current file. You can also enter any arguments your script needs at that time. When it's done, you're returned to your Vi session.

I realize that this is more than just a template, but for me, that bit is pretty much inextricably tied up with all the rest of it. I'm too Lazy to use just templates. :)

-- 
Human history becomes more and more a race between education and catastrophe. -- HG Wells

Mine is simple and includes a handful of use modules which I often don't. To 'Control+cut' 100 lines of stuff is all but instant so just jam in anything you tend to use and take out what didn't end up being necessary once you have your script pretty well drafted.