All you've done is pass the buck from "self" to "me". And given the hijinks Roger pulled with Swarm, self might respond to "jump" one day, but throw an error the next ... just like, say, today I can throw a baseball with my right arm. But if I break that arm, tomorrow I might not be able to throw the base ball. So, who's "me" in this temporal game? The receiver of the signal or the arm that does the throwing?
On 08/07/2017 02:54 PM, Marcus Daniels wrote: > In Smalltalk and Objective C "self" is an alias for any receiver object from > the point of view of that object. > > E.g. if someone tells me to "jump" I can implement that by sending them a > "howHigh" message, or I can send that message to my(self)! > > self is a handle to the stuff in me, especially the methods I implement. > Different people have different stuff. > Some folks mix-in methods they model in others and some do not. Others > can't imagine doing mix-ins and only can get their head around inheritance. > (Very tribal are they!) > > Some full stop when they see objects they don't understand. Others just send > crap to each other all day. -- ☣ glen ============================================================ FRIAM Applied Complexity Group listserv Meets Fridays 9a-11:30 at cafe at St. John's College to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ by Dr. Strangelove
