use Perl

• Lovely! (Score:2)

  by Ovid (2709)

  You know, an Acme::Module::Starter might be called for! The POD alone is worth the price of admission.
  • Re: (Score:1)

    by sigzero (5768)

    That is too funny...
• Use TT (Score:2)

  by brian_d_foy (44)

  My module start point is just a directory of TT templates that I process with ttree. When I want to change the templates, I don't deal with code. :)

  #!/usr/bin/perl
   
  use Cwd;
  use File::Spec;
   
  my $module = $ARGV[0] || prompt( "Module name> " );
  my $dist   = $module; $dist =~ s/::/-/g;
  my $file   = $module; $file =~ s/.*:://; $file .= ".pm";
   
  my $cwd    = File::Spec->catfile( cwd(), $dist );
   
  system
          join " ",
     
• Not surprising considering how programmers think (Score:1)

  by scot (6695)

  To me it comes down to the fact that documentation, commenting code, and cleaning up or "refactoring" code is generally considered the most boring part of IT. So eliminating the boilerplate as you mention would fall under that category. It's just another one of those things that might fall under the category of accumulating "technical debt."
  
  It's the tradeoff between "quick and dirty"; and elegant. There's been much hoo-ha about how long Perl 6 is taking to be completed; as I've said before I don't min
• The author of this module is a mindless drone (Score:1)

  by kid51 (5328)

  ExtUtils::ModuleMaker is designed to be customizable to your individual preferences. See, e.g., ExtUtils::ModuleMaker::PBP. Would that help?
  • Re: (Score:1)

    by Alias (5735)

    Well, I pretty much have what I want working now, so I'm happy to leave it as is.
    
    It also means I can add other functionality like auto-commiting to my repository etc.
    
    So I'm happy for now.