- Pharo-dev - lists.pharo.org

LLM which coder is best?
by John M McIntosh Feb. 13, 2026

Feb. 13, 2026

Updated our release of ClaudeSmalltalk today to better support the OpenAI codex models, and added xAI support. Any Pharo developer who would like to assist in altering the code base to support Pharo? In asking the various LLM models to explain for example the class 'FMSound' I found that xAI Grok 4.1 Fast gave the best answer as compared to OpenAI, Anthropic, and Qwen. It is significantly cheap too. https://github.com/CorporateSmalltalkConsultingLtd/ClaudeSmalltalk/releases… .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

3 2

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

Feb. 10, 2026

Hi Richard. I checked the code and the double backticks are for the recursion mode. It forces the search to dive into the current matching node to find more cases inside it. For example: (instVar isNil ifTrue: [ 'inside recursion' ]) isNil ifTrue: [ 'outer node' ] The syntax with single backtick will not find the internal "instVar isNil" expression. In BPatterns the recursion mode is enabled by default for the pattern variables. So the default mode covers the maximum scope for a search. Currently you can't not disable the #recurseInto flag as there is not suitable accessor for this. But if it would be there the pattern would like: [ anyVar isNil ifTrue: anyBlock ] bpattern with: [ anyVar ] -> [:pattern | pattern recurseInto: false ] Anyway I adjusted my blog accordingly. Thanks for the attention. Ð²Ñ, 3 ÑÐµÐ²Ñ. 2026â¯Ð³. Ð² 10:47, Richard O'Keefe <raoknz(a)gmail.com>: > Thank you. One of the reasons given for introducing BPatterns is a subtle > difference between > single backticks and double backticks, which is mentioned but not > explained in the BPatterns > blog entry. The help screen you directed me to does not explain that. > > Is there any documentation which is *complete* and *proofread*? > > On Tue, 3 Feb 2026 at 23:16, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> 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 >>>> >>>> >>>> - >>>> >>>>

3 6

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