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

2013-10-25 Thread Stéphane Ducasse
> > With respect to Seaside (and its cross-platform-ness), this is probably a > good decision, for now. > > But it is fundamentally unfair to call this an arbitrary unimportant change > meant to annoy people. On the contrary ! I even think that there are too many > methods in TAssertable and t

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

2013-10-25 Thread Stéphane Ducasse
tx! On Oct 24, 2013, at 1:55 PM, Torsten Bergmann 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

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

2013-10-25 Thread Stéphane Ducasse
>>> >> >> yes, people are not willing to change code all the time… > > We are willing to change the code where there is a clear benefit. For example > it's hard to argue that the new filesystem is an improvement over > FileDirectory. We have a partically working Spec based UI for the servers.

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

2013-10-24 Thread Sven Van Caekenberghe
On 24 Oct 2013, at 13:55, Torsten Bergmann 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/

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

2013-10-24 Thread Torsten Bergmann
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