Op 20-8-2013 13:39, Esteban Lorenzano schreef:
but you can do
MyClass class>>#someOtherMethodWhichIsNotCalled"initialize"
super someOtherMethodWhichIsNotCalled"initialize".
etc...
the restriction is just for the method called #initialize :)
Just to make it simple, I guess :-)
I write is somewhere down...
Tim
Esteban
On Aug 20, 2013, at 12:22 PM, Tim Hendriks <t...@dds.nl> wrote:
OK Thanks a lot.
I won't call super initialize on de Class side.... Don't know why.... I just
don't.... simpel....
Thanks for trying to explain why.
Op 20-8-2013 12:00, Esteban Lorenzano schreef:
no, you do not call super initialize in class side initialize method.
You do not do:
MyClass class>>#initialize
super initialize. "THIS IS BAD"
... rest of initialization.
we should add a Lint rule with that, btw.
On Aug 20, 2013, at 11:52 AM, Tim Hendriks <t...@dds.nl> wrote:
Ok, I don't want to know :-)
Just as a rule: don't call super initialize on the Class site ? But I can use
(the message) initialize on the Class site (for initializing applications roots
in seaside for example) but just do'nt use super in it. Correct?
Thanks Tim
Op 20-8-2013 11:45, jtuc...@objektfabrik.de schreef:
Hi Tim,
the problem is not the send of #super to a class, but the call of #initialize
of #super on the class side.
As long as you are not interested in very confusing details about the
inheritence hierarchy of Class and Metaclasses and stuff, don't ask, just do as
you're told ;-)
You can, however, have a look at chapter 13 Classes and Metaclasses of the "Pharo By
Example" book (http://pharobyexample.org) if you want to know more.
A very short and incomplete explanation is that the superclass of a class is
never the superclass of the class of its instances, because all classes are
instances of the same class ( I told you you prabably don't want to know right
now ;-) ).
Joachim
Am 20.08.13 11:34, schrieb Tim Hendriks:
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
<mailto: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
<http://smalltalkhub.com/#%21/%7EPharo/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.
