[squeak-dev] 4.5 -- how should we proceed then?
Chris Muller
asqueaker at gmail.com
Wed Dec 25 03:16:35 UTC 2013
> Colin has revendicated the right to call self initialize from within
> initializeWithXXX: initializer.
> You denied this right because that would open the door to arbitrarily ignore
> initialize.
Yes, that is the core of my complaint. I just cannot help to believe
all code should be at the highest level it can be. I think it
provides better accessibility to a kind of system scripters and
app-developers want to use.
> But I think you are mistaking here.
> Indeed, contrarily to what you said, each initialize SHOULD call another
> initialize (*), that is super initialize.
As the aforementioned rebel that I am, I'm afraid "should" usually
leaves my curiosity unsatisfied. However, I can understand the appeal
of wanting to see all initialization right there in one designated
initializer method, including even the line that does the
default-values.
> So once we agree that initializeWithXXX is a proper initialize method as
> HashedCollection>>initialize: is,
> The problem is solved and we can revert to previous version.
Out of respect for Colin and democracy and progress, I will revert the changes.
I've been writing Constructor Parameter Methods for 20 years. I won't
change others' code about this again, but I must continue using my
style for my own trunk contributions.
More information about the Squeak-dev
mailing list
|