Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Max Leske
So first: as Sven said Sequenceable collection is abstract. Still I would consider what you found a bug since it provides the implementations that produce the behavior you reported. I can reproduce it in a 40 with vmLatest, and the proble occurs whenever either #do: or #size is sent.

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Max Leske
And 30 has the exact same problem of course (just checked). On 16.09.2014, at 08:39, Max Leske maxle...@gmail.com wrote: So first: as Sven said Sequenceable collection is abstract. Still I would consider what you found a bug since it provides the implementations that produce the behavior

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Sven Van Caekenberghe
Well, since SequenceableCollection overwrites #do: breaking its superclass' contract, it should also overwrite #size as subclassResponsibility - at least. That would break the loop, no ? The discussion about catching infinite recursion loops is old and comes up every couple of weeks. It should

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Max Leske
Slice in inbox. Required reimplementing #size in Stack and LinkedList. Name: SLICE-Issue-14022-Infinite-loop-in-simple-subclasses-of-SequenceableCollection-MaxLeske.1 Author: MaxLeske Time: 16 September 2014, 9:23:03.047607 am UUID: a911f5cc-bc3e-4579-bbf4-ad6f61d1199c Ancestors:

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Sven Van Caekenberghe
On 16 Sep 2014, at 09:24, Max Leske maxle...@gmail.com wrote: Slice in inbox. Required reimplementing #size in Stack and LinkedList. Argh, that is a bit ugly. Stack#size is not needed as it inherits from LinkedList, right ? Otherwise: checked and all Collection tests ran OK. Name:

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-16 Thread Max Leske
On 16.09.2014, at 09:50, Sven Van Caekenberghe s...@stfx.eu wrote: On 16 Sep 2014, at 09:24, Max Leske maxle...@gmail.com wrote: Slice in inbox. Required reimplementing #size in Stack and LinkedList. Argh, that is a bit ugly. Stack#size is not needed as it inherits from

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-15 Thread Sven Van Caekenberghe
SequenceableCollection is abstract. Collection methods select: #isSubclassResponsibility. = {Collection#add:. Collection#do:. Collection#remove:ifAbsent:} The inspector probably fails because it cannot enumerate the collection. But I haven't actually tried your code. On 15 Sep 2014, at

Re: [Pharo-dev] Strange behavior in Pharo 3.0

2014-09-15 Thread Jordi Delgado
Yes, that would be ok. But the problem is not the Inspector failing, the problem is that Pharo crashes, and that should not happen. Bests, Jordi SequenceableCollection is abstract. Collection methods select: #isSubclassResponsibility. = {Collection#add:. Collection#do:.