Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-25 Thread Camillo Bruni
On 2013-05-23, at 20:15, Clément Bera wrote: > Did you check the latest SUnit version before doing that ? I think it is > not integrated yet in Pharo. Yes I had a look at it, though not that much in detail. And I think not that much change on the global scale. I should check again I guess :)

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Clément Bera
Did you check the latest SUnit version before doing that ? I think it is not integrated yet in Pharo. 2013/5/23 Camillo Bruni > > On 2013-05-23, at 16:37, Sven Van Caekenberghe wrote: > > > > > On 23 May 2013, at 16:34, Camillo Bruni wrote: > > > >> > >> On 2013-05-23, at 16:26, Sven Van Caek

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Camillo Bruni
On 2013-05-23, at 16:37, Sven Van Caekenberghe wrote: > > On 23 May 2013, at 16:34, Camillo Bruni wrote: > >> >> On 2013-05-23, at 16:26, Sven Van Caekenberghe wrote: >> >>> >>> On 23 May 2013, at 15:59, Camillo Bruni wrote: >>> why? To me this does not make sense. I'd expect

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Sven Van Caekenberghe
On 23 May 2013, at 16:34, Camillo Bruni wrote: > > On 2013-05-23, at 16:26, Sven Van Caekenberghe wrote: > >> >> On 23 May 2013, at 15:59, Camillo Bruni wrote: >> >>> why? To me this does not make sense. I'd expect >>> >>> Error subclass: #AssertionFailure >> >> Yeah, I have asked myself

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Camillo Bruni
On 2013-05-23, at 16:26, Sven Van Caekenberghe wrote: > > On 23 May 2013, at 15:59, Camillo Bruni wrote: > >> why? To me this does not make sense. I'd expect >> >> Error subclass: #AssertionFailure > > Yeah, I have asked myself the same question quite often. > > I often write self assert:

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Sven Van Caekenberghe
On 23 May 2013, at 15:59, Camillo Bruni wrote: > why? To me this does not make sense. I'd expect > > Error subclass: #AssertionFailure Yeah, I have asked myself the same question quite often. I often write self assert: in production code, but then an #on:do: handler specifying only Error wo

Re: [Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Max Leske
+1 Maybe Halt et. al need to be put into a separate hierarchy (all of the classes the implement #defaultAction identically). On 23.05.2013, at 15:59, Camillo Bruni wrote: > why? To me this does not make sense. I'd expect > > Error subclass: #AssertionFailure >

[Pharo-dev] Halt subclass: #AssertionFailure

2013-05-23 Thread Camillo Bruni
why? To me this does not make sense. I'd expect Error subclass: #AssertionFailure