I can empathise with your learning of OO. Once you get past the buzz, it's just a way of designing programmes that's good for certain situations. Very useful for things like writing text validators for GUIs as an abstract class and subclassing all windows from that to inherit the validator functions for every text field, but I'd rarely create a class for some linear text processing.
Regards,
Liam Clarke
On 6/9/05, Lee Cullens <[EMAIL PROTECTED]> wrote:
Javier, Allen, Kent, Liam
Hmm, I think I understand what you all are saying. Basically, my
familiar take on "code reuse" (the function model) as used in the
utility is essentially not rewriting any more of a block than what is
different, as opposed to "do all" blocks with convoluted switching.
Whereas what it seems to me you are saying is levels of functional
abstraction more akin to the Unix model.
My only prior experience with OOP was with Lingo several years ago in
a variable record file use, which was simple to grasp.
Obviously my take is flawed, so I will study the material noted,
reread my Learning Python Part VI, and take another stab at it.
No doubt this is "rank amateurish" to you all - somewhat like I felt
back in the 80's when a "senior analyst" asked me how to use more
than one output file in a COBOL program ;') Anyway, starting with
assembler in the 60s, and doing my last substantial technical work in
the 80s with C and Pascal, I have a bit of catching up to do :~)
Thank you all for pointing me in the right direction,
Lee C
--
'There is only one basic human right, and that is to do as you damn well please.
And with it comes the only basic human duty, to take the consequences.'
_______________________________________________ Tutor maillist - Tutor@python.org http://mail.python.org/mailman/listinfo/tutor
