Re: [Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-06-19 Thread Ronie Salgado
There are not news yet, but I will try to take a look on this. This is actually anoying, so I will find a workaround soon. 2015-06-17 18:16 GMT-03:00 Natalia Tymchuk : > Are there any news? > > > On 06 May 2015, at 13:00, Alexandre Bergel > wrote: > > > > Apparently moose will soon move to Pharo

Re: [Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-06-17 Thread Natalia Tymchuk
Are there any news? > On 06 May 2015, at 13:00, Alexandre Bergel wrote: > > Apparently moose will soon move to Pharo 5. Maybe next week or so. > > Alexandre > > > >> Le 6 mai 2015 à 04:34, Lusa Nicolas a écrit : >> >> Hi, >> >> thanks for the quick answer, I'll switch back to pharo4 for

Re: [Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-05-06 Thread Alexandre Bergel
Apparently moose will soon move to Pharo 5. Maybe next week or so. Alexandre > Le 6 mai 2015 à 04:34, Lusa Nicolas a écrit : > > Hi, > > thanks for the quick answer, I'll switch back to pharo4 for the moment. > > Cheers, > Nicolas > >

Re: [Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-05-06 Thread Lusa Nicolas
Hi, thanks for the quick answer, I'll switch back to pharo4 for the moment. Cheers, Nicolas

Re: [Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-05-05 Thread Alexandre Bergel
Hi Nicolas, > I just noticed that with today's pharo5 image the inspector breaks if > Woden-Roassal is in the image. > The reason is that there is a recursive call to String>>#findAnySubStr: > startingAt: . This is caused by the deprecation of such method then defined > as String>>#findAnySubs

[Pharo-users] Woden-Roassal pharo5 inspector bugs

2015-05-05 Thread Lusa Nicolas
Hi, I just noticed that with today's pharo5 image the inspector breaks if Woden-Roassal is in the image. The reason is that there is a recursive call to String>>#findAnySubStr: startingAt: . This is caused by the deprecation of such method then defined as String>>#findAnySubstring: startingAt