in reply to Bundling commonly-used modules into a toolset

Seems extremely interesting. But in passing it may be worthwile to remind a cheap alternative that would yield the absolute maximum of portability: editor macros or templates. For example you may create a template like thus 
#!/usr/bin/perl

use strict;
use warnings;



__END__

[download]
If you know that you're using a certain module, say File::Find, quite often, then you can include it with a cmt in said template: 
# use File::Find;

[download]
and you may create a suitable macro for inserting subs: I don't have any, but with my editor (jed]) it would be easy to create one that would ask me for a name, say foo and create this code for me: 
sub foo {
    my $var=shift;

}

[download]
positioning the cursor on the empty line, or on $var, to allow me to switch to a more sensible var name.

Replies are listed 'Best First'.
Re^2: Bundling commonly-used modules into a toolset
by Perl Mouse (Chaplain) on Oct 25, 2005 at 14:06 UTC
    But in passing it may be worthwile to remind a cheap alternative that would yield the absolute maximum of portability: editor macros or templates.
    Seconded. Whenever I start a perl file, I start with a macro that loads one of three templates for me (one for programs, one for non-OO modules, and one for OO modules). They include things like a she-bang line, use strict, use/no warnings, modules I often use with a '#' in front of the use so I don't pay a price when I don't need them, but can enable them by just deleting a single character.

    And Perl isn't the only language I use templates for. I also have them for C, awk, FORTRAN, and Pascal. Not to mention tons of (retired) templates for all kinds of projects.

    Perl --((8:>*
[reply]

In Section Meditations