in reply to Re: Proper way to call subclass methods?
in thread Proper way to call subclass methods?

OK, I will noodle through this. Thanks. I'm using Daman Conway's old book from 2000 to get up to speed. I guess it's a bit obsolete because it doesn't mention "parent" and "base". Are there any more recent Perl OO books I should be looking at?

$PM = "Perl Monk's";
$MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon";
$nysus = $PM . $MCF;
Click here if you love Perl Monks

  • Comment on Re^2: Proper way to call subclass methods?

Replies are listed 'Best First'.
Re^3: Proper way to call subclass methods?
by Your Mother (Archbishop) on Mar 08, 2016 at 17:32 UTC

    16 years is a long time in IT/CS. Conway's book is still worth absorbing though. This has some good stuff. I reach for Moo much faster than Moose but opinions differ and some monks think both are overkill/foolish. :P

      I'm thinking I should learn "old school" OO Perl for now before taking on Moo and Moose. Is that a good idea?

      $PM = "Perl Monk's";
      $MCF = "Most Clueless Friar Abbot Bishop Pontiff Deacon";
      $nysus = $PM . $MCF;
      Click here if you love Perl Monks

        It's an interesting idea. Conway's book really got my brain going in a way none of my other 30 Perl books did. I think, however, the newish kits approach the problem-space... maybe not holistically but with a wide view. So, hard to say. Doing it manually, aka the hard way, will certainly improve your appreciation for the tools and rationale for the OO-frameworks.

        I'm thinking I should learn "old school" OO Perl for now before taking on Moo and Moose. Is that a good idea?

        Neither :) see High level OOP query

        Then skim through perlobj and perlootut

        "old school" or Moo... that is the easy part (less typing or more typing) :)

        The hard part is knowing When to Use OO and how to model your classes

        Like Modern Perl says Creating and using objects in Perl with Moose (Moose, pp. 107) is easy. Designing good programs is not. It's as easy to overdesign a program as it is to underdesign it....