Despite the hype, OO isn't a panacea.
It's entirely possible to create lousy designs using OO,
and unfortunately, it sounds like that might be the situation you're running into.
When I was first exposed to OO principles,
I found that many of the touted OO advantages
had analogs in things I considered plain old good software engineering practice from my straight-C days:
using libraries to avoid re-inventing the wheel (code re-use), "private" structure definitions (data encapsulation), well-defined accessor APIs (method calls).
OO does go beyond that, though, making it easy to do nifty things like inheritance that are, at best, laborious without an OO language.
Learning OO has actually made me a more effective
non-OO programmer, too, so don't let a first sour taste turn you off. There's plenty of value in learning the principles, if only to give your mental toolbox an alternate way of approaching programming problems.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.