On 09.07.2013, at 23:28, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-09, at 21:23, Frank Shearar frank.shea...@gmail.com wrote:
On 9 July 2013 19:45, Camillo Bruni camillobr...@gmail.com wrote:
I continue my rant with should:raise:description:
a) self should: [ Error signal:
Camillo wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
Yes, it has a special meaning AND is very helpfull - ESPECIALLY when you start
with tests first (XPStyle):
Usually one writes the tests and then you try to get them from red over yellow
to
green:
red:
Am 10.07.2013 um 08:15 schrieb Torsten Bergmann asta...@gmx.de:
Camillo wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
Yes, it has a special meaning AND is very helpfull - ESPECIALLY when you
start with tests first (XPStyle):
Usually one writes the
Hi Camillo:
On 10 Jul 2013, at 02:46, Camillo Bruni camillobr...@gmail.com wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
To make your live a little more difficult, I actually introduced an additional
type of failure on top of that: blue for still to be
Hi,
We mananged to nearly review (and often integrate) almost all pending fixes and
enhancements.
There are 4 issues left:
https://pharo.fogbugz.com/f/filters/36/Review
It would be nice if more people would be involved. If *you* don't comment, it
might be we will do the
wrong thing?
Hi folks, while working on the new debugger, I've come up with some
questions...
*is there any other implementation for dynamic widgets other that the
current one?
I do not get your question ...
This is related to my previous question about dynamic spec, if it's
possible to define
On 2013-07-10, at 09:08, Stefan Marr smallt...@stefan-marr.de wrote:
Hi Camillo:
On 10 Jul 2013, at 02:46, Camillo Bruni camillobr...@gmail.com wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
To make your live a little more difficult, I actually
30261
-
11138 Implementation of user directories is a mess
https://pharo.fogbugz.com/f/cases/11138
11152 Monticello not creating proper changes when moving trait methods to/from
class
https://pharo.fogbugz.com/f/cases/11152
Diff information:
20612
-
10569 Backport 2.0: Better Interrruptionche
https://pharo.fogbugz.com/f/cases/10569
10940 Backport 2.0: 10925 Use caching in Gofer
https://pharo.fogbugz.com/f/cases/10940
Diff information:
http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.782.diff
On Wed, Jul 10, 2013 at 10:21 AM, Marcus Denker marcus.den...@inria.frwrote:
11138 Implementation of user directories is a mess
https://pharo.fogbugz.com/f/cases/11138
yea. Now, you can ask FileLocator for the desktop, documents, home...
directories!!
--
Damien Cassou
Hello,
So in the current spec debugger, the receiver's inspector widget is changed
dynamically. Even if it looks like the same because it is always an
inspector, it is not the same widget (could be any subclass of EyeInspector
depending on receiver's type). So it is possible to change the main
30262
-
11089 Update Zn+Zdc July 2013
https://pharo.fogbugz.com/f/cases/11089
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linux-stable-worker/329/
1 regressions found.
Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory
On 2013-07-10, at 08:05, Max Leske maxle...@gmail.com wrote:
On 09.07.2013, at 23:28, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-09, at 21:23, Frank Shearar frank.shea...@gmail.com wrote:
On 9 July 2013 19:45, Camillo Bruni camillobr...@gmail.com wrote:
I continue my rant
On 10 juil. 2013, at 11:24, Camillo Bruni wrote:
On 2013-07-10, at 08:05, Max Leske maxle...@gmail.com wrote:
On 09.07.2013, at 23:28, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-09, at 21:23, Frank Shearar frank.shea...@gmail.com wrote:
On 9 July 2013 19:45, Camillo
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
Please do not do away with this distinction.
Cheers,
Doru
On Jul 10, 2013, at 10:34 AM, Damien Cassou damien.cas...@gmail.com wrote:
On Wed, Jul 10,
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
In which sense?
As a programmer I have to tackle them both the same way: start debugging.
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/330/
2 regressions found.
Tests.Polymorph.Widgets.FileDialogWindowTest.testIssue6406
Tests.Release.ReleaseTest.testObsoleteClasses
On 2013-07-10, at 14:09, Sven Van Caekenberghe s...@stfx.eu wrote:
Maybe we should not throw away the distinction, I am used to it as well.
But what Camillo means, I think, is that in the end it does not matter.
For example, if I have a unit test for some object's #printString both the
On Jul 10, 2013, at 2:06 PM, Marcus Denker marcus.den...@inria.fr wrote:
30263
-
11142 For 3.0: 11102 FileSystemError
https://pharo.fogbugz.com/f/cases/1114
This seems to fail on the mac, and the windows build is not finishing since
14minutes.
I think I will revert the
Error – defect in the human thought process made while trying to
understand given information, solve problems, or to use methods and
tools. In the context of software requirements specifications, an error
is a basic misconception of the actual needs of a user or customer.
Fault – concrete
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/331/
1 regressions found.
Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory
Hi,
On Jul 10, 2013, at 1:47 PM, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
In which
Which one is the right repository?
http://smalltalkhub.com/#!/~PharoExtras/Phexample
or
http://smalltalkhub.com/#!/~Phexample/Phexample
And if they are copies of each other could you please change one of those to
include a comment/pointer that the other one is in use?
Norbert
On 2013-07-10, at 14:47, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
On Jul 10, 2013, at 1:47 PM, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
Hi:
On 10 Jul 2013, at 14:50, Norbert Hartl norb...@hartl.name wrote:
Which one is the right repository?
http://smalltalkhub.com/#!/~PharoExtras/Phexample
or
http://smalltalkhub.com/#!/~Phexample/Phexample
As far as I remember, Camillo was going to clean that up. The PharoExtras repo
was
thanks Doru
Am 10.07.2013 um 15:01 schrieb Tudor Girba tu...@tudorgirba.com:
On Jul 10, 2013, at 2:50 PM, Norbert Hartl norb...@hartl.name wrote:
Which one is the right repository?
http://smalltalkhub.com/#!/~PharoExtras/Phexample
or
http://smalltalkhub.com/#!/~Phexample/Phexample
Oh, so programming in the debugger was a myth?
I'm disappointed ;)
2013/7/10 Damien Cassou damien.cas...@gmail.com
On Wed, Jul 10, 2013 at 8:16 AM, Norbert Hartl norb...@hartl.name wrote:
I use them. I always fix the red tests first because they are mostly
easier to fix and some of them
Am 10.07.2013 um 15:33 schrieb Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com:
Oh, so programming in the debugger was a myth?
I'm disappointed ;)
Well, I would say it is neither a myth nor has it to be forced. There is always
more than one work mode.
So you program only in the
2013/7/10 Stephan Eggermont step...@stack.nl
Erwan wrote:
I didn't commit since the past week. I'm trying many things with Spec.
Don't worry i'm working on it :)
Just commit the experiments. They provide valuable input on what
you already tried. You can mark the successfull experiments in
On 9 July 2013 22:45, Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com wrote:
should not raise an exceptional event whose description does not include
wow, who is crooked enough to use double negation ;)
is it a convenience method for following:
[ self dosomething ] on: Error do: [:ex |
On 10 Jul 2013, at 16:44, Mariano Martinez Peck marianop...@gmail.com wrote:
Hi guys. There is a method in Glorp that looks like this:
Dialect #convert: aByteArray toStringWithEncoding: encodingName
self isVisualWorks ifTrue: [^aByteArray asStringEncoding: encodingName].
self
Hi guys. It may happen that both, Glorp and the database driver in
question, support an encoding strategy. In Pharo, both drivers
(NativePostgresDriver and OpenDBXDriver) does support setting an encoding
and take care of it. But Glorp supports that as well.
I want to avoid doing double
On 10 Jul 2013, at 17:00, Mariano Martinez Peck marianop...@gmail.com wrote:
Hi guys. It may happen that both, Glorp and the database driver in question,
support an encoding strategy. In Pharo, both drivers (NativePostgresDriver
and OpenDBXDriver) does support setting an encoding and take
2013/7/10 Sven Van Caekenberghe s...@stfx.eu:
So...where should I do the conversion? At Glorp level or at database driver
level?
And IMHO at the lowest possible level. If you have an SQL VARCHAR column, the
driver should convert bytes to a normal Smalltalk String. An OR mapper is a
client
Hi Dale,
The introduction of Opal as the new compiler has some side effects.
The problem is reported here : https://pharo.fogbugz.com/default.asp?11141
Today, Camillo and I worked on this problem and we should come with a solution
soon.
Once integrated in the image, you should have the same kind
''
On Jul 9, 2013 11:43 AM, Clément Bera bera.clem...@gmail.com
wrote:,,.
They may be useful. Imagine you are too lazy to create /a subclass of
Error, but not lazy enough to create a test and copy paste a String.
Then you write in your method:
self error: 'some strange error happened'
What you want is a TAssertable#should:raise: that:
- takes a one arg block as second argument that is evaluated with the
exception thrown
- fails if no exception is raised
Then please call it #should:raise:suchThat:
That's what is in upcoming SUnit 5.0 [1]
Also I would avoid using traits in
Someone who is not me need to look at this:
11140 #addDeferredUIMessage: is always sent directly to WorldState
https://pharo.fogbugz.com/f/cases/11140
39 matches
Mail list logo
