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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Maybe you can write an article about it when you win? This is just the kind of apples-to-apples comparison that's so hard to come by and yet can be so persuasive.

    -sam

    • I think it is so hard because the skill levels of each person skews the end result. I have been steadily learning Perl but the Java person is just picking it up again after about a year.
  • Get CGI::Application::Pligin::TT and use both!

    http://cpan.uwinnipeg.ca/module/CGI::Application::Plugin::TT [uwinnipeg.ca]

    • I am the level in my Perl learning where I really need to focus on one or the other. Once I get that down then I will look at combining them. One of my goals was to use "as little as possible" in my development of the web app.

      I am leaning towards CGI-Application and HTML-Template as HT is a "simple" yet "powerful" paradigm. That and I really dig CA's run modes.

      • Well the plugin allows you to use C::A's runmodes but use TT as the template language ( no need for [% USE CGI %] in your templates or any other of the more involved constructs that can make TT more like programming than templating).

        • I meant to say this:

          The plugin that I mentioned allows you to replace HTML::Template with TT as the templating language.

          TT as a templating language is very easy, most of the time you don't need anything more complex than [% PROCESS %] [% FOREACH %] or [% variable.property %]

          I prefer using TT, but good luck with your project with whichever approach you choose.