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

[Pharo-project] Re: #2

by nicolas cellier

Igor Stasenko <siguctua@...> writes: > > hello stef, > > recently i poked with scanner/parser and i wonder what possible > literals/combinations are correct and what is not: > > - a well known: > > #word , #keyword(s) -- Symbolic literal > #- #* ... etc. Symbolic literal > #( ...) -- array literal > > - now what about these: > > #123 -- number, or '123' asSymbol? > > ##( ... ) --- ?? > ##word --- ?? > ##... -- ??? > ###... --- ??? > Hehe that reminds me http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-May/117145.html http://lists.squeakfoundation.org/pipermail/squeak-dev/2007-May/117153.html I see not all are fixed in old compiler. Also note the discrepancy between parsing and printing You might want to fix #isLiteralSymbol: too...

Oct. 10, 2008

Re: [Pharo-project] #2

by Igor Stasenko

2008/10/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Apparently #2 value is a number? > but the parser parses it. > hello stef, recently i poked with scanner/parser and i wonder what possible literals/combinations are correct and what is not: - a well known: #word , #keyword(s) -- Symbolic literal #- #* ... etc. Symbolic literal #( ...) -- array literal - now what about these: #123 -- number, or '123' asSymbol? ##( ... ) --- ?? ##word --- ?? ##... -- ??? ###... --- ??? > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Oct. 10, 2008

Re: [Pharo-project] History and SUnit

by Damien Pollet

On Fri, Oct 10, 2008 at 1:25 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: >> - I don't understand the "Progress" feature. What I did is run the tests, >> then "Store results", then I fixed a failing test, then "Run Failures", then >> "Show progress". But nothing happens. Maybe I did something wrong? > > Result is displayed in the Transcript. Sorry to not have said it before. > We though first about opening a workspace with the result inside, but I did > not find an easy way to do it. So, for now, it prints in the Transcript. What about summarizing progress with the passes/failures/errors statistics after each run, and if one wants more details, then clicking on the statistics opens a workspace with the detailed list of fixed/broken tests ? -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Oct. 10, 2008

Re: [Pharo-project] problem with cursor

by David RÃ¶thlisberger

> Does anybody else experiencing the same. I'm using OB + packageBrowser + > for a moment I thought it would be related to the demo mode font > > When I click sometimes the cursor simply does not move to the point. Have you tried to execute Utilities cleanseOtherworldlySteppers ? This helped me when I had similar problems, eg. when I had to click twice to make something happen... David

Oct. 10, 2008

[Pharo-project] problem with cursor

by StÃ©phane Ducasse

I noticed that the cursor is quite slow at getting where I point. I often have to click two times so that it appears under my mouse. Does anybody else experiencing the same. I'm using OB + packageBrowser + for a moment I thought it would be related to the demo mode font When I click sometimes the cursor simply does not move to the point. Stef

Oct. 10, 2008

Re: [Pharo-project] History and SUnit

by StÃ©phane Ducasse

the idea adrian is that we store the tests with a packgae then when we load the package we can then compare if we made progress or not. For moose this is really nice beacuse I got far too muc h red tests at the beginning. On Oct 10, 2008, at 10:10 AM, Adrian Lienhard wrote: > Hi Alex, > > I tried your extension and have the following questions/problems: > - when I first run all the tests in the system, I get 4 failures (as > expected) but the bar on top stays green where it should be yellow > (it worked before) > - I don't understand the "Progress" feature. What I did is run the > tests, then "Store results", then I fixed a failing test, then "Run > Failures", then "Show progress". But nothing happens. Maybe I did > something wrong? > > Thanks, > Adrian > > On Oct 1, 2008, at 16:56 , Alexandre Bergel wrote: > >> Dear list, >> >> In PharoInbox Gwenael and I put an extension of SUnit that records >> results when running a set of test. >> Feel free to suggest improvement.... >> >> Open a TestRunner to enjoy its 'History' button. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 10, 2008

Re: [Pharo-project] Installer refactor

by StÃ©phane Ducasse

On Oct 10, 2008, at 10:27 AM, Matthew Fulmer wrote: > On Fri, Oct 10, 2008 at 07:31:23AM +0200, St?phane Ducasse wrote: >> Excellent! >> I will look at that. >> I never thought there were 14 classes :) >> >> You added aslo a factory? >> so that Installer squeaksource still work I imagine? > > But of course! it wouldn't be installer if the syntax changed. :) I will have to have a look at the code :) I plan to harvest some kernel extensions as soon as I have some time after the etoy cleanup. I would like to be able to get rid of PLF for loading MC1.6 or friend. > > It still runs LPF fine, which is the main thing > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 10, 2008

Re: [Pharo-project] About trait mop

by StÃ©phane Ducasse

> > > I had a look and I like it, so I'll try to make your tests pass ;). > > I don't agree with the following, though: > >> self assert: (D>>#c3) origin = D. "this is a question because it >> could be " > > here I think it should be Trait2, not D. The alias c3->c2 does not > redefine the method in the class; the method still originates in > Trait2. Not really :) we discussed a lot with marcus and I think that I have a point :) the point is that since Compiled Method are copied so c3 is really different from c2 and c3 is not defined in Trait2 but this is realy because there is D that C3 exists. so tell me what you think. Stef > > > So: (D>>#c3) origin = Trait2. > Just like: (D>>#c2) origin = Trait2. > > Adrian > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 10, 2008

Re: [Pharo-project] History and SUnit

by Alexandre Bergel

> I tried your extension and have the following questions/problems: > - when I first run all the tests in the system, I get 4 failures (as > expected) but the bar on top stays green where it should be yellow > (it worked before) that's strange. I run all the test, and it turns yellow saying: "10 October 2008 1:07:37 pm 2286 run, 2279 passes, 4 expected failures, 3 failures, 0 errors, 0 unexpected passes" > - I don't understand the "Progress" feature. What I did is run the > tests, then "Store results", then I fixed a failing test, then "Run > Failures", then "Show progress". But nothing happens. Maybe I did > something wrong? Result is displayed in the Transcript. Sorry to not have said it before. We though first about opening a workspace with the result inside, but I did not find an easy way to do it. So, for now, it prints in the Transcript. Cheers, Alexandre > > On Oct 1, 2008, at 16:56 , Alexandre Bergel wrote: > >> Dear list, >> >> In PharoInbox Gwenael and I put an extension of SUnit that records >> results when running a set of test. >> Feel free to suggest improvement.... >> >> Open a TestRunner to enjoy its 'History' button. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 10, 2008

Re: [Pharo-project] [ANN] 10091

by Adrian Lienhard

Thanks for the explanation, Nicolas! This sounds reasonable. This kind of conclusion was missing for me when I read through the different bug reports on Mantis. Adrian On Oct 9, 2008, at 22:18 , nicolas cellier wrote: > >> http://bugs.squeak.org/view.php?id=7180 +6455 +1603 +1602 > >> > >> Patches for Interval indexOf: and includes: > > > > I wonder about these fixes because of http://code.google.com/p/pharo/issues/detail?id=35 > > > > Did you reconsider the correctness of these fixes? They seem > > complicated and after reading through the bug reports again > > (especially http://bugs.squeak.org/view.php?id=7180) I concluded > > that they may introduce more problems than they fix. > I know I tried to find my way there too. > Now I trusted nicolas. > Nicolas are you strong on these fixes? > > Stef > > > > > > > Adrian > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project at lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > Thank you Stef. > Yes, the fix is safe. > I develop here after these 3 points > A)- The code was wrong > B)- Discussions were too long, but the fixes are very easy > C)- library could be enhanced > > Adrian, hope I will convince you (also, read the code). > > Cheers > > Nicolas > > > > > A) The code was wrong > > Prior this patch: > - #includes: implementation were WRONG. > - #indexOf: was missing, falling back to naive super slow > implementation > > Try these two tests in any Squeak image of your choice (3.7 to: 3.10): > > "There is no reason that the first is true while the second is false" > {(Float pi to: 4*Float pi by: Float pi) includes: Float pi*2 + > 1.0e-11. > (Float pi to: 4*Float pi by: Float pi) includes: Float pi*2 - > 1.0e-11}. > > "There is no reason for this timeToRun to grow" > (1 to: 7) collect: [:i | > [(1 to: 10000000) indexOf: (10 raisedTo: i)] timeToRun] > > > > B)- the fixes are very easy > > I simply implemented indexOf: with same algorithm as #includes: > (corrected!). > Then removed includes: because super includes: is implemented > sending indexOf: > Then I removed valueIncludes: because includes: was sole sender. > You see, two methods removed, one fix added: no revolution > > > > C)- library could be enhanced > > What I would prefer is: > - implement a method with an argument so that user can choose > comparison tolerance > - expand this fuzzy inclusion test to any other collection > Maybe something like: > includes: aNumber moreOrLess: aTolerance. > Then Interval includes: could eventually use a default tolerance. > But the obvious bugs must first be corrected... > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 10, 2008