|
|
Posted by steve on 10/25/05 00:11
| if the OP doesn't see how OOP
| benefits his development process, there's a good chance it actually
| doesn't.
i never though polarized sunglasses would help my fly-fishing...till i tried
it. ;^) the biggest hurdles is truly not being able to see (pun intended) an
opportunity...whether in fishing or software development.
| > generally though, with sufficient complexity, it is easier
| > to manage the specifics of validation and presentation in
| > the manner he described...
|
| It's quite possible. But there will be a cost to that; the OOP will
| have to rewrite his base of reusable code (assuming he has one) from
| scratch.
unless of course he's asking now as a course of future action in which case,
knowing that it is a good idea may prompt him to use better design patterns
to simplify and organize his functionality. if he *is* applying oop to an
existing code base, simple refactoring during routine maintenance averts
most of the costs. it doesn't have to be a whole-sale proposition.
| So, again, the OP is the only person who has information
| sufficient to conclude that OOP is (or is not) beneficial to his
| development process.
"beneficial" being relative to the assumptions made here. oop in general is
a standard for a reason.
anyway...hope i'm not irritating you.
cheers.
Navigation:
[Reply to this message]
|