[Pharo-users] Re: PrintString in PBE8

I opened a ticket. https://github.com/pharo-project/pharo/issues/8178 > On 25 Dec 2020, at 22:43, Stéphane Ducasse wrote: > > Ah indeed. > So we will have to have a look. > > S > >> On 25 Dec 2020, at 16:36, Sven Van Caekenberghe > > wrote: >> >> Maybe his question is

[Pharo-users] Re: PrintString in PBE8

Ah indeed. So we will have to have a look. S > On 25 Dec 2020, at 16:36, Sven Van Caekenberghe 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 #prin

[Pharo-users] Re: PrintString in PBE8

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. > On 25 Dec 2020, at 16:20, Stéphane Ducasse wrote: > > Hi > > this warning is

[Pharo-users] Re: PrintString in PBE8

Hi this warning is just that printOn: is working on a stream and when we do printOn: aStream aStream nextPutAll: x printString printString creates yeat another stream then ask the contents and passes it to the first one printOn: aStream x printOn: aStream is faster and c