April 2020 - Pharo-users - lists.pharo.org

[ANN] Willow v13.0.0 [v13.0.0] released!

by Buenos Aires Smalltalk

April 30, 2020

Package Browser (AKA 6-paned Browser) and Pharo package organization

by stephen＠heaveneverywhere.com

Hello friends, Iâm getting started with Pharo after decades using VisualWorks and Squeak; itâs pretty wonderful what you all have assembled! My question is related to what we used to teach as the first law of software reuse: âYou canât reuse it if you canât find it,â and the related software engineering "principle of least astonishment." When I fire up Pharo, the system browser presents me with a list of several hundred categories (from AST to Zodiac) in a system with over 8000 classes. The system categorization makes no sense since I donât know the naming conventions and so many packages have cute but quite non-descriptive names (Zinc? Metacello? Calypso?). In Smalltalk-80, the class category names were organized as a 2-level hierarchy where the top-level were items such as Magnitudes, Collections, Streams, Graphics, Text, System, Tools, Files, etc. This made it easy to find (e.g.,) the browser source code by looking in the Tools package for the class category Tools-Browser. Even packages with cute names (like my own âSirenâ), were categorized for ease of finding; e.g., the Siren classes were in class categories like Music-Events and Music-Magnitudes. Parsing the class category names on the first instance of $- made it possible to build 6-paned Browsers (called package pane browser in Squeak). (We acknowledged that this violates the âzero/one/infinity" rule.) Is something like this available for Pharo? I looked through the Calypso browser code and itâs so over-engineered (IMHO) that itâd take me several days to figure out how to implement this (it was about 1.5 pages of code in Smalltalk-80). If Pharo had a browser that scaled better and a reorganization/simplification of the class categories to use names that were more self-explanatory, it would be *much* easier for new users (in fact, for all users) to find their way around. I apologize for the stepping on toes... Stephen Pope -- Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com <http://heaveneverywhere.com/> http://FASTLabInc.com <http://fastlabinc.com/> https://vimeo.com/user19434036/videos <https://vimeo.com/user19434036/videos> http://heaveneverywhere.com/Reflections --

April 30, 2020

Re: [Pharo-users] mentor question 4

by Roelof Wobben

April 30, 2020

Re: [Pharo-users] mentor question 4

by Richard Sargent

See below. On Thu, Apr 30, 2020 at 10:58 AM Roelof Wobben via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > and also not with this one : > > cardNumber := '4539 1488 0343 6467'. > oddSum := 0. > evenSum := 0. > nextIsOdd := false. > cardNumber reverseDo: [:digit | > digit = Character space ifFalse: [ > nextIsOdd > ifFalse: [oddSum := oddSum + (digit asString asInteger ) ] > ifTrue: [(((digit asString asInteger) * 2) > 9) > ifTrue: [evenSum := evenSum + ((digit asString asInteger) * 2) - 9 ] > ifFalse: [ evenSum := evenSum + (digit asString asInteger) * 2 ]]. > nextIsOdd := nextIsOdd not]]. > ^ evenSum > > > > > Op 30-4-2020 om 18:30 schreef Roelof Wobben: > > Op 30-4-2020 om 16:16 schreef Roelof Wobben: > >> nextIsOdd := true. > >> aString reverseDo: [:digit | > >> digit = Character space ifFalse: [ > >> nextIsOdd > >> ifTrue: [oddSum := ...] > >> ifFalse: [evenSum := ...]. > >> nextIsOdd := nextIsOdd not]]. > > > > hmm, > > > > Still no luck with this code : > > > > cardNumber := '4539 1488 0343 6467'. > > oddSum := 0. > > evenSum := 0. > > nextIsOdd := true. > > cardNumber reverseDo: [:digit | > > digit = Character space ifFalse: [ > > nextIsOdd > > ifTrue: [oddSum := oddSum + digit asInteger ] > > ifFalse: [evenSum := ((digit asInteger * 2) > 9) > > ifTrue: [evenSum + ((digit asInteger * 2) - 9) ] > > ifFalse: [ evenSum + (digit asInteger * 2) ]]. > > nextIsOdd := nextIsOdd not]]. > > ^ oddSum + evenSum > With the one change to use #digitValue instead of #asInteger (which answers the code point), the above example works. | evenSum oddSum | cardNumber := '4539 1488 0343 6467'. oddSum := evenSum := 0. nextIsOdd := true. cardNumber reverseDo: [:digit | digit = Character space ifFalse: [ nextIsOdd ifTrue: [oddSum := oddSum + digit digitValue ] ifFalse: [evenSum := ((digit digitValue * 2) > 9) ifTrue: [evenSum + ((digit digitValue * 2) - 9) ] ifFalse: [ evenSum + (digit digitValue * 2) ]]. nextIsOdd := nextIsOdd not]]. ^ oddSum + evenSum gives me 80 for the answer. A few (mostly) minor points: - I don't see why "reverse" is necessary. Of course if you use #do:, nextIsOdd needs to start with true. - repeating the "digit digitValue" or other variations adds clutter and reduces clarity - ((digit digitValue * 2) - 9) is not unreasonable, but could be simplified. What is the largest integer X such that 2xX<=9? > > > the answer schould be 57 where I get 1157 > > > > So some debugging to do > > > > >

April 30, 2020

Re: [Pharo-users] mentor question 4

by Roelof Wobben

and also not with this one : cardNumber := '4539 1488 0343 6467'. oddSum := 0. evenSum := 0. nextIsOdd := false. Â Â Â Â cardNumber reverseDo: [:digit | Â Â Â Â Â Â Â Â digit = Character space ifFalse: [ Â Â Â Â Â Â Â Â nextIsOdd Â Â Â Â Â Â Â Â Â Â Â Â ifFalse:Â [oddSum := oddSum + (digit asString asInteger ) ] Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [(((digit asString asInteger) * 2) > 9) Â Â Â ifTrue: [evenSum := evenSum + ((digit asString asInteger)Â * 2) - 9 ] Â Â Â ifFalse: [ evenSum := evenSum + (digit asString asInteger)Â * 2 ]]. Â Â Â Â Â Â Â Â Â Â Â nextIsOdd := nextIsOdd not]]. ^ evenSum Op 30-4-2020 om 18:30 schreef Roelof Wobben: > Op 30-4-2020 om 16:16 schreef Roelof Wobben: >> nextIsOdd := true. >> Â Â Â Â aString reverseDo: [:digit | >> Â Â Â Â Â Â Â Â digit = Character space ifFalse: [ >> Â Â Â Â Â Â Â Â nextIsOdd >> Â Â Â Â Â Â Â Â Â Â Â Â ifTrue:Â [oddSum := ...] >> Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [evenSum := ...]. >> Â Â Â Â Â Â Â Â nextIsOdd := nextIsOdd not]]. > > hmm, > > Still no luck with this code : > > cardNumber := '4539 1488 0343 6467'. > oddSum := 0. > evenSum := 0. > nextIsOdd := true. > Â Â Â Â cardNumber reverseDo: [:digit | > Â Â Â Â Â Â Â Â digit = Character space ifFalse: [ > Â Â Â Â Â Â Â Â nextIsOdd > Â Â Â Â Â Â Â Â Â Â Â Â ifTrue:Â [oddSum := oddSum + digit asInteger ] > Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [evenSum := ((digit asInteger * 2) > 9) > Â Â Â ifTrue: [evenSum + ((digit asInteger * 2) - 9) ] > Â Â Â ifFalse: [ evenSum + (digit asInteger * 2) ]]. > Â Â Â Â Â Â Â Â Â Â nextIsOdd := nextIsOdd not]]. > ^ oddSum + evenSum > > the answer schould be 57 where I get 1157 > > So some debugging to do >

April 30, 2020

Re: [Pharo-users] NeoCSV - how to parse a string with unescaped quoted string inside it?

by Sven Van Caekenberghe

Hi Paul, Quotes inside quoted fields must be doubled. See #readQuotedField and #readEndOfQuotedField specifically. See also #testEmbeddedQuotes This is according to https://en.wikipedia.org/wiki/Comma-separated_values and https://tools.ietf.org/html/rfc4180 HTH, Sven BTW: the latest version can be found at https://github.com/svenvc/NeoCSV for more than 2 years, the older repositories are no longer maintained or kept up to date. > On 30 Apr 2020, at 18:39, PAUL DEBRUICKER <pdebruic(a)gmail.com> wrote: > > Hi - > > This is on Pharo 7 with Neo-CSV-Core-SvenVanCaekenberghe.28 > > > In a CSV file I have several instances of records like > > > "123","asdf", "one two "three" four five", "5678" > > > When that line is parsed instead of an Array with 4 records > > '123' > 'asdf' > 'one two "three" four five' > '5678' > > > I instead get > > '123' > 'asdf' > '"one two "three" four five"' > '"5678"' > > Is there a standard way or setting for handing strings with quoted strings in them? > > I'd like to end up with the expected result rather than the result I'm getting. > > > Thanks > > Paul > >

April 30, 2020

NeoCSV - how to parse a string with unescaped quoted string inside it?

by PAUL DEBRUICKER

Hi - This is on Pharo 7 with Neo-CSV-Core-SvenVanCaekenberghe.28 In a CSV file I have several instances of records like "123","asdf", "one two "three" four five", "5678" When that line is parsed instead of an Array with 4 records '123' 'asdf' 'one two "three" four five' '5678' I instead get '123' 'asdf' '"one two "three" four five"' '"5678"' Is there a standard way or setting for handing strings with quoted strings in them? I'd like to end up with the expected result rather than the result I'm getting. Thanks Paul

April 30, 2020

Re: [Pharo-users] mentor question 4

by Pablo Navarro

I proposed as alternative to Luhn check. In special to validation problems like credit card number validation. El jue., 30 abr. 2020 11:11, Richard O'Keefe <raoknz(a)gmail.com> escribiÃ³: > I'm sure you could fit regular expressions into the Luhn check, > but I am rather mystified as to what one could possibly gain by doing so. > How do you do the equivalent of > #(0 2 4 6 8 1 3 5 7 9) at: char digitValue + 1 > in a regular expression and why would you want to? > > On Fri, 1 May 2020 at 01:31, Pablo Navarro <pablo1n7(a)gmail.com> wrote: > > > > Hello!. For this problem is possible to use Regular Expressions too. > > > > > https://ci.inria.fr/pharo-contribution/job/UpdatedPharoByExample/lastSucces… > > > > Saludos, Pablo. > > El 30 de abr. de 2020 10:11 -0300, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr>, escribiÃ³: > > > > It looks like a cool problem > > from where did you take it? > > > > I hope I can discuss my approch to this problem : > > > > Given a number determine whether or not it is valid per the Luhn formula. > > > > The Luhn algorithm is a simple checksum formula used to validate a > variety of identification numbers, such as credit card numbers and Canadian > Social Insurance Numbers. > > > > The task is to check if a given string is valid. > > > > > > > > I like people that are always thinking in string as if a collection of > number would not make it :) > > > > Validating a Number > > > > Strings of length 1 or less are not valid. Spaces are allowed in the > input, but they should be stripped before checking. All other non-digit > characters are disallowed. > > > > Example 1: valid credit card number > > > > 4539 1488 0343 6467 > > > > The first step of the Luhn algorithm is to double every second digit, > starting from the right. We will be doubling > > > > 4_3_ 1_8_ 0_4_ 6_6_ > > > > If doubling the number results in a number greater than 9 then subtract > 9 from the product. The results of our doubling: > > > > 8569 2478 0383 3437 > > > > Then sum all of the digits: > > > > 8+5+6+9+2+4+7+8+0+3+8+3+3+4+3+7 = 80 > > > > If the sum is evenly divisible by 10, then the number is valid. This > number is valid! > > > > > > my idea was to do these steps > > > > 1) reverse the input. > > > > 2) use this to double every second digit and calculate the sum of all > the numbers : > > > > checkNumber := (collection reverse selectwith index: [:item :index | > (index % 2 == 0) . IfTrue: [item *2]] ) sumNumbers > > > > > > > > you can also > > 1 to: xx by: 2 do: > > > > 3) check if its a valid number by doing this : > > > > > > ^ (checkNumber % 10 == 0) > > > > > > is this a good game plan or has it flaws or can I do it better ? > > > > Regards, > > > > > > Roelof > > > > > > > > > > > > -------------------------------------------- > > 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 > > > >

April 30, 2020

Re: [Pharo-users] mentor question 4

by Roelof Wobben

Op 30-4-2020 om 16:16 schreef Roelof Wobben: > nextIsOdd := true. > Â Â Â Â aString reverseDo: [:digit | > Â Â Â Â Â Â Â Â digit = Character space ifFalse: [ > Â Â Â Â Â Â Â Â nextIsOdd > Â Â Â Â Â Â Â Â Â Â Â Â ifTrue:Â [oddSum := ...] > Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [evenSum := ...]. > Â Â Â Â Â Â Â Â nextIsOdd := nextIsOdd not]]. hmm, Still no luck with this code : cardNumber := '4539 1488 0343 6467'. oddSum := 0. evenSum := 0. nextIsOdd := true. Â Â Â Â cardNumber reverseDo: [:digit | Â Â Â Â Â Â Â Â digit = Character space ifFalse: [ Â Â Â Â Â Â Â Â nextIsOdd Â Â Â Â Â Â Â Â Â Â Â Â ifTrue:Â [oddSum := oddSum + digit asInteger ] Â Â Â Â Â Â Â Â Â Â Â Â ifFalse: [evenSum := ((digit asInteger * 2) > 9) Â Â Â ifTrue: [evenSum + ((digit asInteger * 2) - 9) ] Â Â Â ifFalse: [ evenSum + (digit asInteger * 2) ]]. Â Â Â Â Â Â Â Â Â Â nextIsOdd := nextIsOdd not]]. ^ oddSum + evenSum the answer schould be 57 where I get 1157 So some debugging to do

April 30, 2020

Re: [Pharo-users] Automating release announcements

by Gabriel Cotelli

I finally figure out how to make it work. For this mailing list you have to send the e-mail in CC and not BCC, because if not it gets retained awaiting for moderator approval. In case anyone is interested here is the GitHub action making the magic: https://github.com/ba-st-actions/email-release-notification Regards, Gabriel On Thu, Apr 30, 2020 at 9:13 AM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > marcus probably knows. > > let us what he is saying. > > On 30 Apr 2020, at 13:44, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > Hi!, Anyone here is moderator in the Pharo Users list? > > I want to automate the release announcement of projects in github/ba-st > org. I'm using sendgrid to send the e-mails and I'm getting a returning > mail saying: "Your message to Pharo-users awaits moderator approval". > > I subscribed previously to the list the e-mail account used as mail sender. > > Thank you for your help! > Gabriel > > > -------------------------------------------- > 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 > >

April 30, 2020