Re: [Pharo-users] Code loading/unloading order

> Le 26 janv. 2017 à 12:25, webwarrior a écrit : > > Thanks. > > Reason why I ask is because I ran into some issues with slots that depended > on other classes in the package (when creating slot, like SomeSlot new > valueClass: SomeOtherClass). I had to move slots into

Re: [Pharo-users] Code loading/unloading order

Thanks. Reason why I ask is because I ran into some issues with slots that depended on other classes in the package (when creating slot, like SomeSlot new valueClass: SomeOtherClass). I had to move slots into separate package to make it work. Like when you work on your code it's all good, but

Re: [Pharo-users] Code loading/unloading order

Hi, I think it is not documented, and it's usually strange that people write code dependent on this order. However, to anwer your questions, you can look at MCPackageLoader>>#basicLoadDefinitions. More specific below: On Tue, Jan 24, 2017 at 3:07 PM, webwarrior wrote: > It

[Pharo-users] Code loading/unloading order

It is not documented. What happens when I load a package? Are all classes created first, and then methods are added, or classes are loaded one-by-one with all their methods? What about Slots? Are they added to classes after all classes are loaded? Do they have their methods by that time? What is