NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
In the near future, the probability is close to zero. In the distant
future, I'll be dead, and posterity can do whatever they like... :-) --lwall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
OK. Thanks! (Score:1)
use warnings;
use strict;
my($MODNAME) = @ARGV;
mkdir($MODNAME);
chdir($MODNAME);
mkdir("t");
mkdir("lib");
mkdir("lib/$MODNAME");
my $fh;
foreach my $file (qw(README MANIFEST MANIFEST.SKIP Makefile.PL Changes))
{
open($fh, ">$file");
}
open($fh, ">lib/$MODNAME.pm");
open($fh, ">t/00basic.t");
open($fh, ">Makefile.PL") || die "Can't open Makefile.PL: $!";
print $fh <<"EOF";
use ExtUtils::MakeMaker;
WriteMakefile(
'N
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Re:OK. Thanks! (Score:1)
Re:OK. Thanks! (Score:1)
Yes. I started thinking about that and then decided I would never get the program written, let alone posted, if I handled that issue.
But, as the rough rocks in a stream get worn down smooth, I'm sure I will walk across that enough times in the future I (or someone else) will be motivated to fix that.
Hmmmmm. How about Inline::Files to hold to contents of all those files that get set up?
J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers
Reply to This
Parent