Just tried in Pharo 1.4, 2.0 and 3.0. It fails in all of them. The error doesn't happen when sending #add: though. Try doing SequenceableCollection new and the same thing will happen. 2013/10/31 Michael Paap <mpaap@netcologne.de>
Hello list,
in our OOP course we noticed some behaviour of an abstract method, which I cannot explain. Maybe you can help me:
If I do the following
SequenceableCollection new add: 123
I would expect an Error. The method add: is not implemented in SequenceableCollectionbut inherited from collection, where it's only statement is
self subclassResponsibility
But in reality, Pharo seems to enter an endless loop, consuming more and more memory.
Can someone please explain to me, what happens here?
Greetings, Michael
-- Bernat Romagosa.