and besides, one could always redefine #new in subclasses to avoid calling #initialize 2009/8/14 Schwab,Wilhelm K <bschwab@anest.ufl.edu>:
A newbie - welcome! Â We're always happy to spread the addiction. Â To find out for yourself, do this:
 1) open a workspace, type Object new.  2) select the new text, right click and choose debug-it  3) step into #new, and note that it take you to     ^self basicNew initialize
At the risk of oversimplifying, that creates a no-frills instance and then invokes #initialize. Â Not all Smalltalks do this; it is either a bug or a feature depending on one's perspective, though I confess I have bigger things to worry about at present.
Bill
-----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Daniel P Zepeda Sent: Friday, August 14, 2009 11:52 AM To: Pharo-project@lists.gforge.inria.fr Subject: [Pharo-project] Incompatibilities was: #< if at first you dont succeed..
On Aug 14, 2009, at 10:38 AM, Ken.Dickey wrote:
Squeak and Pharo already have some invompatabilities (e.g. not requiring #initialize after #new).
I'm sort of a newbie, can you elaborate on not requiring #initialize after #new somewhat, or point me to where it is documented, I searched around a little bit, but quickly got lost.
Thanks!
DZ
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.