Hi guys just for your information this mailing-list is Pharo-development. You can discuss a lot of topics in Pharo-users but in Pharo-dev we would really appreciate to get a bit focused. I try to read all the mails to be able to help people but it means processing a lot of mails :) and I really have a lot of duties that are not pharo related and I would appreciate to get my pharo time for pharo.
Stef On Dec 1, 2012, at 9:52 PM, Alexandre Bergel wrote: >> Ok, wow. Didn't know that. >> >> So, whenever I change a class, I have both the old version and the new >> version co-existing? >> And then the instances are told to become: instances of the new class? > > Yes > > Alexandre > >> >> 2012/12/1 Alexandre Bergel <alexandre.ber...@me.com>: >>>> Are there some vital things that are impossible if #become: is >>>> missing? (no irony in my question, I just don't know) >>> >>> Changing a class on the fly. #become: is used behind the scene > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >
