#1113 Clear usages of initClass / #setupClass:

Originally at 2014-12-06T15:35:59Z by Herbert Vojčík In some of the core APIs in `boot.js` (addMethod, removeMethod, setConstructor), `initClass` functionality is performed, that is, the change propagates where needed. In other (create class, remove class etc.) it is not performed and smalltalk code must call `ClassBuilder >> #setupClass:` to achieve that. It would be nice if there wasn't any dichotomy and it would be clear where the changes are propagated / whether there is two layers of API (low-level vs. high-level). Now, it is unclear. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/6817272-clear-usages-of-initclass-setupclass?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F79201&utm_medium=issues&utm_source=github). </bountysource-plugin>

Done in 0.16.0.