Sven Van Caekenberghe-2 wrote
Maybe his question is (also) why the automatic refactoring did it wrong,
the rules warned about the wrong use of #printString, suggested a fix, but
the solution is still using #printString, hence the same problem.
I might be reading it wrong, but I thought everything worked as advertised,
and the limitation was that there was no option to automatically fix the
other warning about the printString. The "Use cascaded nextPutAll:���s instead
of #, in #nextPutAll:" transformation did change:
aStream nextPutAll: ' with value: ', count printString.
to:
aStream
��nextPutAll: ' with value: ';
��nextPutAll: count printString