Classes forming the tree structure (one class can have many subclasses). A class initialization usually done for initializing properties shared by class and all its subclasses, and sent automatically to tools like Monticello when it loads the code to each separate class. So, if we use 'super initialize' we will end up initializing superclass 100 times if it has 100 subclasses.
Moreover, if we strictly follow that rule, the class initialization will endup in Behavior>>initialize (look at that method and guess what will happen if you run it) On 20 August 2013 11:34, Tim Hendriks <t...@dds.nl> wrote: > I'am just learning (a few weeks) .... so why not use super in Class? > > Thanks Tim > > Op 20-8-2013 11:29, Igor Stasenko schreef: > > Thanks for your hard work! > > 1 important remark: > > NBXLibTypes class>>initialize > super initialize. > Display := #NBXLibDisplay. > > > > Never use 'super initialize' for class initializers. > > > > > > On 20 August 2013 09:42, Torsten Bergmann <asta...@gmx.de> wrote: > >> I just wrapped this in NB last week, so if you have NativeBoost and >> Windows >> you can use: >> >> NBWin32Process getCurrentProcessId >> >> (requires the latest packages from >> http://smalltalkhub.com/#!/~Pharo/NativeBoost) >> >> I'm sure on any other platforms there are API's as well to get the PID, >> like >> getpid on Unix. Should be easy to wrap in NB if you follow this tutorial: >> >> >> https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSuccessfulBuild/artifact/NativeBoost/NativeBoost.pier.html >> >> Bye >> T. >> >> >> >> >> > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.
