January 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Collection extensions

by Alexandre Bergel

I vote to get these methods in. Alexandre On 5 Jan 2009, at 10:30, StÃ©phane Ducasse wrote: > Hi all > > I published to the inbox some cool collection extension methods that > we use all the time in Moose. > flatCollect:, collectAsSet:, and groupedBy: > > http://code.google.com/p/pharo/issues/detail?id=432&colspec=ID%20Type%20Sta… > I would like to have your feedback because we found them really useful > in practice. > > Here are some examples: > > testFlatCollectArray > "self debug: #testFlatCollectArray" > > self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each ]) = #(1 2 3 > 4 5 3)). > self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each]) = #(1 2 2 > 3 1 3 4)). > > self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each| Set with: > each]) > = #(#(1 2) #(2 3) #(1 3 4))). > > > testFlatCollectSet > "self debug: #testFlatCollectSet" > > self assert: ((#((1 2) (1 2) (1 3 4)) asSet flatCollect: [:each]) = > #(1 1 2 3 4) asSet). > self assert: ((#() asSet flatCollect: [:each]) = #() asSet). > > self assert: ((#((1 2) () (1 3 4)) asSet flatCollect: [:each]) = > #(1 1 2 3 4) asSet). > self assert: ((#((1 2) #((99)) (1 3 4)) asSet flatCollect: [:each]) > = #(1 1 2 3 4 (99)) asSet). > self assert: ((#((1 2) #(()) (1 3 4)) asSet flatCollect: [:each]) > = #(1 1 2 3 4 ()) asSet). > > > testGroupedByArray > "self debug: #testGroupedByArray" > > | res | > res := #(1 2 3 4 5) groupedBy: [:each | each odd]. > self assert: (res at: true) = #(1 3 5). > self assert: (res at: false) = #(2 4) > > > testGroupedBy > "self debug: #testGroupedBy" > > | res | > res := #(1 2 3 4 5) asOrderedCollection > groupedBy: [:each | each odd]. > self assert: (res at: true) = #(1 3 5) asOrderedCollection. > self assert: (res at: false) = #(2 4) asOrderedCollection > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by StÃ©phane Ducasse

alex it seems that your package is empty. can you check. Stef On Jan 5, 2009, at 1:14 PM, Alexandre Bergel wrote: > New tests on DictionaryTest. The method categories accesssing, adding, > comparing, enumerating, printing, removing, and testing are covered. > This represents a coreverage of 66% > > In PharoInbox. I am continuing the coverage... > > 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 >

Jan. 5, 2009

[Pharo-project] Collection extensions

by StÃ©phane Ducasse

Hi all I published to the inbox some cool collection extension methods that we use all the time in Moose. flatCollect:, collectAsSet:, and groupedBy: http://code.google.com/p/pharo/issues/detail?id=432&colspec=ID%20Type%20Sta… I would like to have your feedback because we found them really useful in practice. Here are some examples: testFlatCollectArray "self debug: #testFlatCollectArray" self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each ]) = #(1 2 3 4 5 3)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each]) = #(1 2 2 3 1 3 4)). self assert: ((#((1 2) (2 3) (1 3 4)) flatCollect: [:each| Set with: each]) = #(#(1 2) #(2 3) #(1 3 4))). testFlatCollectSet "self debug: #testFlatCollectSet" self assert: ((#((1 2) (1 2) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#() asSet flatCollect: [:each]) = #() asSet). self assert: ((#((1 2) () (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4) asSet). self assert: ((#((1 2) #((99)) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 (99)) asSet). self assert: ((#((1 2) #(()) (1 3 4)) asSet flatCollect: [:each]) = #(1 1 2 3 4 ()) asSet). testGroupedByArray "self debug: #testGroupedByArray" | res | res := #(1 2 3 4 5) groupedBy: [:each | each odd]. self assert: (res at: true) = #(1 3 5). self assert: (res at: false) = #(2 4) testGroupedBy "self debug: #testGroupedBy" | res | res := #(1 2 3 4 5) asOrderedCollection groupedBy: [:each | each odd]. self assert: (res at: true) = #(1 3 5) asOrderedCollection. self assert: (res at: false) = #(2 4) asOrderedCollection

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by StÃ©phane Ducasse

Cool I will harvest that soon. On Jan 5, 2009, at 1:14 PM, Alexandre Bergel wrote: > New tests on DictionaryTest. The method categories accesssing, adding, > comparing, enumerating, printing, removing, and testing are covered. > This represents a coreverage of 66% > > In PharoInbox. I am continuing the coverage... > > 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 >

Jan. 5, 2009

[Pharo-project] #traits

by StÃ©phane Ducasse

Hi adrian I wanted to know if we could not have traits defined in Behavior and whose behavior would be self traitComposition allTraits BTW will you have some time to look at my improvements? Stef

Jan. 5, 2009

Re: [Pharo-project] Underscores question

by Gwenael Casaccio

On Sunday 04 January 2009 17:41:21 Bill Schwab wrote: > Gwenael, > > Stef mentioned that you are working on a parser, in part to address > problems with $_. At the risk of appearing impatient, do your goals > include allowing the use of $_ in selector and class names? If so, is > it something simple that could appear soon, or is it involved and likely > to take a while? I have some external interfacing requirements that > would be simplified if $_ were unconstrained. > Hi Bill, You can put _ in selector and class names. There is only a problem with _ when it is used instead of :=. Cheers, Gwenael > Bill > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 5, 2009

[Pharo-project] DictionaryTest

by Alexandre Bergel

New tests on DictionaryTest. The method categories accesssing, adding, comparing, enumerating, printing, removing, and testing are covered. This represents a coreverage of 66% In PharoInbox. I am continuing the coverage... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009

Re: [Pharo-project] [Fwd: [ANN] Number comparison, hash, NaN, Point, and other partially ordered sets]

by StÃ©phane Ducasse

Nicolas could you summarize your solution? Stef On Jan 5, 2009, at 12:55 AM, nicolas cellier wrote: > > > -------- Message original -------- > From: - Mon Jan 05 00:49:18 2009 > X-Mozilla-Status: 0001 > X-Mozilla-Status2: 00800000 > X-Mozilla-Keys: > Date: Mon, 05 Jan 2009 00:49:17 +0100 > From: nicolas cellier <ncellier(a)ifrance.com> > User-Agent: Thunderbird 2.0.0.12 (X11/20080306) > MIME-Version: 1.0 > Newsgroups: gmane.comp.lang.smalltalk.squeak.general > Subject: [ANN] Number comparison, hash, NaN, Point, and other > partially > ordered sets > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > Content-Transfer-Encoding: 7bit > > > > Happy new year everyone. > After VWNC recent discussion about comparing Point and Number, I tried > to make a review of my previous work concerning all these minor (but > annoying) comparison bugs. > > > I think I now have an acceptable and consistent solution. > This is spreaded across several mantis bug reports: > > http://bugs.squeak.org/view.php?id=3374 > http://bugs.squeak.org/view.php?id=6719 > http://bugs.squeak.org/view.php?id=7259 > http://bugs.squeak.org/view.php?id=7260 > > It should also solve: > > > http://bugs.squeak.org/view.php?id=3360 > http://bugs.squeak.org/view.php?id=6601 > (I took andrew solution from the last one) > > Comments, code critics, flames, etc... are welcome > > Nicolas > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 5, 2009

[Pharo-project] [Fwd: [ANN] Number comparison, hash, NaN, Point, and other partially ordered sets]

by nicolas cellier

-------- Message original -------- From: - Mon Jan 05 00:49:18 2009 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00800000 X-Mozilla-Keys: Date: Mon, 05 Jan 2009 00:49:17 +0100 From: nicolas cellier <ncellier(a)ifrance.com> User-Agent: Thunderbird 2.0.0.12 (X11/20080306) MIME-Version: 1.0 Newsgroups: gmane.comp.lang.smalltalk.squeak.general Subject: [ANN] Number comparison, hash, NaN, Point, and other partially ordered sets Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Happy new year everyone. After VWNC recent discussion about comparing Point and Number, I tried to make a review of my previous work concerning all these minor (but annoying) comparison bugs. I think I now have an acceptable and consistent solution. This is spreaded across several mantis bug reports: http://bugs.squeak.org/view.php?id=3374 http://bugs.squeak.org/view.php?id=6719 http://bugs.squeak.org/view.php?id=7259 http://bugs.squeak.org/view.php?id=7260 It should also solve: http://bugs.squeak.org/view.php?id=3360 http://bugs.squeak.org/view.php?id=6601 (I took andrew solution from the last one) Comments, code critics, flames, etc... are welcome Nicolas

Jan. 4, 2009

[Pharo-project] Underscores question

by Bill Schwab

Gwenael, Stef mentioned that you are working on a parser, in part to address problems with $_. At the risk of appearing impatient, do your goals include allowing the use of $_ in selector and class names? If so, is it something simple that could appear soon, or is it involved and likely to take a while? I have some external interfacing requirements that would be simplified if $_ were unconstrained. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

Jan. 4, 2009