- Pharo-dev - lists.pharo.org

Re: [Pharo-users] [Ann] BPatterns: The rewrite engine at your fingertips
by Denis Kudriashov Feb. 3, 2026

Feb. 3, 2026

Yes. There is nice help presenter in the Pharo: StRewriterHelpBrowserPresenter new open [image: Screenshot 2026-02-03 at 10.15.45.png] Ð²Ñ, 3 ÑÐµÐ²Ñ. 2026â¯Ð³. Ð² 01:36, Richard O'Keefe <raoknz(a)gmail.com>: > Is the "classic" rewriting syntax documented anywhere? > > On Mon, 2 Feb 2026 at 22:52, Denis Kudriashov via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> Hi all. >> >> This is the release of *BPatterns* project, one of my old ideas on how >> to make the rewrite engine usable for scripting. >> >> As a quick reminder, here is an example of the classic rewrite-engine >> matching syntax: >> >> *``@receiver isNil ifTrue: ``@nilBlock* >> >> >> In practice, patterns like this usually live inside string >> literalsâhidden away in lint rules, deprecations, or refactorings. >> To use them for *manual* code search or rewriting, you typically need a >> dedicated tool. >> >> Now compare that with the same pattern expressed as a *BPattern*: >> >> *[ any isNil ifTrue: anyBlock ] bpattern* >> >> No special syntax. >> No magical tools. >> Just pure Smalltalk. >> >> You write a block. >> You send #bpattern. >> Youâre done. >> >> Every editor understands it. >> Every tool respects it. >> >> Want to see where this pattern appears? >> >> * [ any isNil ifTrue: anyBlock ] bpattern browseUsers* >> >> >> [image: Screenshot 2026-01-31 at 12.16.19.png] >> >> Want to rewrite all of them? >> >> *[[ any isNil ifTrue: anyBlock ] -> [ any ifNil: anyBlock ]] brewrite >> preview* >> >> >> [image: Screenshot 2026-01-31 at 12.17.57.png] >> >> Because *BPatterns are real Smalltalk code*, all development tools work >> out of the box: >> syntax highlighting, completion, navigation, refactorings. >> >> This is the rewrite engine treated as a *first-class citizen*. >> >> Not strings. >> Not tooling sidecars. >> Not just for advanced users. >> >> *A rewrite engine you can actually use.* >> * A rewrite engine at your fingertips.* >> More details are in the blog post: >> >> - >> https://dionisiydk.blogspot.com/2026/02/bpatterns-rewrite-engine-with-small… >> >> And follow the project on GitHub: >> >> - https://github.com/dionisiydk/BPatterns >> >> >> - >> >>

1 0

Re: [Pharo-users] [Ann] New deprecations API
by Denis Kudriashov Feb. 3, 2026

Feb. 3, 2026

Hi Richard. Not sure I understand your question. But I think there is no difference with the old deprecation approach Ð²Ñ, 3 ÑÐµÐ²Ñ. 2026â¯Ð³. Ð² 07:04, Richard O'Keefe <raoknz(a)gmail.com>: > Nice. > What happens when there are uses of a deprecated method in files held in a > repository > but not currently loaded into the image? > How does one get rewrite rules applied to a bunch of files? > > On Tue, 3 Feb 2026 at 11:22, Denis Kudriashov via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> Following the release of *BPatterns >> <https://github.com/dionisiydk/BPatterns>*, I am happy to share another >> idea that naturally grows out of it: *simplifying deprecations in Pharo*. >> >> Todayâs deprecations are powerful but verboseâstring-based rewrite rules, >> duplicated selectors, and boilerplate that most of us copy from examples. >> >> With BPatterns, all of this can be eliminated: >> >> Object>>confirm: queryString >> ^ self *deprecatedBy: * [ ConfirmationRequest signal: queryString >> ] >> >> Deprecation is now expressed in the same language as the code itself, not >> in a separate, string-based mini-language. There is no need to think about >> transformation rulesâthey are part of the system and enabled by default. >> >> Zero boilerplate. >> No duplicated code >> For more details and comparison with current API see the blog post: >> >> >> - >> https://dionisiydk.blogspot.com/2026/02/deprecations-as-they-should-be.html >> >>

1 0

[Ann] New deprecations API
by Denis Kudriashov Feb. 2, 2026

Feb. 2, 2026

Following the release of *BPatterns <https://github.com/dionisiydk/BPatterns>*, I am happy to share another idea that naturally grows out of it: *simplifying deprecations in Pharo*. Todayâs deprecations are powerful but verboseâstring-based rewrite rules, duplicated selectors, and boilerplate that most of us copy from examples. With BPatterns, all of this can be eliminated: Object>>confirm: queryString ^ self *deprecatedBy: * [ ConfirmationRequest signal: queryString ] Deprecation is now expressed in the same language as the code itself, not in a separate, string-based mini-language. There is no need to think about transformation rulesâthey are part of the system and enabled by default. Zero boilerplate. No duplicated code For more details and comparison with current API see the blog post: - https://dionisiydk.blogspot.com/2026/02/deprecations-as-they-should-be.html

1 0

[Ann] BPatterns: The rewrite engine at your fingertips
by Denis Kudriashov Feb. 2, 2026

Feb. 2, 2026

Hi all. This is the release of *BPatterns* project, one of my old ideas on how to make the rewrite engine usable for scripting. As a quick reminder, here is an example of the classic rewrite-engine matching syntax: *``@receiver isNil ifTrue: ``@nilBlock* In practice, patterns like this usually live inside string literalsâhidden away in lint rules, deprecations, or refactorings. To use them for *manual* code search or rewriting, you typically need a dedicated tool. Now compare that with the same pattern expressed as a *BPattern*: *[ any isNil ifTrue: anyBlock ] bpattern* No special syntax. No magical tools. Just pure Smalltalk. You write a block. You send #bpattern. Youâre done. Every editor understands it. Every tool respects it. Want to see where this pattern appears? * [ any isNil ifTrue: anyBlock ] bpattern browseUsers* [image: Screenshot 2026-01-31 at 12.16.19.png] Want to rewrite all of them? *[[ any isNil ifTrue: anyBlock ] -> [ any ifNil: anyBlock ]] brewrite preview* [image: Screenshot 2026-01-31 at 12.17.57.png] Because *BPatterns are real Smalltalk code*, all development tools work out of the box: syntax highlighting, completion, navigation, refactorings. This is the rewrite engine treated as a *first-class citizen*. Not strings. Not tooling sidecars. Not just for advanced users. *A rewrite engine you can actually use.* * A rewrite engine at your fingertips.* More details are in the blog post: - https://dionisiydk.blogspot.com/2026/02/bpatterns-rewrite-engine-with-small… And follow the project on GitHub: - https://github.com/dionisiydk/BPatterns -

2 1

"Spec Window Management in Hera" â New blog post on all: objects all: theTime
by Koen De Hondt Jan. 30, 2026

Jan. 30, 2026

Dear Pharo users and developers, I started a series of posts about describing Spec application behaviour with Hera. The first post explains how Hera manages open Spec windows and describes the Gherkin steps involved with windows. https://all-objects-all-the-time.st/#/blog/posts/19 As always, all feedback is welcome. Happy reading! Ciao, Koen

1 0

Smalltalk & clawdbot
by John M McIntosh Jan. 30, 2026

Jan. 30, 2026

Runs the Squeak 6.0 environment on Linux. Access from your telegram account https://clawdhub.com/johnmci/smalltalk Clawdbot did all the work, now an approved contributor to https://github.com/CorporateSmalltalkConsultingLtd/ClaudeSmalltalk .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk Sent from [Proton Mail](https://proton.me/mail/home) for iOS.

2 2

How to improve sharpiness of fonts
by stephane ducasse Jan. 28, 2026

Jan. 28, 2026

Hi guys Happy new year! I would like to share with you a need. I have different screens of different DPI and my view is not getting better. Now on retina the fonts are either too small (zoom 100) or too large (150) so I end up having blurry fonts. I would like to know if the situation could be improved with font that have a larger spectrum of sizes. May be using the fonts of the OS could help too. Any idea and help is welcome. S

2 1

AI systems & Smalltalk
by John M McIntosh Jan. 24, 2026

Jan. 24, 2026

This evening I added ChatGPT support to our work on AI systems talking to Squeak and Cuis systems. Likely 10 minutes to enable Pharo to join the party, any takers?https://github.com/CorporateSmalltalkConsultingLtd/ClaudeSmalltalk .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

4 4

Claude & Smalltalk
by John M McIntosh Jan. 21, 2026

Jan. 21, 2026

Hi, if you've been watch Claude Code taking over the world, missing interacting with Smalltalk, then I've build out an interface so you can talk to Cuis Smalltalk. However the Python MCP bridge interfaces to a Smalltalk solution via MQTT so a bit of work could be done to enable one to talk to a Pharo image. https://github.com/CorporateSmalltalkConsultingLtd/SmalltalkCuisMCP .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

1 0

Looking for Metacello beta testers
by stephane ducasse Jan. 4, 2026

Jan. 4, 2026

Hello Under the radar, we are actively continiously cleaning Pharo deep core so that we can work on new features. For metacello, in Pharo 13 we introduced a strict mode (so that we can detect hidden dependencies), and other loading features to support module experimentations. It will make Pharo code more robust in the long term. Since a couple of months we are actively simplifying/cleaning Metacello (as the version available in Pharo) because we want to introduce new features such as the possibility to force the reload of baselines and others. Now the unit test coverage of metacello is quite low and we do not use/know all the features that are available and that you may rely on. So we would love to have beta testers that can just try to load their code in Pharo 14 alpha and report potential bugs or features drop we would have introduced. So do not hesitate and this is a nice way to help pharo S.

2 2