October 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» win - Build # 405 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

[Pharo-project] pharo-2.0-tests Â» linux - Build # 405 - Failure!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

[Pharo-project] [update 2.0] #20339

by Marcus Denker

20339 ----- Issue 6803: Activate the new Pango ST80 style http://code.google.com/p/pharo/issues/detail?id=6803 Issue 6802: remove ChangeSetBrowser http://code.google.com/p/pharo/issues/detail?id=6802 Issue 6794: CommandLine Configuration installer http://code.google.com/p/pharo/issues/detail?id=6794 -- Marcus Denker -- http://marcusdenker.de

Oct. 13, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 404 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 404 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

Re: [Pharo-project] [Lsehub-staff] Do you know any code that can be better understood with its test?

by StÃ©phane Ducasse

bitShift: look at the tests ((1 bitShift: 100) bitShift: -100) = 1 On Oct 13, 2012, at 4:47 PM, Damien Cassou wrote: > I'm looking for a piece of code that is hard to understand by looking > at the source code but which has unit tests that help understanding > the behavior. > > Do you have any idea? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 13, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 403 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

[Pharo-project] pharo-2.0-tests Â» mac - Build # 403 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 13, 2012

Re: [Pharo-project] Do you know any code that can be better understood with its test?

by mail list

How about this: -- takes a string and does a global replacement on substrings.. gsub: aString "from email correspondence with Nicolas Cellier " | newString | newString:= self parameters associations inject: aString into: [:subst :assoc | assoc key asRegex copy: subst replacingMatchesWith: assoc value]. ^newString testBasicGsub | string result| "aDict at: 'test' put: 'testreplaced'; at: 'hello' put: 'hello'; at: 'hello2' put: 'hello2replaced'." string:='test'. result:= FiconabGsub replace: string using: aDict. self assert: result='testreplaced'. string:='test test'. result:= FiconabGsub replace: string using: aDict. self assert: result='testreplaced testreplaced'. S. On 13 Oct, 2012, at 10:47 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I'm looking for a piece of code that is hard to understand by looking > at the source code but which has unit tests that help understanding > the behavior. > > Do you have any idea? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Oct. 13, 2012

[Pharo-project] Do you know any code that can be better understood with its test?

by Damien Cassou

I'm looking for a piece of code that is hard to understand by looking at the source code but which has unit tests that help understanding the behavior. Do you have any idea? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 13, 2012