September 2023 - Pharo-dev - lists.pharo.org

This week (39/2023) on the Pharo Issue Tracker

by Marcus Denker

We merged 55 PRs this week # Pharo 11 - Backport: Clean installation of MCClassTraitDefinition #14768 https://github.com/pharo-project/pharo/pull/14768 # Upstream Sync - Zinc synch #14814 https://github.com/pharo-project/pharo/pull/14814 - Zodiac synch #14815 https://github.com/pharo-project/pharo/pull/14815 # Features - Add alternateRowsColor for Tree Table presenter. #1458 https://github.com/pharo-spec/Spec/pull/1458 - DrTest: Add shortcut to open DrTest #14763 https://github.com/pharo-project/pharo/pull/14763 # Fixes - Removed bomb icon in debugger and put drop down icon instead. #589 https://github.com/pharo-spec/NewTools/pull/589 - Displaying '#' for symbols in the debugger inspector #587 https://github.com/pharo-spec/NewTools/pull/587 - fix: SystemDictionary keys must now be symbols #14819 https://github.com/pharo-project/pharo/pull/14819 - 14400-allReferencesTo-aLiteral-do-aBlock-is-called-unknown-messages #14802 https://github.com/pharo-project/pharo/pull/14802 - More comments, better tests and better API #14788 https://github.com/pharo-project/pharo/pull/14788 - Fixes #14740 : '/..' asFileReference canonicalize returns incorrect result #14767 https://github.com/pharo-project/pharo/pull/14767 - WindowsStore>>printPathð handle the first segment size = 1 #14761 https://github.com/pharo-project/pharo/pull/14761 - Add an ensure block in Shift changes test to clean better the system #14762 https://github.com/pharo-project/pharo/pull/14762 # Packages - RPackage: Update meaning of #removePackage: #14799 https://github.com/pharo-project/pharo/pull/14799 - RPackage: Always return undefined package for unpackaged class #14791 https://github.com/pharo-project/pharo/pull/14791 - RPackage: Implement UndefinedPackage #14785 https://github.com/pharo-project/pharo/pull/14785 - RPackage: Deprecated RPackage>>#packageName #14784 https://github.com/pharo-project/pharo/pull/14784 - RPackage: divers cleanings #14777 https://github.com/pharo-project/pharo/pull/14777 - Monticello: Unloading a package should not load it in the change model #14776 https://github.com/pharo-project/pharo/pull/14776 - RPackage: Deprecate RPackage>>#importClass: #14772 https://github.com/pharo-project/pharo/pull/14772 - RPackage: depend less on categories in RPackage tests #14770 https://github.com/pharo-project/pharo/pull/14770 - Monticello: do not rely on MCClassTraitDefinition #14766 https://github.com/pharo-project/pharo/pull/14766 - Monticello: Clean installation of classes and traits #14759 https://github.com/pharo-project/pharo/pull/14759 - RPackage: Simplify package creation and deletion in tests #14747 https://github.com/pharo-project/pharo/pull/14747 - Do not use #categories in RPackage tests #14758 https://github.com/pharo-project/pharo/pull/14758 - Monticello: Fix st export of organizations #14756 https://github.com/pharo-project/pharo/pull/14756 - fix: expect package names to be hyphenated #14751 https://github.com/pharo-project/pharo/pull/14751 - RPackage: New step at unifying packages addition and removal #14733 https://github.com/pharo-project/pharo/pull/14733 - RPackage: Iteration on package cleanings #14744 https://github.com/pharo-project/pharo/pull/14744 - Unify class added and recategorized actions #14720 https://github.com/pharo-project/pharo/pull/14720 - RPackage: simplify classes cleanup of packages tests #14728 https://github.com/pharo-project/pharo/pull/14728 # Refactoring Engine - Remove classes improvements #14765 https://github.com/pharo-project/pharo/pull/14765 - Rename Driver into InteractionDriver + introduce RBInstanceVariableHaâ¦ #14755 https://github.com/pharo-project/pharo/pull/14755 - RemoveClassRefactoring: new generation #14745 https://github.com/pharo-project/pharo/pull/14745 # Tests - Clean some tests #14736 https://github.com/pharo-project/pharo/pull/14736 - The tests for text editor can be removed #14806 https://github.com/pharo-project/pharo/pull/14806 - Fix release tests and improve rules #14803 https://github.com/pharo-project/pharo/pull/14803 - Release tests: Improve management of unused variables #14794 https://github.com/pharo-project/pharo/pull/14794 - CharacterTest in wrong test package (new attempt with second PR) #14753 https://github.com/pharo-project/pharo/pull/14753 - ShClassInstallerTest>>#testInstallInSpecificEnvironment should clean â¦ #14748 https://github.com/pharo-project/pharo/pull/14748 # CI / Boostrap - Show executed instructions in getPharoVM.sh #14764 https://github.com/pharo-project/pharo/pull/14764 - Bootstrap should use P10 VM for small image #14792 https://github.com/pharo-project/pharo/pull/14792 # Speed - Compiler: do not use an intermediate stream when compiling BraceArray constructs {} #14779 https://github.com/pharo-project/pharo/pull/14779 # Cleanup - Remove usage of deprecated API #588 https://github.com/pharo-spec/NewTools/pull/588 - Generalize ReClassSideResetMethodProtocolRule #14738 https://github.com/pharo-project/pharo/pull/14738 - Typo in String>>#asUncommentedCode #14739 https://github.com/pharo-project/pharo/pull/14739 - Typo in settings - TKTConfiguration class>>#settingsOn: #14742 https://github.com/pharo-project/pharo/pull/14742 - Move all code base to Tonel V3 #14743 https://github.com/pharo-project/pharo/pull/14743 - #SHRBTextStyler: isScripting, not isWorkspace #14811 https://github.com/pharo-project/pharo/pull/14811 - Small cleanup FileSystemStore not needed #subclassResponsabiliy methods #14810 https://github.com/pharo-project/pharo/pull/14810 - FileReference-deleteIfAbsent-optimzied-ifTrue #14809 https://github.com/pharo-project/pharo/pull/14809 - onEventSensorStartup: cleanup #14804 https://github.com/pharo-project/pharo/pull/14804 - Fix deprecated call #14796 https://github.com/pharo-project/pharo/pull/14796 - RTFSelfCallInterpreter should be a subclass of RBProgramNodeVisitor #14780 https://github.com/pharo-project/pharo/pull/14780 - StInspectorThisContextNode should not be subclass of StInspectorSelfNode #586 https://github.com/pharo-spec/NewTools/pull/586

Sept. 29, 2023

Re: Sockets not working under heavy VM load?

by Sven Van Caekenberghe

I know this is very old, but is this still an issue today ? > On 29 Dec 2021, at 12:30, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, > > we have some performance issues with Glorp over P3 and, after some investigation, I have a theory that could explain it. And I would like to know your opinion if it is correct. > > To reproduce this issue, you can try something easy. Just create a process with normal or higher priority that will try to read something from a socket. And, in parallel, do in a separate thread an operation that takes all the processor time for several seconds. > > ```` > [ > 5 seconds wait. > Time now traceCr. > ZnClient new > url: 'https://www.google.com'; > get. > Time now traceCr. > ] forkAt: 60. > > [1000 timesRepeat: [ 10000 factorial ] ] timeToRun > ```` > (you may try a different safe server address) > > The processes run in parallel until the time when the first process tries to obtain data from the socket. Then it hangs and waits until finishing of the second process. > > My theory is that the VM socket plugin is able to receive incoming data from the connection and save it into the buffer. In the meantime, the reading process is waiting on the socket semaphore. But it looks like the plugin is not able to release the semaphore while the VM is actually doing something. It needs to wait until the VM has nothing useful to do, and then it is finally able to release the semaphores so Pharo processes are resumed and can start to read. > > Is my theory right? > > Cheers, > -- Pavel > > >

Sept. 28, 2023

Re: The results of the Pharo Browser usage survey are available

by tesonep＠gmail.com

That is a really cool survey, thanks for the work!!! On Tue, Sep 5, 2023 at 10:11â¯PM Koen De Hondt < koen(a)all-objects-all-the-time.st> wrote: > Dear Pharo users and developers, > > Last week at ESUGâ23 I presented the results of the survey on the usage of > the Pharo Browser. Half an hour was not enough to show and discuss all > questions and answers. You find all results on my blog: > https://all-objects-all-the-time.st/#/blog/posts/3. If you have > questions, comments, or suggestions, please do not hesitate to send me a > message. > > Best regards, > Koen > -- Pablo Tesone. tesonep(a)gmail.com

Sept. 26, 2023

Re: [Pharo-users] The results of the Pharo Browser usage survey are available

by Koen De Hondt

Guille, Thank you for the feedback. This is the action plan: * Talk about the Pharo browser at the Pharo Sprint this week (and probably repeat it at future Pharo Sprints). * Propose improvements via the issue tracker. * Experiment with alternative browsers. * Write blog posts about requirements, use cases, and technical challenges when designing and implementing alternative browsers. * Give a presentation about alternative browsers at ESUG 2024 ð I would say: keep an eye on https://all-objects-all-the-time.st <https://all-objects-all-the-time.st/>. The first posts about alternative browsers will arrive in October. I will send notifications about new posts in this channel. Ciao, Koen > On 6 Sep 2023, at 09:58, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Thanks Koen! Itâs fun to read in detail :) > > So, whatâs the action plan? > >> El 5 sep. 2023, a las 22:10, Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> escribiÃ³: >> >> Dear Pharo users and developers, >> >> Last week at ESUGâ23 I presented the results of the survey on the usage of the Pharo Browser. Half an hour was not enough to show and discuss all questions and answers. You find all results on my blog: https://all-objects-all-the-time.st/#/blog/posts/3. If you have questions, comments, or suggestions, please do not hesitate to send me a message. >> >> Best regards, >> Koen >

Sept. 26, 2023

This week (38/2023) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 11 - Make finalization registry entry removal O(1) -- backport P11 #14655 https://github.com/pharo-project/pharo/pull/14655 # Fixes - Treat a second click within the double-click window but in a different location as a separate click (fixes #14474) #14476 https://github.com/pharo-project/pharo/pull/14476 - Shift: Add tests and fix bugs in the change detectors #14702 https://github.com/pharo-project/pharo/pull/14702 - [Reopen] Migration of events from the debugger UI to the debugger action model to automate its updates #399 https://github.com/pharo-spec/NewTools/pull/399 - Revert "Extend SpDiffPresenter to make it navigable accross differences" #1456 https://github.com/pharo-spec/Spec/pull/1456 # Features - Introducing useful event when a debug session has been cleared, so that all subscribers can unsubscribe from any cleared session automatically #14670 https://github.com/pharo-project/pharo/pull/14670 - Depend on Tonel Pharo12 branch to get TonelV3 format #14669 https://github.com/pharo-project/pharo/pull/14669 # Package Cleanup - RPackage: cleanings now that SystemOrganizer is removed #14692 https://github.com/pharo-project/pharo/pull/14692 - Unify class added and recategorized actions #14720 https://github.com/pharo-project/pharo/pull/14720 - RPackage: simplify classes cleanup of packages tests #14728 https://github.com/pharo-project/pharo/pull/14728 - RPackage: #removeTag: should remove contained classes #14716 https://github.com/pharo-project/pharo/pull/14716 - RPackage: Some cleanings #14717 https://github.com/pharo-project/pharo/pull/14717 - RPackage:â¯Remove category map from RPackageOrganizer #14688 https://github.com/pharo-project/pharo/pull/14688 - RPackage: fileout should not rely on categories #14684 https://github.com/pharo-project/pharo/pull/14684 - RPackage: Rely less on categories in MCOrganizationDefinition #14678 https://github.com/pharo-project/pharo/pull/14678 - Kernel: Clean method removal (Protocol and Method announcements improvements) #14724 https://github.com/pharo-project/pharo/pull/14724 - Kernel: simplify renaming #14695 https://github.com/pharo-project/pharo/pull/14695 - Kernel: Always recompile silently methods #14696 https://github.com/pharo-project/pharo/pull/14696 - Kernel: simplify category management #14681 https://github.com/pharo-project/pharo/pull/14681 - Kernel: Make sure category is never nil #14676 https://github.com/pharo-project/pharo/pull/14676 # RB - tiny improvement RBBrowserEnvironment: use ifNil: #14703 https://github.com/pharo-project/pharo/pull/14703 - Fix: rename methods from different classes #14699 https://github.com/pharo-project/pharo/pull/14699 - Simpler RBNamespace>>#allClassesDo: #14698 https://github.com/pharo-project/pharo/pull/14698 - Refactor: rename class refactoring #14673 https://github.com/pharo-project/pharo/pull/14673 - 2023 09 16 enh rb code glitches #14675 https://github.com/pharo-project/pharo/pull/14675 # Cleanup - Clean some tests #14736 https://github.com/pharo-project/pharo/pull/14736 - Minimize the direct references to Transcript #14629 https://github.com/pharo-project/pharo/pull/14629 - Small refactoring: use #whichMethodsReferTo, not #whichSelectorsReferTo #14672 https://github.com/pharo-project/pharo/pull/14672 - Sync with Fuel #14677 https://github.com/pharo-project/pharo/pull/14677 - ClassDescription is an abstract class #14686 https://github.com/pharo-project/pharo/pull/14686 - change some methods to make sure that the ifNil: message can be inlined #14694 https://github.com/pharo-project/pharo/pull/14694 - String class>>#crlfcrlf has no senders #14730 https://github.com/pharo-project/pharo/pull/14730 - #species should be in private protocol #14735 https://github.com/pharo-project/pharo/pull/14735 - Symbol>>#asAnnouncement should be an extension #14727 https://github.com/pharo-project/pharo/pull/14727 - Comment TFFunctionDefinition >> validate #14718 https://github.com/pharo-project/pharo/pull/14718 - Reflectivity cleaning and comments #14712 https://github.com/pharo-project/pharo/pull/14712 - 14674-ReflectiveMethod-invokes-not-defined-method-isFromTrait #14685 https://github.com/pharo-project/pharo/pull/14685 - use optimzied ifNil #1457 https://github.com/pharo-spec/Spec/pull/1457 # Website - Delete site/2017pharodays.md #54 https://github.com/pharo-project/pharo-website/pull/54 - Update index-links #53 https://github.com/pharo-project/pharo-website/pull/53

Sept. 22, 2023

Re: Literal collections are coming to you :)

by David Mason

Great!! Thanks, Stef! Now on to the parrot operator, initializing local variables at point of declaration, and destructuring collections.... (For those for whom these are new ideas, see: https://github.com/dvmason/Pharo-Functional ) ../Dave On Mon, 18 Sept 2023 at 15:40, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > testNestedLiteralSet > > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: > RBParserLiteralCollection. > self > assert: (compiler evaluate: '{ :Set 1 . { :Set 2 . 2 } . > 1}' ) > equals: (Set new add: 1 ; add: (Set new add: 2; add: 2; > yourself); add: 1 ;yourself). > > > > testOrderedCollection > > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: > RBParserLiteralCollection. > self > assert: (compiler evaluate: '{ :OrderedCollection 1 . 2 . > 1 . 3}â ) > equals: #(1 2 1 3) asOrderedCollection. > > > testDictionary > > | compiler dict | > compiler := OpalCompiler new. > compiler compilationContext parserClass: > RBParserLiteralCollection. > dict := (compiler evaluate: '{ :Dictionary #a -> 33 . #b -> 44}' ). > self assert: (dict at: #a) equals: 33 > > I want to thank dave mason for the design! > > S > > >

Sept. 18, 2023

Re: fun with Pharo: literal collections are coming to you :)

by Daniel Slomovits

Interesting! I submitted a Phep a while back to implement a compile-time literal syntax ##() as seen in Dolphin Smalltalk, with literal collections like this as a major (though not exclusive) use-case. At the time I couldn't think of a way to do better for arbitrary collections, but this is a very natural extension of the brace-array syntaxâclever use of the block-argument-esque leading colon. I still like some things about the flexibility of the compile-time literal approach, but this certainly has it beat for terseness in the common case! One question about the implementationâdoes it reduce straightforwardly to instantiation and repeated sends of `add:`, or a single `withAll:` or similar, or does it depend on knowledge of the underlying collection implementation? Put another way, would it work with a custom collection class? What about a class that isn't a descendant of Collection at all, but understands the right protocol? On Mon, Sep 18, 2023 at 3:16â¯PM Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > Cool! > > Noury > On Sep 18 2023, at 5:20 pm, stephane ducasse <stephane.ducasse(a)inria.fr> > wrote: > > In a Phep005 soon available > > testLiteralSet > > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > self assert: (compiler evaluate: > '{ :Set 1 . 2 . 1}' ) > > equals: #(1 2) asSet. > > > > testOrderedCollection > > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > self assert: (compiler evaluate: > '{ :OrderedCollection 1 . 2 . 1 . 3}' ) > > equals: #(1 2 1 3) asOrderedCollection. > > > testDictionary > > | compiler dict | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > dict := (compiler evaluate: > '{ :Dictionary #a -> 33 . #b -> 44}' ). > self assert: (dict at: #a) equals: 33 > >

Sept. 18, 2023

Literal collections are coming to you :)

by stephane ducasse

testNestedLiteralSet | compiler | compiler := OpalCompiler new. compiler compilationContext parserClass: RBParserLiteralCollection. self assert: (compiler evaluate: '{ :Set 1 . { :Set 2 . 2 } . 1}' ) equals: (Set new add: 1 ; add: (Set new add: 2; add: 2; yourself); add: 1 ;yourself). testOrderedCollection | compiler | compiler := OpalCompiler new. compiler compilationContext parserClass: RBParserLiteralCollection. self assert: (compiler evaluate: '{ :OrderedCollection 1 . 2 . 1 . 3}â ) equals: #(1 2 1 3) asOrderedCollection. testDictionary | compiler dict | compiler := OpalCompiler new. compiler compilationContext parserClass: RBParserLiteralCollection. dict := (compiler evaluate: '{ :Dictionary #a -> 33 . #b -> 44}' ). self assert: (dict at: #a) equals: 33 I want to thank dave mason for the design! S

Sept. 18, 2023

Re: fun with Pharo: literal collections are coming to you :)

by Noury Bouraqadi

Cool! Noury On Sep 18 2023, at 5:20 pm, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > In a Phep005 soon available > > testLiteralSet > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > self assert: (compiler evaluate: > '{ :Set 1 . 2 . 1}' ) > > equals: #(1 2) asSet. > > > testOrderedCollection > | compiler | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > self assert: (compiler evaluate: > '{ :OrderedCollection 1 . 2 . 1 . 3}' ) > > equals: #(1 2 1 3) asOrderedCollection. > > testDictionary > | compiler dict | > compiler := OpalCompiler new. > compiler compilationContext parserClass: RBParserLiteralCollection. > dict := (compiler evaluate: > '{ :Dictionary #a -> 33 . #b -> 44}' ). > self assert: (dict at: #a) equals: 33 >

Sept. 18, 2023

Re: Next Pharo sprints

by Noury Bouraqadi

Thank you @Guille and @Marcus for the dates. Next sprint 29th of sept, Luc and I will attend. Noury On Sep 14 2023, at 2:21 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > The next dates are: > 29/09 > 27/10 > 24/11 > 22/12 âChristmas Sprintâ > > > Marcus > > > On 14 Sep 2023, at 12:26, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > > > Hi, > > > > I'd like to attend. When is the next one ? > > > > Noury > > > > On Wed, Sep 13, 2023, 09:42 Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi all, > > > > For those who would like to participate, we are opening the Pharo sprints we do at Lille every last friday of the month. > > Feel free to contact us if you would like to participate, drop an email or a message somewhere :) > > > > More info in the link below! > > > > https://thepharo.dev/2023/09/13/next-pharo-sprints-lille/ > > > > G >

Sept. 18, 2023