Following the release of
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: