- Pharo-dev - lists.pharo.org

Re: Clean Blocks in Pharo 14

by Daniel Slomovits

Test-run-based code critics would definitely be cool. Though in this case, I think a static analysis using heuristics could get us 99% of the way thereâif the receiver (heh) of the #receiver message is a variable node whose name contains "ctx" or "context", or a message send which is known to return only things other than BlockClosures (e.g. all the context-chain navigation messages like #sender), we can disregard that call site. Starting from ~400 senders of #receiver it wouldn't surprise me if that cut it down to as few as 10 or 20 that could be manually checked. Unfortunately I am not as fluent in the Code Critic as I am in the simpler interfaces in Dolphin Smalltalk, so I can't just bang something out in 5 minutes, but it's fundamentally not hard. On Thu, Jul 10, 2025 at 4:35â¯AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > On 9 Jul 2025, at 21:37, Daniel Slomovits <daniels220(a)gmail.com> wrote: > > > > This is very cool to see. One noteâI would personally not outright > deprecate #receiver, but leave a comment indicating that it is not > guaranteed to be set and why. There are plenty of cases where getting nil > as the receiver of a clean block is correct, or at least good enoughâI > wouldn't want to eventually lose the ability to officially access it > entirely, which is what deprecation implies. > > Yes, trueâ¦ I wonder how to provide support for people to find potential > problematic use. > > One thing we really need is Code Critics, but not doing static analysis > but working on test run data. > > We could > -> add probe in #receiver > -> run tests > -> log all send sites > -> tool shows all uses of #receiver that need to be checked > > > Marcus

July 15, 2025

Pharo News of the Week 28/2025

by Marcus Denker

# Pharo News of the Week 28/2025 - [Video][Smalltalks 2024] Soil: an object oriented database for fun and profit https://www.youtube.com/watch?v=JWY5HCUlX_4 - [Smalltalks 2024][Pharo in Action] ApptiveGrid: solve (business) problems without programming https://www.youtube.com/watch?v=aPtsGswPJAc - [Blog] Hera Voted 2nd in the ESUG 2025 Innovation Technology Awards https://all-objects-all-the-time.st/#/blog/posts/16 - [Blog] Describing Web Applications with Hera https://all-objects-all-the-time.st/#/blog/posts/17 - [ANN] A local MCP server to evaluate Pharo Smalltalk expressions and get system information via NeoConsole. https://github.com/mumez/pharo-nc-mcp-server - [ANN] Pharo client libraries for accessing the Claude API https://github.com/newapplesho/claude-client-smalltalk - GeoTools: Geographic Tools as Coordinates, Kinematics and Geodesic utilities for GIS. https://github.com/ThalesGroup/GeoTools - AIActions â AI-based Comment Generator for Pharo https://github.com/kasperosterbye/PharoAIActions - pharo-archive: Pharo bindings for libarchive https://github.com/estebanlm/pharo-archive If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 12 - Fix lock DNU on P12 and on #18377 https://github.com/pharo-project/pharo/pull/18377 - [P12] Fixing Build #18367 https://github.com/pharo-project/pharo/pull/18367 # Pharo 13 - Backport: fix cleanup undeclared registry after renaming a class #18368 https://github.com/pharo-project/pharo/pull/18368 - continue-to-generate-P30-artifacts #18379 https://github.com/pharo-project/pharo/pull/18379 # Fixes - fix: up/down cursor motion didn't move directly up/down in the presence of tab characters #18348 https://github.com/pharo-project/pharo/pull/18348 # Refactoring Engine - Fix: use correct method to find method #18369 https://github.com/pharo-project/pharo/pull/18369 # Sytax Highlight - introduce a new superclass to SHRBTextStyler and move all the non morâ¦ #18385 https://github.com/pharo-project/pharo/pull/18385 # Code Completion - Code Completion: Fixing all little glitches. #18372 https://github.com/pharo-project/pharo/pull/18372 - Fix the completion by placing a default one after the dependency heurâ¦ #18371 https://github.com/pharo-project/pharo/pull/18371 # Compiler - Enable clean blocks in Pharo14 #18322 https://github.com/pharo-project/pharo/pull/18322 # Tools - Added back fileOut functionnality for the packages #18366 https://github.com/pharo-project/pharo/pull/18366 - Cleaning debugger action model: less dependencies on ast scope #1182 https://github.com/pharo-spec/NewTools/pull/1182 - fixed object transcript recieving beacons when closed if logger was left turn on #1202 https://github.com/pharo-spec/NewTools/pull/1202 - Implement stpulse find all button #1201 https://github.com/pharo-spec/NewTools/pull/1201 - Fixing focus bug on st pulse and tests #1200 https://github.com/pharo-spec/NewTools/pull/1200 - update from Cavrois improved with placeholders #1198 https://github.com/pharo-spec/NewTools/pull/1198 - Fixed the same profile switch bug - Pharo 13 #1196 https://github.com/pharo-spec/NewTools/pull/1196 - Playground Binding presenter #1194 https://github.com/pharo-spec/NewTools/pull/1194 - Reverted deleted stEntry methods that were removed when moving the class #1188 https://github.com/pharo-spec/NewTools/pull/1188 - 1172 implementors in the new transcript #1185 https://github.com/pharo-spec/NewTools/pull/1185 # Spec - add whenFilterChangedDo: event #1791 https://github.com/pharo-spec/Spec/pull/1791 # Git Support - Added back github api menu for repositories #1950 https://github.com/pharo-vcs/iceberg/pull/1950 # Tests - add test for #odd #18338 https://github.com/pharo-project/pharo/pull/18338

July 11, 2025

Re: Clean Blocks in Pharo 14

by Marcus Denker

> On 9 Jul 2025, at 21:37, Daniel Slomovits <daniels220(a)gmail.com> wrote: > > This is very cool to see. One noteâI would personally not outright deprecate #receiver, but leave a comment indicating that it is not guaranteed to be set and why. There are plenty of cases where getting nil as the receiver of a clean block is correct, or at least good enoughâI wouldn't want to eventually lose the ability to officially access it entirely, which is what deprecation implies. Yes, trueâ¦ I wonder how to provide support for people to find potential problematic use. One thing we really need is Code Critics, but not doing static analysis but working on test run data. We could -> add probe in #receiver -> run tests -> log all send sites -> tool shows all uses of #receiver that need to be checked Marcus

July 10, 2025

Re: Clean Blocks in Pharo 14

by Daniel Slomovits

This is very cool to see. One noteâI would personally not outright deprecate #receiver, but leave a comment indicating that it is not guaranteed to be set and why. There are plenty of cases where getting nil as the receiver of a clean block is correct, or at least good enoughâI wouldn't want to eventually lose the ability to officially access it entirely, which is what deprecation implies. On Wed, Jul 9, 2025 at 4:06â¯AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > We have enabled the "Clean Block Closure" option for Pharo14 > > # What is this? > > Until now, blocks are created at runtime, but there are blocks that > actually do not need any runtime data to be created. > > Thus "Clean blocks" are those blocks that > - do not access self > - do not access instance variables (which needs self) > - do not return > - do not access temp variables from outer blocks or the method > > With the clean block option enabled, the compiler can create the object at > compile time. > > For Pharo12, we already enabled a sub-set: Constant Blocks. Now we do the > next step: pre-create *all* clean blocks. > > # What is the effect? > > Positive: > - much faster (we see a factor of 9 speedup for creating a block > like [1+2] ) > - the resulting block does not reference the outer context / self > => GC can cleanup more > - #isClean check on blocks is *much* faster (nice if you check for > it e.g. for serialization) > > But: > > This means that we now have blocks that have no outerContext and #receiver > returns nil. > All code that relies on these needs to be changed to take this into > account. > > We enabled Clean Blocks early in Pharo14 so we find all remaining > problems, especially related to external code. > > So if you see strange behavior (especially in the debugger), please open > an issue on the issue tracker! > > We are interested, too, in cases where you rely on either the receiver or > the outerContext for blocks in your own code. > > > # What next? > > - Deprecate #receiver on BlockClosure > - Track down all remaining problems (e.g. debugger) > > After: > - we want to enable to option to only reference the outerContext > only for those blocks that need it (that do a non-local return). > (there is a compiler option already, but disabled by > default) > - only blocks that access self should hold onto the receiver > - .. and more > >

July 9, 2025

Clean Blocks in Pharo 14

by Marcus Denker

We have enabled the "Clean Block Closure" option for Pharo14 # What is this? Until now, blocks are created at runtime, but there are blocks that actually do not need any runtime data to be created. Thus "Clean blocks" are those blocks that - do not access self - do not access instance variables (which needs self) - do not return - do not access temp variables from outer blocks or the method With the clean block option enabled, the compiler can create the object at compile time. For Pharo12, we already enabled a sub-set: Constant Blocks. Now we do the next step: pre-create *all* clean blocks. # What is the effect? Positive: - much faster (we see a factor of 9 speedup for creating a block like [1+2] ) - the resulting block does not reference the outer context / self => GC can cleanup more - #isClean check on blocks is *much* faster (nice if you check for it e.g. for serialization) But: This means that we now have blocks that have no outerContext and #receiver returns nil. All code that relies on these needs to be changed to take this into account. We enabled Clean Blocks early in Pharo14 so we find all remaining problems, especially related to external code. So if you see strange behavior (especially in the debugger), please open an issue on the issue tracker! We are interested, too, in cases where you rely on either the receiver or the outerContext for blocks in your own code. # What next? - Deprecate #receiver on BlockClosure - Track down all remaining problems (e.g. debugger) After: - we want to enable to option to only reference the outerContext only for those blocks that need it (that do a non-local return). (there is a compiler option already, but disabled by default) - only blocks that access self should hold onto the receiver - .. and more

July 9, 2025

"Describing Web Applications with Hera" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, At ESUG 2025, I demonstrated how Hera can be used to describe the behaviour of web applications when combined with Parasol. I wrote a blog post about it so that you can try it for yourself. See https://all-objects-all-the-time.st/#/blog/posts/17. As always, all feedback is welcome. Enjoy, Koen

July 6, 2025

Pharo News of the Week 27/2025

by Marcus Denker

# Pharo News of the Week 27/2025 - pharo-cig: A tool to import C/C++ libraries into Pharo https://github.com/estebanlm/pharo-cig - pharo-resvg: Pharo bindings for resvg https://github.com/estebanlm/pharo-resvg - ChatPharo: an AI Assistant inside the Pharo environment https://github.com/omarabedelkader/ChatPharo - GeoView: Views to display and interact with geographical objects and cartographic layers https://github.com/ThalesGroup/GeoView - [blog post] Basic Hera Usage as a Video Story https://all-objects-all-the-time.st/#/blog/posts/15 If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Fixes - Fix problem with previous completion enh PR - Rescue a lost class. #18360 https://github.com/pharo-project/pharo/pull/18360 - Fix: rename method violators are list and not single instance #18363 https://github.com/pharo-project/pharo/pull/18363 - FilePresenter: Fix cancelling of FilePresenter via UIManager #18314 https://github.com/pharo-project/pharo/pull/18314 # Tools - Fix wrong place for entries #1184 https://github.com/pharo-spec/NewTools/pull/1184 - Fix: window fails to open when message list is nil initially #1193 https://github.com/pharo-spec/NewTools/pull/1193 - Enh/packagescopecompletion #18357 https://github.com/pharo-project/pharo/pull/18357 - Cavrois update profile improvement #1191 https://github.com/pharo-spec/NewTools/pull/1191 # Iceberg - fix: don't throw uncaught exceptions when a validation error occurs #1928 https://github.com/pharo-vcs/iceberg/pull/1928 # Refactoring Engine - Refactor: rename Refactory* classes in Pharo #1192 https://github.com/pharo-spec/NewTools/pull/1192 - Refactor: migrating and cleaning Inline Method refactoring #18359 https://github.com/pharo-project/pharo/pull/18359 - Rename all RBRefactoryChanges into ReChanges #18346 https://github.com/pharo-project/pharo/pull/18346 - Fix a really dumb endless loop in PullUpMethod. #18324 https://github.com/pharo-project/pharo/pull/18324 - Fix Refactoring issue #18212 #18315 https://github.com/pharo-project/pharo/pull/18315 - Add subclass fix #18296 https://github.com/pharo-project/pharo/pull/18296 - Update to class Rename #1189 https://github.com/pharo-spec/NewTools/pull/1189 # Tests - Improve and fix testProperManifestCategorization #18358 https://github.com/pharo-project/pharo/pull/18358 - Adding packages for tests (may be in the future we should truen them â¦ #18361 https://github.com/pharo-project/pharo/pull/18361 - Add comment and executable comments to String>>copyUpToSubstring: #18352 https://github.com/pharo-project/pharo/pull/18352 - Avoid clean blocks for ED tests #18349 https://github.com/pharo-project/pharo/pull/18349 - I added executable comments to withoutSuffix and withoutPrefix in String class #18347 https://github.com/pharo-project/pharo/pull/18347 - Add behaviour preservation tests for Add Method #18321 https://github.com/pharo-project/pharo/pull/18321 # Cleaup - containing is misspelled #718 https://github.com/pharo-project/pharo-launcher/pull/718 - Simplify Stream API #18141 https://github.com/pharo-project/pharo/pull/18141 - Simplify OSEnvironment #18038 https://github.com/pharo-project/pharo/pull/18038 - remove ProfStef and ProfStef-Test from baselines #18310 https://github.com/pharo-project/pharo/pull/18310

July 4, 2025

"Basic Hera Usage as a Video Story " â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, In my presentation at ESUG 2025 yesterday, I included some videos about using Hera. If you'd like to watch the videos again, I've written a blog post that includes all the videos, along with the explanation I provided in the presentation. See https://all-objects-all-the-time.st/#/blog/posts/15. Enjoy, Koen

July 2, 2025

ChatPharo - stable version

by Omar Abedelkader

Hey everyone, Iâm happy to share that ChatPharo has now reached its stable release! You can find it here: [ https://github.com/omarabedelkader/ChatPharo | https://github.com/omarabedelkader/ChatPharo ] If you are interested in receiving news about ChatPharo, I have created a broadcast list: chatpharo(a)inria.fr Cheers, Omar -- Omar ABEDELKADER Doctorant, Ãquipe EVREF [ https://www.inria.fr/fr/evref | inria.fr/fr/evref ] [ https://www.cristal.univ-lille.fr/profil/omarabedelkader/ | cristal.univ-lille.fr/omarabedelkader ] / Institut National de Recherche en Sciences et Technologies du NumÃ©rique Parc Scientifique de la Haute Borne Park Plaza - BÃ¢timent A - 40 avenue Halley 59650 Villeneuve d'Ascq - France Si vous lisez ce courriel en dehors de vos heures de travail, merci de ne le traiter quâen cas dâurgence avÃ©rÃ©e. Si ce courriel ne vous est pas destinÃ©, merci de ne pas en prendre connaissance, le dÃ©truire et en informer lâexpÃ©diteur. Merci de nâimprimer ce courriel quâen cas de nÃ©cessitÃ©.

July 2, 2025

Pharo News of the Week 26/2025

by Marcus Denker

- [ANN] TinyLogger V2.0.0 https://github.com/jecisc/TinyLogger/releases/tag/v2.0.0 - [ANN] Advanced-Design MOOC on Youtube https://pharo.org/news/2025-06-26-Mooc-Youtube.html - [ANN] Pharo 13.1 Released - https://pharo.org/news/2025-06-26-Pharo13.1.html If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Implements compatibility with Strict Symbol Comparison feature in Pharo #1682 https://github.com/pharo-spec/Spec/pull/1682 # Pharo 13 - update new tools to v0.10.4 and spec to v2.0.3 #18313 https://github.com/pharo-project/pharo/pull/18313 # Fixes - use UIManager default in OCCodeReparator instead of a direct access to MorphicUIManager #18299 https://github.com/pharo-project/pharo/pull/18299 - Give more feedback in testMethodDefinition #18311 https://github.com/pharo-project/pharo/pull/18311 - Fixed the resize bug and improved code #1180 https://github.com/pharo-spec/NewTools/pull/1180 - Remove fast table search by default #1553 https://github.com/pharo-spec/Spec/pull/1553 # Features - Add shortcut for closing windows #18298 https://github.com/pharo-project/pharo/pull/18298 - Adding trim* API to Text to be polymorphic to String. #18309 https://github.com/pharo-project/pharo/pull/18309 # Tools - small fix on NewTools-Spotter-Processors -> stQuery >> updatefromContext #1146 https://github.com/pharo-spec/NewTools/pull/1146 - Improve Epicea search #18306 https://github.com/pharo-project/pharo/pull/18306 - New methods to define window title for Pull up/down refactorings #18303 https://github.com/pharo-project/pharo/pull/18303 - DrTest second pane displayed as a tree #18297 https://github.com/pharo-project/pharo/pull/18297 - Small fix cavrois window manager #1183 https://github.com/pharo-spec/NewTools/pull/1183 - Fixing new tools baseline #1181 https://github.com/pharo-spec/NewTools/pull/1181 - Simplified whole position back method by using placeholders windows #1179 https://github.com/pharo-spec/NewTools/pull/1179 - Profile windows gets resized with the world #1178 https://github.com/pharo-spec/NewTools/pull/1178 - Added a toggle instead of remove for cell mode #1177 https://github.com/pharo-spec/NewTools/pull/1177 - display the strategies title instead of class name #1176 https://github.com/pharo-spec/NewTools/pull/1176 - Fix browser should not be in "New tools preview" anymore #1171 https://github.com/pharo-spec/NewTools/pull/1171 - Fix StRewriteCritiqueChangesBrowserPresenter opening #1170 https://github.com/pharo-spec/NewTools/pull/1170 - Add stpulse #1164 https://github.com/pharo-spec/NewTools/pull/1164 # Cleanup - rename examples and ClapHelp command #18312 https://github.com/pharo-project/pharo/pull/18312 - Reduced UIManager api #1751 https://github.com/pharo-spec/Spec/pull/1751

June 29, 2025