3 ms·
A "method" is just a programming construct. A message in OOP is sent to an object to tell it to do something itself. In an OO approach, rather than have a Hamm
by aryehof 10y ago
A "method" is just a programming construct. A message in OOP is sent to an object to tell it to do something itself.
In an OO approach, rather than have a Hammer hit a Nail, the Hammer sends a message to a Nail which knows how to be hit.
- digi_owl 10y agoThat makes me wonder though, if i send a message to the same object from two different senders, will the first message affect the outcome of the second? If not then there is plainly little difference between the two, as either action gets a new pristine instance. All in all, this seems to be a whole lot of syntactical hair splitting.
- aryehof 10y agoWhat an object does when it receives a message is hidden, and entirely up to that object. >>> All in all, this seems to be a whole lot of syntactical hair splitting Or, simply a case of not understanding.
- digi_owl 10y agoOr not having the 10000 feet outlook. Checking some links to Kay's responses elsewhere, i get the impression that unless we basically toss the notion of a programs as a singular compiled file of binary, and replace it with some kind of abstract notion of work that can happen on a single computer, or across the net as a whole, the distinction between a message and a method is academic at best. Because for message as a concept to make sense, it has to be seen as someone standing on a rooftop shouting "can someone please hit that nail?!", and then wait around until someone shouts back "done!". Without that you just end up with a carpenter talking to himself "hit nail, done, hit nail, done, hit nail, done".
- infinite8s 10y agoYes, exactly. Step back (wayyyyyyy back) from your current understanding of what software should look like.