Le 29/03/2015 15:18, kilon alios a écrit : > For example message passing suppose to be this super powerful feature > , that diffirentiate from method calls in the essence that the user > does not need to know the internals of the class. But I have not seen > a class that take advantage of this feature inside pharo. In every > single case if I had exchanged the message passing with method calls I > would not have even noticed the difference. In every case I have > studied each message corresponds to a method with exactly the same > name. I am sure maybe one day will come handly , but I dont see why > one needs to explain a feature that rarely someone will use understand > how to code in a specific environment.
Hello, You may really take a look at the *first* paragraph of Alan Lovejoy's article mentioned in my previous message, and pass it to the student as well: http://www.smalltalk.org/articles/article_20100320_a3_Getting_The_Message.html Without this understanding, one fails to understand why #ifTrue: argument is a block, or why #and: message's argument is a block[] surrounded by parenthesis(), then the beginner may have a hard time to use correctly the class libraries. Best, -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu
