Re: How to sub class-es

but I have to point out that I do not have enough time to learn Moose at this moment

I'm afraid you will soon find out that not learning an OO-framework (such as Moo) but rolling your own was a waste of time after all.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

Comment on Re: How to sub class-es

Replies are listed 'Best First'.
Re^2: How to sub class-es by gnosti (Hermit) on May 17, 2020 at 22:55 UTC
I'm afraid you will soon find out that not learning an OO-framework (such as Moo) but rolling your own was a waste of time after all. Moo and friends have limitations and bring added complexity that not everyone may want. c.f. "Moose Made me a Bad OO Programmer" by Tadeusz Sośnierz I've done fine for a medium size project using Object::Tiny to create accessors, and Role::Tiny to separate out functionality of large ("God") classes.	[reply]

Replies are listed 'Best First'.

Re^2: How to sub class-es
by gnosti (Hermit) on May 17, 2020 at 22:55 UTC

I'm afraid you will soon find out that not learning an OO-framework (such as Moo) but rolling your own was a waste of time after all.

Moo and friends have limitations and bring added complexity that not everyone may want. c.f. "Moose Made me a Bad OO Programmer" by Tadeusz Sośnierz

I've done fine for a medium size project using Object::Tiny to create accessors, and Role::Tiny to separate out functionality of large ("God") classes.

[reply]

In Section Seekers of Perl Wisdom