For string concatenation on the other hand, we're basically talking about dispersing a whole load of FUD about all the things that "may" go wrong. Fact is, nothing actually *does* go wrong with the change, but the change does fix situations that are *very* difficult to handle otherwise. One of the unfortunate realities of string concatenation is that it's very often used around error messages and logging, often in corner cases that aren't well tested, like:
<some impossible condition> ifTrue:[ self log: 'Found impossible condition: ', foo. ].
I do not buy this argument. We should fix the code and not break the libraries. Your argument is bogus. We do not want such kind of extensions that opens the door to really sloppy code. Then we should avoid overrides as much as possible. Stef