Kilon, Do you have a preview version of the updated book? I would love to see it. Also would you consider adding some exercises will be a good addition? I think so....let me know and i guess i can merge the project i've started to the updated book. Best Nacho
Enviado desde Molto para iPad De: kilon alios Enviado: miércoles, agosto 27, 2014 09:50 a.m. Para: Any question about pharo is welcome Asunto: Re: [Pharo-users] Unintuitive behavior of class-side initialize I will be adding an "Introduction to Object Orientation" chapter to the new updated Pharo By Example online book, so I will add this to the chapter. The chapter will target people not familiar with Object Orientation and people new to coding. Its not an immediate target but it will happen till the end of the year. On Wed, Aug 27, 2014 at 3:44 PM, Mariano Martinez Peck <marianop...@gmail.com> wrote: On Wed, Aug 27, 2014 at 8:22 AM, webwarrior <r...@webwarrior.ws> wrote: As class is just an object in Smalltalk, it would be reasonable to believe that #initialize message is always sent to class on creation. However, that's not true. It is only sent to classes that redefine #initialize. Also sending super initialize may lead to problems. Ohhh yes. There is always a time for every Smalltalkers where you discover that doing super for class side initialize is not a good idea. Here was my time: http://forum.world.st/super-initialize-is-not-a-good-idea-for-Behaviors-td3086162.html None of these is mentioned in documentation (I assume Pahro By Example is the official one). It only says that #initialize is sent when class is loaded into memory. I think either this behavior should be made more consistent, or excplicitly mentioned in the docs. +1 to the documentation -- View this message in context: http://forum.world.st/Unintuitive-behavior-of-class-side-initialize-tp4775042.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. -- Mariano http://marianopeck.wordpress.com