Alan Gauld said unto the world upon 2004-12-20 15:51:
I hope that short history of OOP clarifies rather than
confuses! :-)
Alan G.
Thanks for that Alan. Seems to clarify thing to me ;-)
Best,
Brian vdB
___
Tutor maillist - [EMAIL PROTECTED]
http://mail
> > Its another reason why you should never refer to
> > an object or method *calling* another method
> > (as Pilgrim does). Rather think of the method
> > sending a *message* to the self object which
> > invokes the appropriate method.
> The contrast you suggest between calling a method and sendi
Alan Gauld said unto the world upon 2004-12-20 09:27:
Its another reason why you should never refer to
an object or method *calling* another method
(as Pilgrim does). Rather think of the method
sending a *message* to the self object which
invokes the appropriate method. This decoupling
of message
y.
Alan G.
- Original Message -
From: "Brian van den Broek" <[EMAIL PROTECTED]>
To: "Tutor" <[EMAIL PROTECTED]>
Sent: Saturday, December 18, 2004 1:31 PM
Subject: [Tutor] class overriding question
> Hi all,
>
> instead of sleeping, I've been up all
Kent Johnson said unto the world upon 2004-12-18 08:53:
Yup, that's right!
Attribute access (the dot operator '.') is an operation that happens at
runtime, and each attribute access stands alone. Every attribute access
goes through the same search path, starting with self, then the class
(type)
Yup, that's right!
Attribute access (the dot operator '.') is an operation that happens at runtime, and each attribute
access stands alone. Every attribute access goes through the same search path, starting with self,
then the class (type) of self, finally the base classes. So, in your example, s
Hi all,
instead of sleeping, I've been up all night finally attacking my
apprehension about classes. I think I'm mostly getting the hang of it --
I managed to convert a 300 line procedural script into (what I think is)
a fully object-oriented approach. :-)
I made a lot of use of Mark Pilgrim's Di
