July 2024 - Pharo-users - lists.pharo.org

Looking for new adventures

by Koen De Hondt

Dear Pharo Community, As you may have read on my blog <https://all-objects-all-the-time.st/#/blog/posts/1> or heard during my ESUGâ23 presentation, eighteen months ago I entered the Pharo scene after being away from the Smalltalk community for 20 years. For the last one and a half years, I have been a member of a team using Pharo and GemStone. I attended almost all Pharo Sprints in Lille (every last Friday of the month). In this channel, I have informed you about my intention to build a new browser based on Spec. That development has been on the back burner for the last five months because I have been working hard with StÃ©phane Ducasse to finish the book âApplication Building with Spec 2.0â. I have presented at ESUGâ23, and I am sad that I could not attend ESUGâ24 this week. >From the above, my contribution to the Pharo community is clear, and I think my drive to contribute more is also clear. In a few months, I will leave the team I am working with now. Therefore, I am looking for new adventures. If you are looking for a seasoned software developer who likes working in Smalltalk/Pharo very much, please send me a message, and I will be in touch rapidly. Please find more details on my career history on LinkedIn <https://www.linkedin.com/in/koendehondt/>. Best regards, Koen

July 12, 2024

This week (28/2024) on the Pharo Issue Tracker

by Marcus Denker

This week we reached 10.000 closed pull requests on the main repository (see https://github.com/pharo-project/pharo/pulls) The week did not see many changes merged due to many contributors attending (and giving talks at) this years ESUG conference. # Pharo 12 Backports - [P12] Fix MetacelloRepositoryGroup with duplicated repository #16859 https://github.com/pharo-project/pharo/pull/16859 # Fixes - Fix: deprecate method refactoring to applicability preconditions as list #16867 https://github.com/pharo-project/pharo/pull/16867 - Fix multiple tests with refactoring driver for duplicate class. #16853 https://github.com/pharo-project/pharo/pull/16853 - [P13] Fix MetacelloRepositoryGroup with duplicated repository #1686 https://github.com/pharo-project/pharo/pull/16860 - ffi: add a cache for array types of same type and size #16877 https://github.com/pharo-project/pharo/pull/16877 # Cleanup - Update transmissionBlock: -> transmits: #793 https://github.com/pharo-spec/NewTools/pull/793

July 12, 2024

Re: [ANN] Pharo Launcher 3.2 released!

by bajger＠gmail.com

Congrats Christophe for the release! Great achievement! I was (am) happy to collaborate on this project. Hopefully community would find it useful - please share your feedback! David

July 12, 2024

[ANN] Pharo Launcher 3.2 released!

by Christophe Demarey

Hi all, Pharo Launcher 3.2 has just been released! It is available from http://pharo.org/download. Pharo Launcher now comes with a command-line version that you can use from a terminal! You can check the documentation of commands at https://pharo-project.github.io/pharo-launcher/commands-cmd-line/ as well as instructions to make pharo-launcher available on command line: https://pharo-project.github.io/pharo-launcher/installation/. This nice feature is now available thanks to the contributions of Axel Marlard, David Bajger and I as well as the support of Damien Pollet for the Clap library. New features: Command Line support all commands available in the UI version of Pharo Launcher are supported new commands create an image from a Pull Request number (from Pharo repository) create an image from a build number, a SHA create an image and import your code from a repository share easily an image (zip file with the Pharo image, the VM to run it and a launch script) find easily the Pharo version where a bug was introduced with image bisect algorithm launch an image with a script list running Pharo processes When creating an image, the image is now launched automatically CI moved to Github Actions Improvements: Better Mac Os system menu Do not try to guess anymore the version of a Pharo image if information not available but rather ask the user When deleting more than 1 image at a time the message is not clear #594 <https://github.com/pharo-project/pharo-launcher/issues/594> Bug fixes: Pharo 12.0 build list incomplete #667 <https://github.com/pharo-project/pharo-launcher/issues/667> Use "Show" when no image is downloaded yet gives error #570 <https://github.com/pharo-project/pharo-launcher/issues/570> (thanks to @astares <https://github.com/astares>) Development mode does not close pharoLauncher application #548 <https://github.com/pharo-project/pharo-launcher/issues/548> Using "Show in folder" gives DNU #568 <https://github.com/pharo-project/pharo-launcher/issues/568> (thanks to @astares <https://github.com/astares>) Launcher cannot launch Pharo-4.0 image #585 <https://github.com/pharo-project/pharo-launcher/issues/585> Regards, The Pharo team.

July 10, 2024

Re: Help with PetitParser2 rules

by Rafael Luque

Thank you, Frank. I'll try your suggestion. El dom, 7 jul 2024 a las 6:19, vfclists (<vfclists(a)gmail.com>) escribiÃ³: > > > On Fri, 5 Jul 2024 at 10:39, Rafael Luque <rafael.luque.leiva(a)gmail.com> > wrote: > >> Hi all, >> >> I'm struggling with a small parser using PetitParser2. Here is a fragment >> of some of the rules I'm defining but their behaviour is not as I could >> expect: >> >> andKeyword := 'and' asPParser trim, #letter asPParser not. >> notKeyword := 'not' asPParser trim, #letter asPParser not. >> keyword := andKeyword / notKeyword. >> nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser >> star. >> word := nonKeywordIdentifier, #blank asPParser star. >> words := word star. >> >> The behaviour of the "nonKeywordIdentifier" is the expected: >> >> identifier end parse: 'hello'. "It parses successfully" >> identifier end parse: 'and'. "It fails as 'and' is a keyword" >> >> However the "words" rule's behavior is the following: >> >> words end parse: 'hello Pharo'. "It parses successfully" >> words end parse: 'hello and bye'. "It parses, when I would expect it >> fails because of 'and' is a keyword" >> >> I don't understand why the "words" rule works this way, but I'm starting >> with PetitParser. Any suggestions? >> >> Thank you. >> > > You might consider asking on stackoverflow. > > A PetitParser2 question has been answered there recently. > -- > Frank Church > > ======================= > >

July 7, 2024

Re: Help with PetitParser2 rules

by vfclists

On Fri, 5 Jul 2024 at 10:39, Rafael Luque <rafael.luque.leiva(a)gmail.com> wrote: > Hi all, > > I'm struggling with a small parser using PetitParser2. Here is a fragment > of some of the rules I'm defining but their behaviour is not as I could > expect: > > andKeyword := 'and' asPParser trim, #letter asPParser not. > notKeyword := 'not' asPParser trim, #letter asPParser not. > keyword := andKeyword / notKeyword. > nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser > star. > word := nonKeywordIdentifier, #blank asPParser star. > words := word star. > > The behaviour of the "nonKeywordIdentifier" is the expected: > > identifier end parse: 'hello'. "It parses successfully" > identifier end parse: 'and'. "It fails as 'and' is a keyword" > > However the "words" rule's behavior is the following: > > words end parse: 'hello Pharo'. "It parses successfully" > words end parse: 'hello and bye'. "It parses, when I would expect it fails > because of 'and' is a keyword" > > I don't understand why the "words" rule works this way, but I'm starting > with PetitParser. Any suggestions? > > Thank you. > You might consider asking on stackoverflow. A PetitParser2 question has been answered there recently. -- Frank Church =======================

July 7, 2024

This week (27/2024) on the Pharo Issue Tracker

by Marcus Denker

Main work this week happend on the CI infrastruture (and getting the test green for Pharo13 again), we did not merge lots of PRs due to that. # Pharo 12 - [P12][Backport] Fix recompilation of dead block twice in debugger #16784 https://github.com/pharo-project/pharo/pull/16784 # Fixes - Improve contrasts of DarkBlueTheme #16822 https://github.com/pharo-project/pharo/pull/16822 # Cleanup - Fixing issue#14145: ycAbstractAllInstVarAccessorsCommand >> variable never set #16820 https://github.com/pharo-project/pharo/pull/16820 - fix #15843: Reduce references to Transcript #16830 https://github.com/pharo-project/pharo/pull/16830 - fixed issue #15252: Cleanup: Small Lint issue in ZnImageExampleDelegate>>#handlePostRequest: #16815 https://github.com/pharo-project/pharo/pull/16815 # Documentation - Updated class comments of UUID and UUIDGenerator #16817 https://github.com/pharo-project/pharo/pull/16817

July 5, 2024

Help with PetitParser2 rules

by Rafael Luque

Hi all, I'm struggling with a small parser using PetitParser2. Here is a fragment of some of the rules I'm defining but their behaviour is not as I could expect: andKeyword := 'and' asPParser trim, #letter asPParser not. notKeyword := 'not' asPParser trim, #letter asPParser not. keyword := andKeyword / notKeyword. nonKeywordIdentifier := keyword not, #letter asPParser, #word asPParser star. word := nonKeywordIdentifier, #blank asPParser star. words := word star. The behaviour of the "nonKeywordIdentifier" is the expected: identifier end parse: 'hello'. "It parses successfully" identifier end parse: 'and'. "It fails as 'and' is a keyword" However the "words" rule's behavior is the following: words end parse: 'hello Pharo'. "It parses successfully" words end parse: 'hello and bye'. "It parses, when I would expect it fails because of 'and' is a keyword" I don't understand why the "words" rule works this way, but I'm starting with PetitParser. Any suggestions? Thank you.

July 5, 2024

isLoop 2024: 2nd International School on Live Object-Oriented Programming

by Sebastian Jordan Montano

Hello everyone, We are happy to announce that on August 5-9 Pharo Consortium is organizing the International School on Live Object-Oriented Programming (isLoop 2024) in Montpellier - a sunny French city near the coast of the Mediterranean sea. Participation is free and open to everyone. But if you want to participate, you must fill the registration form as soon as possible: [ https://forms.gle/f8RBnU11MM8BLKeRA | https://forms.gle/f8RBnU11MM8BLKeRA ] More information can be found on our website: [ https://isloop24.pharo.org/ | https://isloop24.pharo.org ] If you have any additional questions, don't hesitate to contact Oleksandr at [ mailto:oleksandr.zaitsev@cirad.fr | oleksandr.zaitsev(a)cirad.fr ] And we would also be grateful if you could share this information with your colleagues and students. See you soon! Oleksandr Zaitsev and Sebastian Jordan

July 2, 2024