Woden-Roassal pharo5 inspector bugs

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: .
The first call gets the  String>>#findAnySubStr:  startingAt: which gives the warning and calls ByteString>>#findAnySubstring:  startingAt: (in Woden-Roassal package) which calls String>>#findAnySubStr:  startingAt: and so on.

Now my question is, do you plan on moving Woden to Pharo5?

Sorry to bother you all the time.

Cheers,
Nicolas

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>>#findAnySubstring:  startingAt: .
> The first call gets the  String>>#findAnySubStr:  startingAt: which gives the warning and calls ByteString>>#findAnySubstring:  startingAt: (in Woden-Roassal package) which calls String>>#findAnySubStr:  startingAt: and so on.

Arg…
I personally use Moose for my own development. This is the reason of this failure.
I will ask to the moose community whether we can move to Pharo 5.

> Now my question is, do you plan on moving Woden to Pharo5?

That was not in my radar until you send this email.

> Sorry to bother you all the time.

No problem at all!

Cheers,
Alexandre

Hi,

thanks for the quick answer, I'll switch back to pharo4 for the moment.

Cheers,
Nicolas

Apparently moose will soon move to Pharo 5. Maybe next week or so.

Alexandre

Are there any news?