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.
  • I haven't touched Catalyst in a long time, but when I did, I seem to recall that they implemented plugins via multiple inheritance. I urged them to consider something different, including a trait model. It would have been far more sane, but they were concerned (if I recall correctly) about backwards compatibility. Traits solve so many problems and I wish more people would take a look at them. Of course, it would help if I completely rewrote the Class::Trait documentation.

    • Of course, it would help if I completely rewrote the Class::Trait documentation.

      Okay, go ahead. : )
  • The basic issue is that everyone wants a piece of the request (and response) class. It's the logical place to put app-specific per-request/response attributes & behavior. I note that the Catalyst docs seem to encourage you to do this:

    Where does the documentation say that?

    --
    Ordinary morality is for ordinary people. -- Aleister Crowley
    • Right here [cpan.org].

      BTW, I'm on the Catalyst list if you want to move this discussion there.
      • Argh. That was even _my_ fault. I hadn't done that much with Catalyst, and this document is really outdated. Fortunately, I'm about to finish a new version that focuses more on best practices.
        --
        Ordinary morality is for ordinary people. -- Aleister Crowley