[Pharo-dev] Issue #11876 (Do not allow shouldnt:raise: Error) and Seaside dev. on Pharo 3.0

Norbert Hartl norbert at hartl.name
Thu Oct 24 05:52:34 EDT 2013


Am 24.10.2013 um 08:05 schrieb Marcus Denker <marcus.denker at inria.fr>:

> 
> On 23 Oct 2013, at 23:07, Stéphane Ducasse <stephane.ducasse at 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.
> 
+1

Norbert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131024/93074ceb/attachment-0002.html>


More information about the Pharo-dev mailing list