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

Stéphane Ducasse stephane.ducasse at inria.fr
Fri Oct 25 03:28:53 EDT 2013


tx!

On Oct 24, 2013, at 1:55 PM, Torsten Bergmann <astares at gmx.de> wrote:

> From the comments I think we can agree that it is a better to have a lint rule
> instead of breaking things the way it was introduced by the original issue #11876. 
>  
> I therefore opened an issue 
>   https://pharo.fogbugz.com/f/cases/11989/shouldnt-raise-Error-from-issue-11876-is-too-offensive
> and uploaded a slice 
>  
>   SLICE-Issue-11989-shouldntraise-Error-from-issue-11876-is-too-offensive-TorstenBergmann.1
>  
> to Pharo30Inbox on STHub (http://smalltalkhub.com/mc/Pharo/Pharo30Inbox/main) that
> removed #validateShouldntException: 
>  
> I used a fresh 3.0 image (Pharo3.0 Latest update: #30519)
>  
> Please test so it can be integrated and we can continue to focus on more interesting stuff.
>  
> Thanks
> Torsten
>  
>  
>  

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131025/40262998/attachment-0002.html>


More information about the Pharo-dev mailing list