[squeak-dev] some CharacterScanner methods weirdly send setStopConditions twice

Chris Muller asqueaker at gmail.com
Mon Sep 30 20:19:02 UTC 2013

Don't know if it would have helped, but just a friendly reminder that
there's also the new "mc origin" feature in the Inbox which opens an
MCVersion inspector on the earliest version known to contain that

Assuming the change occurred after the invention of Monticello, and
the author put the _why_ in there, of course..   ;)

On Sat, Sep 28, 2013 at 2:51 PM, Nicolas Cellier
<nicolas.cellier.aka.nice at gmail.com> wrote:
> Sending twice some complex initialization message with inter-mixed state
> messing smells...
> This is for example in CharacterBlockScanner>>buildCharacterBlockIn:
> I found http://bugs.squeak.org/view.php?id=3570 which were included in
> Graphics-ar.39
> (in 3.9 repository see http://source.squeak.org/39a/Graphics-ar.39.diff)...
> ...but the doubled setStopConditions was there already, the change just
> swapped some lines...
> This is not in the Multilingual branch, so it seems newer than 2002...
> Does anyone remember where to dig to understand why, which bug it solves,
> which feature it supports, and whether it is really needed?

More information about the Squeak-dev mailing list