February 2026 - Pharo-dev - lists.pharo.org

Re: [Pharo-users] [Ann] New deprecations API

by Denis Kudriashov

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 >> >>

Feb. 3, 2026

[Ann] New deprecations API

by Denis Kudriashov

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

Feb. 2, 2026

Re: [Pharo-users] [Ann] BPatterns: The rewrite engine at your fingertips

by Richard Sargent

Excellent! That is so welcome!! On Mon, Feb 2, 2026, 04: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 > > > - > >

Feb. 2, 2026

[Ann] BPatterns: The rewrite engine at your fingertips

by Denis Kudriashov

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 -

Feb. 2, 2026