But that's no excuse not to learn it. Without knowing what the problem domain was, i can't agree that OO was not the right choice for your job.
"Yes, I can re-use some of my modules, but most of them were special-purpose..."
What's good about OO is that it teaches you how to make those decisions: when to generalize, when to specialize.
"...script has ballooned ... Mostly due to having to make constructors ... for about 10 different objects"
Don't forget the one line constructor:
Sorry you now have a bad taste for OO. To be honest, i would rather teach someone OO in a language like Ruby or even Java before throwing them into Perl. Perl's OO is, in my opinion, more difficult to grasp than other languages. It's easy to turn OO into a big ball of mud, it's very easy to do that with Perl OO - but, personally, i love Perl OO!sub new { bless {}, shift }
Any chance of you throwing a couple of these objects on your scratchpad? I'm really curious to see what you have done. And congrats for finishing the project!
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)
In reply to (jeffa) Re: OO 2 death?
by jeffa
in thread OO 2 death?
by Cestus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |