- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Necessity of TDD with Smalltalk

by kilon

I dont think a debugger can ever replace TDD for two reason a) Tests are faster way to find bugs that don't want to be found ;) b) Tests are more than debugging tools (A) If you have already created a large suite of tests then all it takes is to fire those tests and just wait for the result to come out. Much fastert than going one by one bug. Also I dont know if the same applies for smalltalk but when i was coding for python not all code was executed and so I did not see all the bugs my code contains. So I had to test the app myself in many diffirent ways and I quickly found out that writing tests was way faster in the long run. (B) tests also make sure that your code behaves the way you want to behave and produces the result you want to produce. It may not be a bug per se, just a weird behavior. They also set a design pattern for your code to follow in the future. Generally speaking I use TDD for long code or code that is going to be maintained in the long run and get larger and larger. I think in that scenario TDD really excells. TDD is very popular in python, its part of the main library cpython(unittesting.py) comes with and there is also a third party library called "Nose" that even offer more features. I think TDD helps you keep your sanity in the long run especially with big projects and complex code. Debuggers are more like microscopes while i see TDD more like Satelites on orbit. ;) -- View this message in context: http://forum.world.st/Pharo-dev-Necessity-of-TDD-with-Smalltalk-tp4691867p4… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 6, 2013

Re: [Pharo-dev] [Screencast]: Pharo Smalltalk's New TxText: The Power of Clean Code

by Igor Stasenko

On 6 June 2013 11:14, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/6/6 Sean P. DeNigris <sean(a)clipperadams.com> >> >> https://vimeo.com/67752734 > > > Cool. Did you publish code? > >> >> >> >> Very short and simple video describing my experience while implementing >> replacing a text morph's cursor with a block cursor to signify vim normal >> mode. Shows how I was able to accomplish something in a few minutes which >> seemed impossible with TextEditor and friends. >> >> Things are getting really exciting around here :) > > > We talk with Alain about Rubric and in near future we will have selection as > morph's. So we can tune selection border width, color, present it with > ellipse and etc. umm? text selection? what ellipse if it can span multiple lines/pages of text? > >> >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Screencast-Pharo-Smalltalk-s-New-TxText-The-Power-of-… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > -- Best regards, Igor Stasenko.

June 6, 2013

Re: [Pharo-dev] Lowecase class names

by kilon

When I was coding with python I used underscore instead of camel case. MorphWindow -> morph_window and I also like common lisp approach MorphWindow -> morph-window I always found camel case very weird , since back in 1996 that i saw it used in C++. And even though I have grown up reading it , I am still find it difficult especially with lenghty code. Of course what happens in pharo should be a democratic decision, but I dont think allowing for freedom to choose is a bad thing. Thats how python works, and most programming languages. Only pharo / squeak than I know of foces usage of Camel case, and capitalisation of first letter in classes . Cant say i find it a good thing. -- View this message in context: http://forum.world.st/Pharo-dev-Lowecase-class-names-tp4690963p4691925.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 6, 2013

Re: [Pharo-dev] Lowecase class names

by Esteban Lorenzano

Hi, On Jun 6, 2013, at 9:43 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 6, 2013, at 9:29 AM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: > >> On 03/06/13 12:18, Marcus Denker wrote: >>> >>> On Jun 3, 2013, at 1:13 PM, Jan Vrany <jan.vrany(a)fit.cvut.cz> wrote: >>> >>>> I thought so. Attached hack removes it. >>>> >>> >>> Of course a complete rewrite of the class builder is ready for integrationâ¦ >>> >>> https://ci.inria.fr/pharo-contribution/job/Slot/ >>> >>> So the question is if it makes sense to add this one? >> >> Hm...I'm not sure what you mean. > > I mean that we should not change ClassBuilder now if it is replaced next week. > (man power is limited). > >> Let put it this way? Any chance >> 2.0 will allow lowercase class names? well... since allowing lowercase class names does not exactly qualify as "bugfix", I would say it will not be there in 2.0. The idea is that the trunk development moves each year (with each version) and older version becomes just bugfix supported. Otherwise we will be ever-maintaining older versions, something that not even apple does (with all the capacity they have). So I would vote also "no" :) > > The problem with changing 2.0 is that all change always has side-effect impacting > othersâ¦ often in very non-expected ways. > > So I am a bit skeptical to change 2.0, especially anything in the dark places like the class > builder. > > If it is a change that is for the good of all users, is makes sense to invest time and effort. > But changing the class builder in 2.0 just for an experiment of one person? I would tend to > argue to not do it. > > The current development version is another story. There we can break things, have time to stabilize. > > Marcus

June 6, 2013

Re: [Pharo-dev] Lowecase class names

by StÃ©phane Ducasse

Do not expect us to change the classbuilder in 2.0 :) I agree with marcus Stef >>> I thought so. Attached hack removes it. >>> >> >> Of course a complete rewrite of the class builder is ready for integrationâ¦ >> >> https://ci.inria.fr/pharo-contribution/job/Slot/ >> >> So the question is if it makes sense to add this one? > > Hm...I'm not sure what you mean. Let put it this way? Any chance > 2.0 will allow lowercase class names? If not, fine with me, I'll patch > ClassBuilder before loading my packages. > > Jan >

June 6, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Marcus Denker

>> > > I recreated a work image (20605), tested and saw the two failures: > > FileSystem.Tests.Disk.FileHandleTest.testTruncate > Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment > > Then loaded SLICE-Issue-10411-flush-after-nextChunkPut-ThierryGoubier.1 (the changes are visible :)) > > And ended with those two tests green. > > (But with > Refactoring.Tests.Changes.RBRefactoringChangeTests.tesValidTraitComposition(|2|3|4) failures) > > Now, 606 isn't available, no? I use get.pharo.org/20 Ah, then that is the problemâ¦ normally it is pushed automatically, but this seems to have failed. I think we should just wait till the infrastructure is back and then redo the build. Marcus

June 6, 2013

Re: [Pharo-dev] [Screencast]: Pharo Smalltalk's New TxText: The Power of Clean Code

by Denis Kudriashov

2013/6/6 Sean P. DeNigris <sean(a)clipperadams.com> > https://vimeo.com/67752734 Cool. Did you publish code? > > > Very short and simple video describing my experience while implementing > replacing a text morph's cursor with a block cursor to signify vim normal > mode. Shows how I was able to accomplish something in a few minutes which > seemed impossible with TextEditor and friends. > > Things are getting really exciting around here :) > We talk with Alain about Rubric and in near future we will have selection as morph's. So we can tune selection border width, color, present it with ellipse and etc. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Screencast-Pharo-Smalltalk-s-New-TxText-The-Power-of-… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

June 6, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Goubier Thierry

Le 06/06/2013 10:33, Marcus Denker a Ã©crit : > > On Jun 6, 2013, at 10:25 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 06/06/2013 08:32, Marcus Denker a Ã©crit : >>> >>> On Jun 5, 2013, at 4:10 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>>> Le 05/06/2013 16:04, Marcus Denker a Ã©crit : >>>>> >>>>> On Jun 5, 2013, at 4:03 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>>> >>>>>> Le 05/06/2013 15:56, Marcus Denker a Ã©crit : >>>>>>> >>>>>>> On Jun 5, 2013, at 2:39 PM, no-reply(a)ci.inria.fr wrote: >>>>>>> >>>>>>>> https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin… >>>>>>>> >>>>>>>> 3 regressions found. >>>>>>>> FileSystem.Tests.Disk.FileHandleTest.testTruncate >>>>>>>> Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment >>>>>>>> Tests.Monticello.MCClassDefinitionTest.testLoadAndUnload >>>>>>>> >>> >>> Ok, so we have 2 independent issues; >>> >>> 1) testTruncate failing on recent Ubuntu in both 2.0 and 3.0 >>> >>> https://pharo.fogbugz.com/f/cases/10852 >>> >>> 2) The slice I integrated was wrong / not complete: >>> >>> FileSystem.Tests.Disk.FileHandleTest.testTruncate >>> Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment >>> >>> >>> https://pharo.fogbugz.com/f/cases/10415 >>> >>> For this, I think the best would be to submit the missing code in some machine readable form >>> as I right now am a bit confused about what exactly "adding the right flush methods" means. >> >> As far as I can browse, SLICE-Issue-10411-flush-after-nextChunkPut-ThierryGoubier.1 contains the correct code. >> > When I merge it in 2.0 606 I do not see any change.. > >> Do you want me to retry generating a slice? > > Maybe something is wrong with the image that was used to run the tests? Maybe that one actually was 605? > > Marcus I recreated a work image (20605), tested and saw the two failures: FileSystem.Tests.Disk.FileHandleTest.testTruncate Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment Then loaded SLICE-Issue-10411-flush-after-nextChunkPut-ThierryGoubier.1 (the changes are visible :)) And ended with those two tests green. (But with Refactoring.Tests.Changes.RBRefactoringChangeTests.tesValidTraitComposition(|2|3|4) failures) Now, 606 isn't available, no? I use get.pharo.org/20 Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 6, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Marcus Denker

On Jun 6, 2013, at 10:25 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > Le 06/06/2013 08:32, Marcus Denker a Ã©crit : >> >> On Jun 5, 2013, at 4:10 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> Le 05/06/2013 16:04, Marcus Denker a Ã©crit : >>>> >>>> On Jun 5, 2013, at 4:03 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>>> >>>>> Le 05/06/2013 15:56, Marcus Denker a Ã©crit : >>>>>> >>>>>> On Jun 5, 2013, at 2:39 PM, no-reply(a)ci.inria.fr wrote: >>>>>> >>>>>>> https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin… >>>>>>> >>>>>>> 3 regressions found. >>>>>>> FileSystem.Tests.Disk.FileHandleTest.testTruncate >>>>>>> Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment >>>>>>> Tests.Monticello.MCClassDefinitionTest.testLoadAndUnload >>>>>>> >> >> Ok, so we have 2 independent issues; >> >> 1) testTruncate failing on recent Ubuntu in both 2.0 and 3.0 >> >> https://pharo.fogbugz.com/f/cases/10852 >> >> 2) The slice I integrated was wrong / not complete: >> >> FileSystem.Tests.Disk.FileHandleTest.testTruncate >> Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment >> >> >> https://pharo.fogbugz.com/f/cases/10415 >> >> For this, I think the best would be to submit the missing code in some machine readable form >> as I right now am a bit confused about what exactly "adding the right flush methods" means. > > As far as I can browse, SLICE-Issue-10411-flush-after-nextChunkPut-ThierryGoubier.1 contains the correct code. > When I merge it in 2.0 606 I do not see any change.. > Do you want me to retry generating a slice? Maybe something is wrong with the image that was used to run the tests? Maybe that one actually was 605? Marcus

June 6, 2013

Re: [Pharo-dev] [regression reporter]regression occurred

by Goubier Thierry

Le 06/06/2013 08:32, Marcus Denker a Ã©crit : > > On Jun 5, 2013, at 4:10 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Le 05/06/2013 16:04, Marcus Denker a Ã©crit : >>> >>> On Jun 5, 2013, at 4:03 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> >>>> Le 05/06/2013 15:56, Marcus Denker a Ã©crit : >>>>> >>>>> On Jun 5, 2013, at 2:39 PM, no-reply(a)ci.inria.fr wrote: >>>>> >>>>>> https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=lin… >>>>>> >>>>>> 3 regressions found. >>>>>> FileSystem.Tests.Disk.FileHandleTest.testTruncate >>>>>> Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment >>>>>> Tests.Monticello.MCClassDefinitionTest.testLoadAndUnload >>>>>> > > Ok, so we have 2 independent issues; > > 1) testTruncate failing on recent Ubuntu in both 2.0 and 3.0 > > https://pharo.fogbugz.com/f/cases/10852 > > 2) The slice I integrated was wrong / not complete: > > FileSystem.Tests.Disk.FileHandleTest.testTruncate > Refactoring.Tests.Changes.RBRefactoringChangeTests.testPerformChangeComment > > > https://pharo.fogbugz.com/f/cases/10415 > > For this, I think the best would be to submit the missing code in some machine readable form > as I right now am a bit confused about what exactly "adding the right flush methods" means. As far as I can browse, SLICE-Issue-10411-flush-after-nextChunkPut-ThierryGoubier.1 contains the correct code. Do you want me to retry generating a slice? Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 6, 2013