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 incomplete/degenerate one, things break/loop.
Ok. This explains, why just "doing" SequenceableCollection new is ok, while "printing" causes problems. Thank you for your explnation.
The question is: should there be an explicit error message when an abstract class is instanciated, is that even possible ?
This may be difficult, because the instantiation of a not abstract subclass normally /is/ an instantiation of the abstract super class, isn't it? And in Smalltalk we have no concept of abstractness in the language itself, but only by convention. Greetings, Michael