I do not know the answer but this would be great to get the interpreter back on track.
Stef On Sep 5, 2009, at 7:03 PM, Andrey Larionov wrote: > I attach screenshot of debugger to better understanding of context > (why not provide in debuger an stacktrace exporter, or i miss > somthing?) > > > On Sat, Sep 5, 2009 at 20:53, Stéphane Ducasse<[email protected] > > wrote: >> Let us know if you find and we need to react in pharo. >> >> Stef >> >> On Sep 5, 2009, at 6:16 PM, David T. Lewis wrote: >> >>> I'm sorry, I did not read your original posting carefully enough. >>> The >>> classes that implement coerceTo:sim: are Integer, Array, Bitmap, >>> CArray, >>> and CObjectAccessor. So I do not know what the problem is in this >>> case. >>> Sorry for the confusion. >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > <Interpreter.png>_______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
