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

[Pharo 9.0] Build #10: ClassVariable>>#asRingMinimalDefinitionIn: should use Smalltalk globals

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #10 was: SUCCESS. The Pull Request #5523 was integrated: "ClassVariable>>#asRingMinimalDefinitionIn: should use Smalltalk globals" Pull request url: https://github.com/pharo-project/pharo/pull/5523 Issue Url: https://github.com/pharo-project/pharo/issues/5522 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 17, 2020

[Pharo 8.0] Build #1113: Removed forgotten halts in SettingsBrowser

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1113 was: FAILURE. The Pull Request #5520 was integrated: "Removed forgotten halts in SettingsBrowser" Pull request url: https://github.com/pharo-project/pharo/pull/5520 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2020

About RBProgramNodeVisitor >> visitMethodNode: aMethodNode

by StÃ©phane Ducasse

While I can understand that RBProgramNodeVisitor >> visitMethodNode: aMethodNode does not return a value. - because visiting a program does not mean automatically to interpret it. RBProgramNodeVisitor >> visitMethodNode: aMethodNode self visitArgumentNodes: aMethodNode arguments. aMethodNode pragmas do: [ :each | self visitNode: each ]. self visitNode: aMethodNode body I was wondering if we could have visitBody RBProgramNodeVisitor >> visitMethodNode: aMethodNode self visitArgumentNodes: aMethodNode arguments. aMethodNode pragmas do: [ :each | self visitNode: each ]. self visitBody: aMethodNode RBProgramNodeVisitor >> visitBody: aMethodNode self visitNode: aMethodNode body So that subclasses can simply override it instead of being forced to override visitMethodNode: ? https://github.com/pharo-project/pharo/issues/5521 S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Jan. 16, 2020

[Pharo 8.0] Build #1112: Fixing Enlumineur tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1112 was: FAILURE. The Pull Request #5517 was integrated: "Fixing Enlumineur tests" Pull request url: https://github.com/pharo-project/pharo/pull/5517 Issue Url: https://github.com/pharo-project/pharo/issues/fixing Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2020

[Pharo 8.0] Build #1111: Revert "switch theme to white (Pharo 8.0 is a white themed release)"

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1111 was: SUCCESS. The Pull Request #5516 was integrated: "Revert "switch theme to white (Pharo 8.0 is a white themed release)"" Pull request url: https://github.com/pharo-project/pharo/pull/5516 Issue Url: https://github.com/pharo-project/pharo/issues/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2020

Re: [Pharo-dev] [Pharo-users] Pharo Quality Rules for Beginners

by StÃ©phane Ducasse

> On 16 Jan 2020, at 14:18, Ben Coman <btc(a)openinworld.com> wrote: > > On Wed, 15 Jan 2020 at 17:41, ESTEBAN VILLALOBOS DIAZ via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: >> >> Hello everyone! >> >> My name is Esteban and I will be working on the Pharo Quality Rules for the next few months. The goal is to create different profiles for the rules according to the programming experience of the user. For example, for the beginner profile we would like to check for common mistakes made by people who are just starting with Pharo like: >> >> Sending self as a message (probably because they forgot a . ) >> Using False instead of false >> etc.. >> >> I would appreciate it if you could share with me other common mistakes that you have seen beginners do, or maybe tell me a bit of your own experience when you started using Pharo :) > > - Getting confused between instance-side and class-side, mixing up > which side methods are on. > When getting a DNU maybe check if that message is known on the class-side. > > - leaving out the end of statement trailing dot. > An error message like "Blah doesn't understand self" is a bit complex > for a beginner to decipher. Yes this one is on our list :) > > cheers -ben > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Jan. 16, 2020

Re: [Pharo-dev] [Pharo-users] Pharo Quality Rules for Beginners

by Ben Coman

On Wed, 15 Jan 2020 at 17:41, ESTEBAN VILLALOBOS DIAZ via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello everyone! > > My name is Esteban and I will be working on the Pharo Quality Rules for the next few months. The goal is to create different profiles for the rules according to the programming experience of the user. For example, for the beginner profile we would like to check for common mistakes made by people who are just starting with Pharo like: > > Sending self as a message (probably because they forgot a . ) > Using False instead of false > etc.. > > I would appreciate it if you could share with me other common mistakes that you have seen beginners do, or maybe tell me a bit of your own experience when you started using Pharo :) - Getting confused between instance-side and class-side, mixing up which side methods are on. When getting a DNU maybe check if that message is known on the class-side. - leaving out the end of statement trailing dot. An error message like "Blah doesn't understand self" is a bit complex for a beginner to decipher. cheers -ben

Jan. 16, 2020

[Pharo 8.0] Build #1110: #5428 resync enlumineur

by ci-pharo-ci-jenkins2＠inria.fr

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

Jan. 16, 2020

[Pharo 8.0] Build #1109: 5434-Default-values-in-settings-should-not-be-stored

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1109 was: FAILURE. The Pull Request #5473 was integrated: "5434-Default-values-in-settings-should-not-be-stored" Pull request url: https://github.com/pharo-project/pharo/pull/5473 Issue Url: https://github.com/pharo-project/pharo/issues/5434 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2020

[Pharo 9.0] Build #9: Categorize uncategorizes classes in ClassAnnotation-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #9 was: SUCCESS. The Pull Request #5504 was integrated: "Categorize uncategorizes classes in ClassAnnotation-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/5504 Issue Url: https://github.com/pharo-project/pharo/issues/5503 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 16, 2020