in reply to Re^2: To use or not to use OO Perl
in thread To use or not to use OO Perl
Anyhow, OO is fine -- but don't think it's about reuse or maintainability or massive inheritance hierachies or anything like that. It's mostly about state and clean interfaces -- or, at least -- that's how it SHOULD be. The number of real world problems correctly modelled by massive inheritance trees are few and far between.
If you ask me, OO is a method for modelling problems that are based on interactions between Things. Not all problems are easily or properly modelled this way. When used for suitable problems, object-oriented code can be stunningly elegant; when used for unsuitable problems, it's usually a steaming heap of
crap unnecessary complexity.
tilly argued this point better and more completely: The world is not object oriented.
Yours in pedantry,
F o x t r o t U n i f o r m
"Lines of code don't matter as long as I'm not writing them." -- merlyn
|Replies are listed 'Best First'.|
Re^4: To use or not to use OO Perl
by perlcapt (Pilgrim) on Oct 26, 2004 at 02:34 UTC
In Section Seekers of Perl Wisdom