‘%1 %2′ % { ‘Hello’. ‘world’ } => ‘Hello world’
‘

Note a subtle difference between ” and String new. The former is read-only, the latter is not. One case where this is important, is when #become: enters the scene. For example you can have a proxy object like

Proxy class>>on: aBlock
^self basicNew set__Block: aBlock

Proxy>>set__Block: aBlock
block := aBlock

Proxy>>doesNotUnderstand: aMessage
[ block value become: self. "assumes two-way become!" ]
on: Error do: [ :ex | ex pass. ^self ].
^self perform: aMessage

then, only “Proxy on: [ String new ]” will work. Either of “Proxy on: [ '' ]” or “Proxy on: [ 3 ]” won’t work. Indeed, you better put that exception handler or bad usage will lock up the system. Of course, this is made up, but you got the idea.

Also interesting is “(p := Proxy on: [ p ]) foo”, which will nicely halt the system. :-)

100 @ 50

I make use of

Point x: 100 y: 50.

Yes, it’s much more verbose but it’s very clear. To me clarity is more important than brevity via cryptic symbols.

I also now use “String new” rather than the empty string, ”. Again for clarity but also to avoid any confusion about which instance is being referred to.