"It does not emphasize the key features of OOP - message sending and late binding - or the tremendous benefits." I am glad it does not , because if it did , it would be not a Introductory chapter to OOP. "This is an important topic that should be written about by a master OOP practitioner." Good luck, are you willing to wait another 5 years ? Because newcomers to Pharo with no clue to OOP finding fragmented information around the book about classes and objects, dont think will wait that long. I doubt if they last even a day. On the subject of message passing there is dedicate chapter for it in Chapter 4 and its also explained in Chapter 5. Late binding again its an advanced subject that will need its own chapter. For now my focus is making sure the reader understand the very basics of OOP. Without such basic knowledge is pointless to talk about advanced OOP features in Pharo. One can easily write a book on OOP with Pharo to explain the full potential, but since there are very few people contributing to documentation it comes down to the fact that every single contribution counts and the fact that UPBE must have an Introduction to OOP 5 years ago. Furthermore, if people are so willing to help out, the repo is open to every potential contributor, you can edit the chapter or even erase and replace it with your own if you believe you are up to the task. Until a better alternative comes up , the work will go on. By the way I am supervising the chapter , even though the student writes it, I will be editing and improving it along the way and as it is , is very far from finished. It will be included to the book as a pull request when its finished. My personal opinion , rejecting an effort on documentation, whether its something that satisfy high standards or not, is something that the Pharo community cannot afford with the serious problem in the lack of documentation. Its an area that Pharo can use any help it can get.

Le 29/03/2015 13:19, kilon alios a écrit :

"It does not emphasize the key features of OOP - message sending and late binding - or the tremendous benefits."

I am glad it does not , because if it did , it would be not a Introductory chapter to OOP.

Hello, I don't know the article Sean is talking about so I am only discussing the point about message and late binding. What Sean explains is that message sending and late binding is at the essence of Smalltalk (and therefore Pharo). More over it is an *easy* concept to understand, and finally and probably more important: a learner getting it right at the first time will learn and understand *more easily* the way the Class libraries are built and practised. Hopefully there are already valuable resources on the topic one can reuse: http://www.smalltalk.org/articles/article_20100320_a3_Getting_The_Message.ht... Probably more: https://duckduckgo.com/?t=lm&q=smalltalk+essence+to+OOP And the points from Smalltalk creator: http://www.c2.com/cgi/wiki?AlanKaysDefinitionOfObjectOriented Thanks -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu