- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] Pharo Quality Rules for Beginners
by Ben Coman Jan. 16, 2020

Jan. 16, 2020

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

2 1

[Pharo 8.0] Build #1110: #5428 resync enlumineur
by ci-pharo-ci-jenkins2＠inria.fr Jan. 16, 2020

Jan. 16, 2020

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…

1 0

[Pharo 8.0] Build #1109: 5434-Default-values-in-settings-should-not-be-stored
by ci-pharo-ci-jenkins2＠inria.fr Jan. 16, 2020

Jan. 16, 2020

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…

1 0

[Pharo 9.0] Build #9: Categorize uncategorizes classes in ClassAnnotation-Tests
by ci-pharo-ci-jenkins2＠inria.fr Jan. 16, 2020

Jan. 16, 2020

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…

1 0

[Pharo 8.0] Build #1108: Fix OSWindowWorldMorph new open and family
by ci-pharo-ci-jenkins2＠inria.fr Jan. 16, 2020

Jan. 16, 2020

There is a new Pharo build available! The status of the build #1108 was: SUCCESS. The Pull Request #5509 was integrated: "Fix OSWindowWorldMorph new open and family" Pull request url: https://github.com/pharo-project/pharo/pull/5509 Issue Url: https://github.com/pharo-project/pharo/issues/5507 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #8: Small cleanups in Debugger-Tests package
by ci-pharo-ci-jenkins2＠inria.fr Jan. 16, 2020

Jan. 16, 2020

There is a new Pharo build available! The status of the build #8 was: FAILURE. The Pull Request #5506 was integrated: "Small cleanups in Debugger-Tests package" Pull request url: https://github.com/pharo-project/pharo/pull/5506 Issue Url: https://github.com/pharo-project/pharo/issues/5505 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1107: switch theme to white (Pharo 8.0 is a white themed release)
by ci-pharo-ci-jenkins2＠inria.fr Jan. 15, 2020

Jan. 15, 2020

There is a new Pharo build available! The status of the build #1107 was: FAILURE. The Pull Request #5487 was integrated: "switch theme to white (Pharo 8.0 is a white themed release)" Pull request url: https://github.com/pharo-project/pharo/pull/5487 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…

1 0

[Pharo 9.0] Build #7: Improve comments of renraku
by ci-pharo-ci-jenkins2＠inria.fr Jan. 15, 2020

Jan. 15, 2020

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

1 0

Negative number syntax
by Sven Van Caekenberghe Jan. 15, 2020

Jan. 15, 2020

Hi, I came across the following quirk that surprised me. Positive number in a arbitrary radix 16rA = 10 Same number but negative -16rA = -10 I guess, we all know that. However, the following is also possible 16r-A = -10 I did not know that, but OK. But what about this one ? -16r-A = 10 I understand that the double negation is positive again, but do we really want to support such a syntax ? Sven

2 2

Characterizing Pharo Code: A Technical Report
by Oleksandr Zaytsev Jan. 15, 2020

Jan. 15, 2020

Hello, We have analyzed the source code of the 50 projects selected from the Pharo ecosystem and reported our findings in this document: https://hal.inria.fr/hal-02440055v1 Perhaps, you will find it interesting. Here are some fun facts that we have discovered: - 25% of classes have no more than 3 methods in them, and 50% of classes have no more than 6 methods - The average number of lines of code in Pharo methods is 5.8, the median of this number is 3, meaning that 50% of methods have no more than 3 lines. - About a quarter of source code are message sends (method names) - they take 27.3% of source code tokens and 26.3% of characters. - On a character level, 22.5% of source code are string literals, and 19.4% are literal arrays. Together literals take 44% of characters in source code, but only 7.1% of tokens. - Positive statements are much more common than negative ones. ifTrue: is used 3 times more often than ifFalse:. Similarly, ifTrue:ifFalse: is 26 times more common than ifFalse:ifTrue:. - After tokenizing the code of 151,717 methods, splitting identifier names by camel case, and removing non-alphabetic characters, we received a sequence of almost 3 million words (e.g. ... ordered collection with all command line arguments...). This sequence contains only 8,211 unique words (including all misspellings such as arrray, clipped words such as arr, and nonsense words such as ddd or xdkh). Compare this to over 40,000 unique words used in roughly the same amount of printed English prose. - At least 5,480 of those 8,211 unique alphabetic sequences are valid English words. Have a nice day, and let us know what you think. We would be happy to receive your feedback. Oleks

3 2