December 2020 - Pharo-users

Re: Can a class be not equal to itself?

by Konrad Hinsen

On 31/12/2020 12:19, Konrad Hinsen wrote: > It's been a while since I have encountered mysterious behavior in > Pharo, but today it happened. I set up a dictionary with classes as > keys, and got "Key not found" errors for keys that were definitely in > my dictionary. A quick debugging session showed the underlying issue: > I had two references to a class which look the same when inspected, > but turn out to be not identical (==) and thus not equal (=). How can > this happen? Update, after a few more debugging sessions: my dictionary is the result of a deepCopy operation, meaning the class has been copied. And the copy of a class is indeed a distinct but otherwise indistinguishable class. 'Object copy = Object' is 'false'. Konrad.

Dec. 31, 2020

Re: Can a class be not equal to itself?

by Tudor Girba

Hi Konrad, Could it be that you have overridden = on the class side of your class? Otherwise, I do not see how this can happen. Cheers, Tudor > On Dec 31, 2020, at 12:19 PM, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > > Hi everyone, > > > It's been a while since I have encountered mysterious behavior in Pharo, but today it happened. I set up a dictionary with classes as keys, and got "Key not found" errors for keys that were definitely in my dictionary. A quick debugging session showed the underlying issue: I had two references to a class which look the same when inspected, but turn out to be not identical (==) and thus not equal (=). How can this happen? > > > Konrad. -- feenk.com "It's not how it is, it is how we see it."

Dec. 31, 2020

Can a class be not equal to itself?

by Konrad Hinsen

Hi everyone, It's been a while since I have encountered mysterious behavior in Pharo, but today it happened. I set up a dictionary with classes as keys, and got "Key not found" errors for keys that were definitely in my dictionary. A quick debugging session showed the underlying issue: I had two references to a class which look the same when inspected, but turn out to be not identical (==) and thus not equal (=). How can this happen? Konrad.

Dec. 31, 2020

Re: PrintString in PBE8

by 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 <stephane.ducasse(a)inria.fr> wrote: > > > On 26 Dec 2020, at 20:41, Sean P. DeNigris <sean(a)clipperadams.com> 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 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 > > > > > Yes but with such approach you still create an extra intermediary > stream. > > The solution should be > > > aStream > nextPutAll: ' with value: â. > count printOn: aStream > > Now this is a bit more tricky to do. > > > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Dec. 29, 2020

Re: Pharo and Virtual Realitity

by Sven Van Caekenberghe

> On 28 Dec 2020, at 03:25, askoh <askoh(a)askoh.com> wrote: > > ZnReadEvalPrintDelegate startInServerOn: 1701. > > (ZnServer on: 1701) > bindingAddress: NetNameResolver localHostAddress; > delegate: ZnReadEvalPrintDelegate new; > start; > yourself I don't know anything about VRIDE but the above two expressions are equivalent, they do the same thing, twice. You need only one of them.

Dec. 28, 2020

Re: Pharo and Virtual Realitity

by askoh

Hi: I installed Pharo and enter the following in workspace. Author uniqueInstance fullName: 'VRIDE User'. Metacello new baseline: 'Roassal3'; repository: 'github://ObjectProfile/Roassal3'; load. Metacello new baseline: 'Roassal3Exporters'; repository: 'github://ObjectProfile/Roassal3Exporters'; load. Metacello new baseline: 'Roassal3Exporters'; repository: 'github://ObjectProfile/Roassal3Exporters'; load: 'AFrame'. ZnReadEvalPrintDelegate startInServerOn: 1701. (ZnServer on: 1701) bindingAddress: NetNameResolver localHostAddress; delegate: ZnReadEvalPrintDelegate new; start; yourself PharoVRIDE open I don't understand the following instructions in GitHub page: Now open PharoVRIDE. Right into the first scene, you will see a field asking for the IP address of your Pharo server. It must be as follows: http://<Host name or IP Address>:<Port>/repl If you are running on localhost just as shown in the previous script, press the Enter button to proceed. Otherwise, you must specify an address. Finally, put on your VR headset, and try some stuff! Please advise. Thanks, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 28, 2020

Re: PrintString in PBE8

by StÃ©phane Ducasse

> On 26 Dec 2020, at 20:41, Sean P. DeNigris <sean(a)clipperadams.com> 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 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 > > Yes but with such approach you still create an extra intermediary stream. The solution should be aStream nextPutAll: ' with value: â. count printOn: aStream Now this is a bit more tricky to do. > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 27, 2020

Re: PrintString in PBE8

by 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 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 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 26, 2020

Re: PrintString in PBE8

by 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 <stephane.ducasse(a)inria.fr> wrote: > > Ah indeed. > So we will have to have a look. > > S > >> On 25 Dec 2020, at 16:36, Sven Van Caekenberghe <sven(a)stfx.eu <mailto:sven@stfx.eu>> 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. >> >>> On 25 Dec 2020, at 16:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: >>> >>> 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 cleaner in that case. >>> >>> >>>> On 24 Dec 2020, at 18:32, g_patrickb--- via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: >>>> >>>> I started working through PBE8, and in section 3.13 there is a method: >>>> >>>> Counter >> printOn: aStream >>>> >>>> super printOn: aStream. >>>> >>>> aStream nextPutAll: ' with value: ', count printString. >>>> >>>> But it returns two warnings: >>>> >>>> [printString] No printString inside printOn >>>> >>>> Use cascaded nextPutAll:âs instead of #, in #nextPutAll: >>>> >>>> >>>> >>>> It has the option to automatically resolve the cascaded nextPutAll: which results in: >>>> >>>> printOn: aStream >>>> >>>> super printOn: aStream. >>>> >>>> aStream >>>> >>>> nextPutAll: ' with value: '; >>>> >>>> nextPutAll: count printString >>>> >>>> >>>> >>>> But it still has the warning about printString. >>>> >>> >>> -------------------------------------------- >>> StÃ©phane Ducasse >>> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> >>> 03 59 35 87 52 >>> Assistant: Aurore Dalle >>> FAX 03 59 57 78 50 >>> TEL 03 59 35 86 16 >>> S. Ducasse - Inria >>> 40, avenue Halley, >>> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >>> Villeneuve d'Ascq 59650 >>> France >>> > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <http://www.pharo.org/> > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 25, 2020

Re: PrintString in PBE8

by StÃ©phane Ducasse

Ah indeed. So we will have to have a look. S > On 25 Dec 2020, at 16:36, Sven Van Caekenberghe <sven(a)stfx.eu> 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. > >> On 25 Dec 2020, at 16:20, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> 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 cleaner in that case. >> >> >>> On 24 Dec 2020, at 18:32, g_patrickb--- via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> I started working through PBE8, and in section 3.13 there is a method: >>> >>> Counter >> printOn: aStream >>> >>> super printOn: aStream. >>> >>> aStream nextPutAll: ' with value: ', count printString. >>> >>> But it returns two warnings: >>> >>> [printString] No printString inside printOn >>> >>> Use cascaded nextPutAll:âs instead of #, in #nextPutAll: >>> >>> >>> >>> It has the option to automatically resolve the cascaded nextPutAll: which results in: >>> >>> printOn: aStream >>> >>> super printOn: aStream. >>> >>> aStream >>> >>> nextPutAll: ' with value: '; >>> >>> nextPutAll: count printString >>> >>> >>> >>> But it still has the warning about printString. >>> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Dec. 25, 2020