String >> format: is brittle with using #value and not is sync with Text >> format.

[marceltaeumel]

The last change from 7/13/2022 21:01 to String >> format: forgot to bring Text >> format: in sync.

And the support of blocks is unnecessary given that clients can easily put a value behind the respective argument if necessary. It is even dangerous because value is quite polymorphic in objects that are not values. At least, check for isBlock explicitely.

[squeak-smalltalk-bot]

Forwarding to involved parties.

________________________________ Von: Thiede, Christoph ***@***.***> Gesendet: Donnerstag, 14. August 2025 23:32 Uhr An: ***@***.*** ***@***.***> Betreff: [squeak-dev] Re: [squeak-smalltalk/squeak-object-memory] String >> format: is brittle with using #value and not is sync with Text >> format. (Issue #135)

And the support of blocks is unnecessary given that clients can easily put a `value` behind the respective argument if necessary.

I would love to learn more about Chris' original motivation to support blocks in this place. I can imagine a scenario where the string is not a quasi-interpolated constant literal but a dynamic user-provided pattern. E.g.: | date keys pattern | date := DateAndTime now . keys := #('ansi protocol' 'smalltalk-80') gather: [:cat | (date class selectorsInCategory: cat) select: #isUnary]. pattern := Project uiManager request: 'Enter date format' initialAnswer: '{year}-{month}-{dayOfMonth}'. pattern format: (keys collect: [:key | key -> [date perform: key]] as: Dictionary). Performance could matter in such scenarios. Then again, a lazy lookup object would be even more efficient here. Best, Christoph

…

--- Sent from Squeak Inbox Talk<https://github.com/hpi-swa-lab/squeak-inbox-talk>

On 2025-08-13T08:51:23-07:00, ***@***.*** wrote: marceltaeumel created an issue (squeak-smalltalk/squeak-object-memory#135) The last change from `7/13/2022 21:01` to `String >> format:` forgot to bring `Text >> format:` in sync. And the support of blocks is unnecessary given that clients can easily put a `value` behind the respective argument if necessary. It is even dangerous because `value` is quite polymorphic in objects that are not values. At least, check for `isBlock` explicitely. -- Reply to this email directly or view it on GitHub: #135 You are receiving this because you are subscribed to this thread. Message ID: <squeak-smalltalk/squeak-object-memory/issues/135(a)github.com>

[squeak-smalltalk-bot]

Dynamic formatting via late-binding is the purpose of supporting blocks here. There's an example in the comment: 'foo {NOW} bar' format: ({'NOW'-> [DateAndTime now]} as: Dictionary). It's for an app which persists these kinds of "template" definitions, including the Dictionary of arguments, in order to be recalled later for use. The template must be able to define values that'll be determined at runtime. - Chris On Thu, Aug 14, 2025 at 5:21 PM Thiede, Christoph < ***@***.***> wrote:

…

Forwarding to involved parties. ------------------------------ *Von:* Thiede, Christoph ***@***.***> *Gesendet:* Donnerstag, 14. August 2025 23:32 Uhr *An:* ***@***.*** < ***@***.***> *Betreff:* [squeak-dev] Re: [squeak-smalltalk/squeak-object-memory] String >> format: is brittle with using #value and not is sync with Text >> format. (Issue #135) > And the support of blocks is unnecessary given that clients can easily put a `value` behind the respective argument if necessary. I would love to learn more about Chris' original motivation to support blocks in this place. I can imagine a scenario where the string is not a quasi-interpolated constant literal but a dynamic user-provided pattern. E.g.: | date keys pattern | date := DateAndTime now . keys := #('ansi protocol' 'smalltalk-80') gather: [:cat | (date class selectorsInCategory: cat) select: #isUnary]. pattern := Project uiManager request: 'Enter date format' initialAnswer: '{year}-{month}-{dayOfMonth}'. pattern format: (keys collect: [:key | key -> [date perform: key]] as: Dictionary). Performance could matter in such scenarios. Then again, a lazy lookup object would be even more efficient here. Best, Christoph --- *Sent from **Squeak Inbox Talk <https://github.com/hpi-swa-lab/squeak-inbox-talk>* On 2025-08-13T08:51:23-07:00, ***@***.*** wrote: > marceltaeumel created an issue (squeak-smalltalk/squeak-object-memory#135) > > The last change from `7/13/2022 21:01` to `String >> format:` forgot to bring `Text >> format:` in sync. > > And the support of blocks is unnecessary given that clients can easily put a `value` behind the respective argument if necessary. It is even dangerous because `value` is quite polymorphic in objects that are not values. At least, check for `isBlock` explicitely. > > -- > Reply to this email directly or view it on GitHub: > #135 > You are receiving this because you are subscribed to this thread. > > Message ID: <squeak-smalltalk/squeak-object-memory/issues/135(a) github.com>