in reply to Missing base classes when called from Tk
I had program working in non-object oriented mode and have been converting to object oriented
Um, if it wasn't broke, why are you "fixing" it?
(only 2.3x in size (751 lines ->1776 lines), so far; :-) ).
It must be my own naivete regarding OO concepts (which are admittedly somewhat foreign to me still), but I would have expected that a "proper" OO design would yield fewer lines of code than an old-fashioned procedural/structured design.
If you have a working non-OO version, and an equivalent OO version would entail writing 2 or 3 times more lines of code, what exactly is the benefit you derive from an OO solution, such that it would offset all the extra effort to create it (and presumably, with so many more lines of code, the extra maintenance load that it's likely to impose)?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Missing base classes when called from Tk
by perl-diddler (Chaplain) on Sep 27, 2007 at 08:19 UTC |