On 23 Oct 2013, at 23:07, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:

Hi,

just as info: looks like already fixed Pharo issue #11876 makes problem for Seaside in 3.0:

http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005509.html
http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-October/005540.html

It would be a bit sad that Seaside does not work in Pharo3.0
I imagine that Philippe is tired. 

I would revert the change and add a rule that check that the argument of shouldnt:raise: should not be an Error

yes, people are not willing to change code all the time� we should do things like that in rules first and only later
hard errors.