On Mar 31, 2012, at 6:43 PM, Fabrizio Perin wrote:

Hi, I was coding in Pharo1.3 Latest update: #13315

By evaluating some tests again the emergency evaluator pop up (Pharo doesn't like me lately :) ). This time at least I figure that some elements i use in the tests do not print properly:

<error in printString: evaluate "collection printString" to debug> so if you do

Collection new printString.

this was fixed in 1.4 Now Collection is an abstract class so do not expect that instantiating make any sense.

the image seems to hang the only was to stop it is to do command period.

In 1.4 at least the debugger pops up telling that "do:" should be implemented in a subclass. To make the image hang you should do

SequenceableCollection new printString.

I don't know if those are suppose to be bugs or my inappropriate use of Collection and SequenceableCollection. I just reported.

Cheers, Fabrizio