- Pharo-dev - lists.pharo.org

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 9, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 9, 2013

[Pharo-project] [update 3.0] #30115

by Marcus Denker

30115 ----- 10577 deprecate all decompiler API but #decompileMethod: https://pharo.fogbugz.com/f/cases/10577 10581 MenuMorph hardcode bounds instead of using defaultBounds https://pharo.fogbugz.com/f/cases/10581 10579 Small cleanup DebugContext https://pharo.fogbugz.com/f/cases/10579 10574 remove class side methods VirtualMachine https://pharo.fogbugz.com/f/cases/10574 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-MarcusDenker.1426.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/DebuggerModel-MarcusDenker.31… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.445.diff

May 9, 2013

[Pharo-project] Gofer push logic looks wrong

by StÃ©phane Ducasse

I'm copy Pharo1.0 from Squeaksource to smalltalkhub and for some packages I got error because I do not really know why Transcript does not understand classSide. It looks to be in the MCStWriter. Now I do not get why MCStWriter would have to be called to push a package from my local disc to smalltalkhub. It looks to me fundamentally wrong. May be this is the definition of Gofer of push that is bogus for what I'm doing. May be this is not storing a version but copying a file that I should do. |go repo|repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo10' user: 'StephaneDucasse' password: 'sn00py_papa'. go := Gofer new. go repository: repo. (((FileSystem disk workingDirectory / 'package-cache') allFiles select: [:each |'*.mcz' match: each basename]) groupedBy: [:each | (each base copyUpToLast: $-) ]) keys do: [:name | go package: name; push. ]

May 9, 2013

[Pharo-project] Fwd: [vwnc] Reducers in Smalltalk

by StÃ©phane Ducasse

look interesting Begin forwarded message: > From: Steffen MÃ¤rcker <merkste(a)web.de> > Subject: [vwnc] Reducers in Smalltalk > Date: May 9, 2013 4:40:15 PM GMT+02:00 > To: vwnc <vwnc(a)cs.uiuc.edu> > > Hi, > > out of curiosity I did an initial port of Clojure's Reducers library. I've just pushed it to the public repository. It is by no means complete or optimized. In fact, I ask you for your impressions and ideas where to go from here. > > So, what's in here? > Reducers builds upon the simple abstraction that a collection is a reducible object, i.e., an object that understands #reduce:init:. It provides fundamental collection operations similar to classical methods, e.g., like #collect:, but offers specific advantages: > - Reducers are composable and reusable. > - Memory efficiency, since no intermediate collections are constructed. > - Enable collection operations on custom types simply by implementing #reduce:init:. > - Possibility of parallel operations on collections, e.g., with Polycephaly 2. > > For example, the sum of odd numbers could be computed like this: > > | col red | > col := (1 to: 10**6). > (Reducer filter: #odd from: col) reduce: #+ init: 0. > > "composition of reducers works like this:" > red := (Reducer filter: #odd) <> (Reducer map: #squared). > (red from: col) reduce: #+ init: 0. > > Some questions: > 1. What do you think of the current API? > 2. How could one improve the execution time? (Optimizations to the construction of the (nested) blocks?) > > Have fun! > Steffen > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

May 9, 2013

[Pharo-project] ci.pharo.org forward working again

by Marcus Denker

The ci.pharo.org forward working again: http://ci.pharo.org Marcus

May 9, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 9, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 9, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. Zinc.Tests.ZnClientTests.testRedirect

May 9, 2013

[Pharo-project] [update 3.0] #30114

by Marcus Denker

May 9, 2013