- Pharo-users - lists.pharo.org

[ANN] Next Pharo Sprint: June 28

by Marcus Denker

We will organize a Pharo sprint / Moose dojo June 28, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

June 24, 2019

Re: [Pharo-users] Anything on Pharo that would be like Opentalk on VW?

by askoh

I had the same quest. See the thread http://forum.world.st/Smalltalk-to-Smalltalk-interface-td5099844.html#none Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 24, 2019

Re: [Pharo-users] Distribution of test method name length

by Kasper Osterbye

Quite interesting! I was wondering about the correlation to number of arguments due to the particularities of the keyword syntax which might give longer method names in the first place. Best, Kasper

June 24, 2019

Anything on Pharo that would be like Opentalk on VW?

by Jerry Kott

I am looking at some interprocess communication with Pharo. VW has Opentalk, VASt has Sst (I think, havenât looked in a while). Does anything similar exist for Pharo? Jerry Kott This message has been digitally signed. PGP Fingerprint: A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5

June 24, 2019

Re: [Pharo-users] Distribution of test method name length

by Ben Coman

On Mon, 24 Jun 2019 at 07:10, Jerry Kott <jkott(a)image-ware.com> wrote: > Interestingâ¦ > > I am curious about the purpose of this analysis (other than the > âinteresting-nessâ of it). Sure, some names read like sentences, but that > beats the âstrcpy()â, doesnât it? I love that in Smalltalk / Pharo, I donât > have to remember cryptic function names and can make the code optimally > verbose (if there is such a thing) to express intent. If that means a > method is rather long, so be it. > Its an offshoot of working on the Pharo Track of the Exercism project ( https://exercism.io/tracks/pharo-smalltalk) Here we generate test-method names from their canonical data "description" ( https://github.com/exercism/problem-specifications/blob/master/exercises/wo… ) The original intent of that field was to generate identifiers, but sometimes the language ends up a bit flowery and we ended up with method-name 150 character long. I am in the process of slimming these down. Someone queried me "what was a recommended identifier length" and I had no clue -- so I thought the Pharo code base would be a good source of data. Having produced the graph, I thought others might find it mildly interesting. Thats all. It may be worthwhile reviewing some of the outliers, but that was not its intent. It was shared just-for-interest. The purpose is certainly not to squeeze Pharo messages down to 6 characters ;) cheers -ben P.S. I found the graph more useful showing percentages rather than absolute count. 95% less than 50 characters 99% less than 60 characters [image: image.png]

June 24, 2019

Re: [Pharo-users] Distribution of test method name length

by Jerry Kott

Interestingâ¦ I am curious about the purpose of this analysis (other than the âinteresting-nessâ of it). Sure, some names read like sentences, but that beats the âstrcpy()â, doesnât it? I love that in Smalltalk / Pharo, I donât have to remember cryptic function names and can make the code optimally verbose (if there is such a thing) to express intent. If that means a method is rather long, so be it. Jerry Kott This message has been digitally signed. PGP Fingerprint: A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5 > On 21-06-2019, at 2:35 AM, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Fri, 21 Jun 2019 at 12:43, K K Subbu <kksubbu.ml(a)gmail.com <mailto:kksubbu.ml@gmail.com>> wrote: > Nice graph, Ben! The larger test names (selector size > 100) look more > like sentences than names ;-). > > On 21/06/19 6:50 AM, Ben Coman wrote: > > classes := Object allSubclasses select: [ :cc | cc isKindOf: > > TestCase class ]. > > methods := c flatCollect: [ :c | c allMethods ]. > > Ahh, yes. Blame evolution of the Playground code between when I used it and when I copied it here. > > > Did you mean "classes" flatCollect: here? > > > tests := methods select: [ :m | m selector beginsWith: 'test' ]. > > lengths := tests collect: [ :m | m selector size ]. > > select:thenCollect: can also be used here. > > yes. but I was checking each stage as it grew incrementally. > > > > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > > len; show: ','; show: count ] > > I find the in: selector very handy for quick commands without having to > use undefined temps. e.g. > ```` > (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: > [ :classes | > (classes flatCollect: [ :c | c allMethods ]) in: [ :methods | > (methods select: [ :m | m selector beginsWith: 'test' ] thenCollect: > [ :m | m selector size ]) in: [:lengths | > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > len; show: ','; show: count ]]]] > ```` > > cool > > cheers -ben

June 23, 2019

Re: [Pharo-users] Question: anyone using NOCompletion setting?

by Sean P. DeNigris

Marcus Denker-4 wrote > Removing the Ocompletion (for a while) would make it much easierâ¦ I can live without it for a while, especially if we can plug it back in at the end! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

June 21, 2019

Re: [Pharo-users] Distribution of test method name length

by Ben Coman

On Fri, 21 Jun 2019 at 12:43, K K Subbu <kksubbu.ml(a)gmail.com> wrote: > Nice graph, Ben! The larger test names (selector size > 100) look more > like sentences than names ;-). > > On 21/06/19 6:50 AM, Ben Coman wrote: > > classes := Object allSubclasses select: [ :cc | cc isKindOf: > > TestCase class ]. > > methods := c flatCollect: [ :c | c allMethods ]. > Ahh, yes. Blame evolution of the Playground code between when I used it and when I copied it here. > Did you mean "classes" flatCollect: here? > > > tests := methods select: [ :m | m selector beginsWith: 'test' ]. > > lengths := tests collect: [ :m | m selector size ]. > > select:thenCollect: can also be used here. > yes. but I was checking each stage as it grew incrementally. > > > lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > > len; show: ','; show: count ] > > I find the in: selector very handy for quick commands without having to > use undefined temps. e.g. > ```` > (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: > [ :classes | > (classes flatCollect: [ :c | c allMethods ]) in: [ > :methods | > (methods select: [ :m | m selector beginsWith: > 'test' ] thenCollect: > [ :m | m selector size ]) in: [:lengths | > lengths asBag keysAndValuesDo: [ :len > :count | Transcript crShow: > len; show: ','; show: count ]]]] > ```` > cool cheers -ben

June 21, 2019

Re: [Pharo-users] Distribution of test method name length

by K K Subbu

Nice graph, Ben! The larger test names (selector size > 100) look more like sentences than names ;-). On 21/06/19 6:50 AM, Ben Coman wrote: > Â Â classes := Object allSubclasses select: [ :cc | cc isKindOf: > TestCase class ]. > Â Â methods := c flatCollect: [ :c | c allMethods Â ]. Did you mean classes flatCollect: here? > Â Â tests := methods select: [ :m | m selector beginsWith: 'test' ]. > Â Â lengths := tests collect: [ :m | m selector size ]. select:thenCollect: can also be used here. > Â Â lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: > len; show: ','; show: count Â ] I find the in: selector very handy for quick commands without having to use undefined temps. e.g. ```` (Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]) in: [ :classes | (classes flatCollect: [ :c | c allMethods ]) in: [ :methods | (methods select: [ :m | m selector beginsWith: 'test' ] thenCollect: [ :m | m selector size ]) in: [:lengths | lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: len; show: ','; show: count ]]]] ```` Regards .. Subbu

June 21, 2019

Distribution of test method name length

by Ben Coman

Working on the Exercism project to shorten generated test method names, for comparison I reviewed the length of test method names in Pharo 7. So just for curiousity value, here is that graph (done in Excel)... [image: image.png] Data generated by... classes := Object allSubclasses select: [ :cc | cc isKindOf: TestCase class ]. methods := c flatCollect: [ :c | c allMethods ]. tests := methods select: [ :m | m selector beginsWith: 'test' ]. lengths := tests collect: [ :m | m selector size ]. lengths asBag keysAndValuesDo: [ :len :count | Transcript crShow: len; show: ','; show: count ] cheers -ben

June 21, 2019