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.
  • TT (Score:2, Informative)

    I moved about a year ago to TT from H::T and haven't looked back. The extra power is great. I feel that you get a lot better separation of overall presentation and logic if you can move some of the presentation logic out into the template. You can defiantly cut down on lines of code which makes maintenance easier.

    The thing I really like about TT is that you can pass any kind of data type; hashes, arrays, objects, functions, etc and use them in your template. It also works nicely with Class::DBI which I am

  • Bug Report? (Score:3, Insightful)

    by samtregar (2699) on 2003.03.18 1:00 (#18010) Homepage Journal
    Do you want to file a bug report, or just cry about it? I'm more than happy to work on fixing bugs in HTML::Template but I haven't personally witnessed any problems in the syntax error detection code.

    In case you didn't read the docs, the proper place to report a bug in HTML::Template is here [cpan.org].

    -sam

    • Yeah, I will report an error today.

      Sorry to bitch about H::T so much, I think we should have been using TT a long time ago. I don't think H::T is suited to a project of this scale.

      when you are looking for a really stupid mistake (and these are the hardest to find as we all know) incorrect or lack of line numbers in error messages are deeply unhelpful.

      Bug reported via rt.

      I would probably have some problems to bitch about with TT if I used it everyday at work too, but I don't so H::T is going to get b

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;