On Jan 30, 2012, at 4:30 PM, Andrew P. Black wrote:

Hmm, is this really right? I'm used to seeing "Error in printString ..."

Wasn't that a bug we already fixed? In 1.4 I can do Collection new and I get the subclass responsibility... And I thought we back-ported the fix to 1.3, too. Need to check...

On 30 Jan 2012, at 11:12 , Milan Mimica wrote:

...

On 30 January 2012 19:31, Andrew P. Black <black@cs.pdx.edu> wrote:

But I don't understand the root cause. Printing eventually sends do:, which is self subclassResponsibility. Why don't we get a clean failure?

Andrew

When an error occurs during error handling (which includes printing) it is not a clean failure. Emergency evaluator pops up in that case.

-- Marcus Denker -- http://marcusdenker.de