[squeak-dev] #initialize to superclass [was Re: [squeak-dev] The
cunningham.cb at gmail.com
Thu Aug 27 21:36:09 UTC 2015
On Thu, Aug 27, 2015 at 5:14 AM, Levente Uzonyi <leves at elte.hu> wrote:
> Unless you have a very good reason to send #initialize to the superclass,
> you shouldn't do it.
> So, I have two questions:
1 - why should we not do this?
2 - if we shouldn't do it, then why does the system ALWAYS bug us about not
overriding #initialize when adding that method to the class side?
I am in the habit of adding it - because the message pops up, and I suppose
the system has a good reason for us to not override it. Maybe just a bad
habit on my part.
> On Thu, 27 Aug 2015, commits at source.squeak.org wrote:
> Marcel Taeumel uploaded a new version of Tests to project The Trunk:
>> ==================== Summary ====================
>> Name: Tests-mt.329
>> Author: mt
>> Time: 27 August 2015, 11:12:04.169 am
>> UUID: 2665a1ed-6312-1845-8181-d83c588cd161
>> Ancestors: Tests-mt.328
>> Fixes initialization problem with test preferences.
>> =============== Diff against Tests-mt.328 ===============
>> Item was added:
>> + ----- Method: PreferencesTestPreferences class>>initialize (in category
>> 'class initialization') -----
>> + initialize
>> + super initialize.
>> + self initializeDictionaryOfPreferences.!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev