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

[Pharo 8.0] Build #1108: Fix OSWindowWorldMorph new open and family

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

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…

Jan. 16, 2020

[Pharo 9.0] Build #8: Small cleanups in Debugger-Tests package

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

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…

Jan. 16, 2020

[Pharo 8.0] Build #1107: 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 #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…

Jan. 15, 2020

[Pharo 9.0] Build #7: Improve comments of renraku

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

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…

Jan. 15, 2020

Re: [Pharo-dev] Negative number syntax

by Sven Van Caekenberghe

For the record, should we want to remove the option of having a (possible second) minus sign after the radix specification, the expression self peekSignIsMinus ifTrue: [ neg := neg not ]. should be removed from NumberParser>>#nextNumber and #nextInteger But I haven't tested this. Some unit tests might fail since this 'feature' seems to be supported explicitly. > On 15 Jan 2020, at 17:38, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 15 Jan 2020, at 14:30, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> 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 would not support this one either >> >> 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 ? > > I would not > >> >> Sven

Jan. 15, 2020

Re: [Pharo-dev] Negative number syntax

by ducasse

> On 15 Jan 2020, at 14:30, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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 would not support this one either > > 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 ? I would not > > Sven > >

Jan. 15, 2020

Re: [Pharo-dev] Characterizing Pharo Code: A Technical Report

by Oleks

Hello Tudor, In the end of the report, we have provided links to the repositories with all our code. The analysis itself was done using Jupyter Notebooks, they are in the first repository. However, I'm afraid that we forgot to make that repository public. We will do it ASAP. As for the "naturalness" of Pharo code, I can only offer you my Master thesis: http://er.ucu.edu.ua/handle/1/1338 (but I think that you already saw it) If you want to discuss "naturalness", let me know, because I have many thoughts on this topic. Oleks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 15, 2020

Re: [Pharo-dev] Characterizing Pharo Code: A Technical Report

by Tudor Girba

Very nice work! Is this report available in an executable form? Iâd also be interested in an analysis of ânaturalnessâ of Pharo code. Did you, by any chance, also perform that one? Cheers, Doru > On Jan 15, 2020, at 12:02 PM, Oleksandr Zaytsev <olk.zaytsev(a)gmail.com> wrote: > > 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 -- feenk.com "From an abstract enough point of view, any two things are similar."

Jan. 15, 2020

Smalltalk meetup in Palo Alto, CA on January 25, 2020

by Alexandre Bergel

Dear Friends and Colleagues, We are organizing a Smalltalk meetup in Palo Alto, CA, on Saturday 25 January, 2020. The event is free, thanks to Lam Research, Object Profile, Semantics for sponsoring the event. More information may be found on https://agileartificialintelligence.github.io/meetup.html People who wish to attend, then the webpage contains the registration links. Please, join! Kind regards, Alexandre & Juan Pablo -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 15, 2020

Negative number syntax

by Sven Van Caekenberghe

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

Jan. 15, 2020