Am 31.10.2013 11:24, schrieb Sven Van Caekenberghe:
Obviously, abstract classes should not be instanciated,
This is of course known.
Now, the actual error happens in the environment (debugger,
inspector, printString mechanisms): they see a collection and try to
work with it, since it is an i
Michael,
On 31 Oct 2013, at 11:00, Michael Paap wrote:
> 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
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
> Hello list,
>
> in our OOP course we noticed some behaviour of an abstract method, w
