- Pharo-dev - lists.pharo.org

about common command
by ducasse Oct. 6, 2019

Oct. 6, 2019

Hi I played a bit to turn smart suggestion actions into commander2 commands. It works :). Now with CM2 we do not have to have a class per command. We can create an instance. Now I was wondering what we prefer - using classes + we can dispatch later (for example suggestions dispatch on nodes message to register to specific AST node and the new behavior can be plugged modularly using extension + free registration - we create one class per command - using instances + no need to create one class. - we need to build a registration and query mechanism - extension will require to change or annotate somehow the created instances . So I have the impression that using classes is better. Setf

1 0

[Pharo 8.0] Build #836: Spec2-sync
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2019

Oct. 5, 2019

There is a new Pharo build available! The status of the build #836 was: SUCCESS. The Pull Request #4811 was integrated: "Spec2-sync" Pull request url: https://github.com/pharo-project/pharo/pull/4811 Issue Url: https://github.com/pharo-project/pharo/issues/Spec2 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #835: Move the #errorNotKeyed message from Collection to Bag
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2019

Oct. 5, 2019

There is a new Pharo build available! The status of the build #835 was: SUCCESS. The Pull Request #4835 was integrated: "Move the #errorNotKeyed message from Collection to Bag" Pull request url: https://github.com/pharo-project/pharo/pull/4835 Issue Url: https://github.com/pharo-project/pharo/issues/4808 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #834: 4833-Better-class-comment-for-RegexRefactorings
by ci-pharo-ci-jenkins2＠inria.fr Oct. 5, 2019

Oct. 5, 2019

There is a new Pharo build available! The status of the build #834 was: FAILURE. The Pull Request #4834 was integrated: "4833-Better-class-comment-for-RegexRefactorings" Pull request url: https://github.com/pharo-project/pharo/pull/4834 Issue Url: https://github.com/pharo-project/pharo/issues/4833 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

looking for the baselineoffuel
by ducasse Oct. 5, 2019

Oct. 5, 2019

Hi I would like to depend on fuel for a project and I cannot find the baselinein the image. Is there one somewhere and where can I find it. Tx

2 2

XmlSupport on GitHub?
by Tudor Girba Oct. 5, 2019

Oct. 5, 2019

Hi, Did anyone port XmlSupport to GitHub? Cheers, Tudor -- feenk.com âHow do you feenk today?"

5 4

BlockClosures - Equality and Things
by Sean P. DeNigris Oct. 5, 2019

Oct. 5, 2019

While developing Magritte, I have a problem because blocks that are read/written to/from strings (e.g. via Magritte forms) have a different outerContext before and after and thus I don't know how (without an ugly hack) to determine whether they were changed by the user. Question: Is there a smarter way to do block equality? Currently in Pharo block comparison is via #==. In Squeak, there is: BlockClosure >> #= aClosure self == aClosure ifTrue: [^true]. aClosure class = self class ifFalse: [^false]. (self method == aClosure method and: [startpc = aClosure startpc and: [self isClean]]) "<--- this line" ifTrue: [^true]. ^outerContext = aClosure outerContext and: [startpc = aClosure startpc] I'm not totally sold on the implementation due to the `startpc = aClosure startpc` the first time it appears (in the comment-marked line). With it, in a workspace, the following is false: `[1] = [1]`, but removing that test makes it true. I'd like something that returns true if both blocks are clean and they "do the same thing". But I like the track it's on... ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 1

[Pharo 8.0] Build #833: Compiler: Cache Vector Index
by ci-pharo-ci-jenkins2＠inria.fr Oct. 4, 2019

Oct. 4, 2019

There is a new Pharo build available! The status of the build #833 was: FAILURE. The Pull Request #4827 was integrated: "Compiler: Cache Vector Index" Pull request url: https://github.com/pharo-project/pharo/pull/4827 Issue Url: https://github.com/pharo-project/pharo/issues/CacheVectorIndex Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #832: Improve-slot-error-message
by ci-pharo-ci-jenkins2＠inria.fr Oct. 4, 2019

Oct. 4, 2019

There is a new Pharo build available! The status of the build #832 was: SUCCESS. The Pull Request #4826 was integrated: "Improve-slot-error-message" Pull request url: https://github.com/pharo-project/pharo/pull/4826 Issue Url: https://github.com/pharo-project/pharo/issues/Improve Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #831: Epicea browser: Do no remove filters on log selection change
by ci-pharo-ci-jenkins2＠inria.fr Oct. 4, 2019

Oct. 4, 2019

There is a new Pharo build available! The status of the build #831 was: SUCCESS. The Pull Request #4816 was integrated: "Epicea browser: Do no remove filters on log selection change" Pull request url: https://github.com/pharo-project/pharo/pull/4816 Issue Url: https://github.com/pharo-project/pharo/issues/4815 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0