Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Repository services partially resume 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • I’d suggest at least adding CGI::Application or CGI::Prototype to the mix. Neither adds significant weight, except for declaring dependencies on template systems that they don’t actually need in order to function. Maybe you can also get Sam Tregar and/or merlyn to fix that.

    Among template systems, Template::Simple is probably what you want. HTML::Template doesn’t have non-core dependencies either though.

    • I won't be using a templating module, it would really just be overkill.

      Instead I'm using a templating method which implements very small subset of Template Toolkit syntax... i.e. it just supports [% foo %]. :)

      sub template {
              my $self = shift;
              my $html = shift;
              my $args = shift || $self->args;
              foreach ( 0 .. 10 ) {
                      # Allow up to 10 levels of

      • If that is really all you need… then go for it. But I find that even minimal scripts outgrow that functionality very quickly.

        My main point was that you should take a look at the lightweight web frameworks for Perl, though. Even the tiniest apps benefit from them in my experience – as soon as you have more than 2 screens, you need to impose structure somehow. (Of course, variations of Greenspun’s 10th Rule apply to many things. You could build a rudimentary framework in situ – much

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.