richi.moran at gmail.com
Fri Feb 11 19:23:06 UTC 2011
On Fri, Feb 11, 2011 at 3:29 PM, Igor Stasenko <siguctua at gmail.com> wrote:>
> you can do something like:
> World blahblah...
> I am sure, if you look deeply there is a way to iterate over all submorphs
I think you mean
and in my experience it is *much* faster than iterating over all objects.
> And don't say that it will be slower than iterating over all objects
> in object memory.
> But even if you do, then why not iterating over morphs , so you don't
> have to use #isMorph
> Morph allSubInstancesDo: ...
> >>>> So, all you need is to think a bit more broadly in a sense, how to
> >>>> improve system and remove crappy patterns from use,
> >>>> but not blindly replace one pattern by another , which replacing one
> >>>> flood with another.
> >>> If you can show a pattern for this which has comparable performance
> >>> the
> >>> current implementation, then I'm all ears.
> >> Since when performance became the only criteria for reasoning about
> >> implementation quality?
> > Who said it's the only criteria (besides you)?
> > Btw, the previous implementation of this method was slow. It annoyed me
> > much that I changed it to the current implememtation which uses
> > allObjectsDo: and is 22x faster for a Trunk image.
> Why then to not change the implementation?
> Why you fighting with imlementation being slow, without getting
> interested why it implemented in such manner,
> which is the main reason why its so slow.
> Did you asked yourself, why cleaning up the undo commands in morphs is
> responsibility of SmalltalkImage class ??
> Why it is not responsibility of morphic world/project.
> So, yeah.. keep fighting with consequences instead of dealing with cause.
> > Levente
> Best regards,
> Igor Stasenko AKA sig.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev