http://www.perlmonks.org?node_id=1059769


in reply to Re: High level OOP query
in thread High level OOP query

I also strongly suggest you learn how Moose and Moo work. They bring a sane object system into the Perl land and have some very, very good developers working on them.

Moo/Moose later :)

I think its better to first learn why/when/what/whichway ... and only later deal with mechanics/implementation/how-details like moo/moose/badger...bless

To wit http://www.developer.com/author/Matt-Weisfeld-81520.htm / https://en.wikiversity.org/wiki/Object_Oriented_Software_Design#Introductory_Articles

Building Skills in Object-Oriented Design S.Lott Building Skills in Object-Oriented Design Step-by-Step Construction of A Complete Application Roulette / Craps / Blackjack / Testing

Why yes, this is just an opportunity to link some new-to-me stuff I found :)

  • Comment on Re^2: High level OOP query ( Building Skills Object-Oriented Design Mindset Development )

Replies are listed 'Best First'.
Re^3: High level OOP query ( Building Skills Object-Oriented Design Mindset Development )
by stonecolddevin (Parson) on Oct 25, 2013 at 22:29 UTC

    I say Moose/Moo now, because that completely sidesteps the frustrations of having to figure out how to coerce native perl into doing OO. It's got a fairly standard OO syntax that you will be able to translate OO concepts into without too much hassle. Then, you can backtrack and learn how it's done with perl sans Moo(se) and it will make much more sense.

    Three thousand years of beautiful tradition, from Moses to Sandy Koufax, you're god damn right I'm living in the fucking past

      I say Moose/Moo now ...

      Great point ... so you can write some Moo for OP?

      I think first pictures on paper, then Moo