[Pharo-users] Re: PrintString in PBE8

2020-12-29 Thread Julián Maestri
As far as I know: aStream nextPutAll: ' with value: ‘; print: count. Works with most streams, does not create intermediary streams, and is readable. On Sun, 27 Dec 2020 at 05:59, Stéphane Ducasse wrote: > > > On 26 Dec 2020, at 20:41, Sean P. DeNigris wrote: > > Sven Van Caekenberghe-

[Pharo-users] Re: PrintString in PBE8

2020-12-27 Thread Stéphane Ducasse
> On 26 Dec 2020, at 20:41, Sean P. DeNigris wrote: > > 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

[Pharo-users] Re: PrintString in PBE8

2020-12-26 Thread Sean P. DeNigris
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 every

[Pharo-users] Re: PrintString in PBE8

2020-12-25 Thread Stéphane Ducasse
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

2020-12-25 Thread Stéphane Ducasse
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

2020-12-25 Thread Sven Van Caekenberghe
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

2020-12-25 Thread Stéphane Ducasse
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

[Pharo-users] Re: PrintString in PBE8

2020-12-24 Thread Richard Sargent
You should be able to replace nextPutAll: count printString with print: count On December 24, 2020 9:32:38 AM PST, g_patrickb--- via Pharo-users wrote: >I started working through PBE8, and in section 3.13 there is a method: > >`Counter >> printOn: aStream ` > >`super printOn: aStream. `