- Pharo-users - lists.pharo.org

Re: [Pharo-users] a basic hash question

by CÃ©drick BÃ©ler

But it raises the question if : (1 to:4)hash = #(1 2 3 4)hash should return true instead ?? Cedrick > Le 30 juil. 2018 Ã 14:51, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> a Ã©crit : > > Just a quick guess seeing the implementation > > hash for collections is about hash of its elements > > SequencableCollection>>hasEqualElements: otherCollection > "Answer whether the receiver's size is the same as otherCollection's > size, and each of the receiver's elements equal the corresponding > element of otherCollection. > This should probably replace the current definition of #= ." > > | size | > (otherCollection isKindOf: SequenceableCollection) ifFalse: [^ false]. > (size := self size) = otherCollection size ifFalse: [^ false]. > 1 to: size do: > [:index | > (self at: index) = (otherCollection at: index) ifFalse: [^ false]]. > ^ true > > Cheers, > > CÃ©drick > >> Le 30 juil. 2018 Ã 14:07, werner kassens <wkassens(a)libello.com> a Ã©crit : >> >> Hi, >> i guess i can subsume almost everything i know about hashes in one sentence: >> it is my understanding that two objects that are equal (obj1=obj2. >> -->true) have to have the same hash value (which is used for some >> collection types), whereas objects where obj1=obj2 returns false should >> have different hash values although it may happen that they have the >> same one. >> >> now here things don't turn out exactly like that: >> (1 to:4) = #(1 2 3 4). "true" >> (1 to:4)hash = #(1 2 3 4)hash. "false" >> well ok, actually these results make - pfffh, in a certain way - sense >> to me, but i wonder what arguments the people in the know would use to >> defend that result, if i would have another opinion? >> werner >> >> >

July 30, 2018

Re: [Pharo-users] a basic hash question

by CÃ©drick BÃ©ler

Just a quick guess seeing the implementation hash for collections is about hash of its elements SequencableCollection>>hasEqualElements: otherCollection "Answer whether the receiver's size is the same as otherCollection's size, and each of the receiver's elements equal the corresponding element of otherCollection. This should probably replace the current definition of #= ." | size | (otherCollection isKindOf: SequenceableCollection) ifFalse: [^ false]. (size := self size) = otherCollection size ifFalse: [^ false]. 1 to: size do: [:index | (self at: index) = (otherCollection at: index) ifFalse: [^ false]]. ^ true Cheers, CÃ©drick > Le 30 juil. 2018 Ã 14:07, werner kassens <wkassens(a)libello.com> a Ã©crit : > > Hi, > i guess i can subsume almost everything i know about hashes in one sentence: > it is my understanding that two objects that are equal (obj1=obj2. > -->true) have to have the same hash value (which is used for some > collection types), whereas objects where obj1=obj2 returns false should > have different hash values although it may happen that they have the > same one. > > now here things don't turn out exactly like that: > (1 to:4) = #(1 2 3 4). "true" > (1 to:4)hash = #(1 2 3 4)hash. "false" > well ok, actually these results make - pfffh, in a certain way - sense > to me, but i wonder what arguments the people in the know would use to > defend that result, if i would have another opinion? > werner > >

July 30, 2018

a basic hash question

by werner kassens

Hi, i guess i can subsume almost everything i know about hashes in one sentence: it is my understanding that two objects that are equal (obj1=obj2. -->true) have to have the same hash value (which is used for some collection types), whereas objects where obj1=obj2 returns false should have different hash values although it may happen that they have the same one. now here things don't turn out exactly like that: (1 to:4) = #(1 2 3 4). "true" (1 to:4)hash = #(1 2 3 4)hash. "false" well ok, actually these results make - pfffh, in a certain way - sense to me, but i wonder what arguments the people in the know would use to defend that result, if i would have another opinion? werner

July 30, 2018

Re: [Pharo-users] Morph reacting to Window being closed

by Henrik-Nergaard

Hi Peter, There are two methods which can be used for this purpose. #outOfWorld: #announceDeleted Both are called recursively down the morph tree from the window. If you need to stop the window or provide a dialog then you should create a subclass of Model and use that to keep references to things that need cleanup and control the closing and other events. Best regards, Henrik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 29, 2018

Re: [Pharo-users] [ANN] Pharo Git Thermite Release

by Andrew Black

Hi Ronie, These visualizations look great! But I donât know what they mean. When one hovers the mouse over the visualizations, does help text appear explaining what one is looking at? For example, I guess that the red and green segments in âLines of Codeâ refer to lines deleted and added. But what are the green and yellow for âClassesâ. And whatâs a âFunctionâ in Pharo? The more complicated diagram for âRoassal2â I canât even begin to guess at! Donât make the mistake of thinking that because you know what the diagram means, after working on it for months, that other programmers will also know. Andrew

July 29, 2018

Re: [Pharo-users] Morph reacting to Window being closed

by Hilaire

Hi Peter, I think you have two options: 1. Specialize the Window and use your own delete method to do your additional cleaning. This is what I do in Dr. Geo. 2. Use the WindowClosed announcement from system window to catch the signal from the morph you want to clean Hilaire Le 29/07/2018 Ã 13:35, Peter UhnÃ¡k a Ã©critÂ : > how can a Morph react to its parent window being closed? > > E.g. > > Morph subclass: #MyMorph. > MyMorph new openInWindow > > how can MyMorph cleanup itself on window close? > > I thought Morph>>delete would do the trick, but it is not being called. > > Thanks, > Peter -- Dr. Geo http://drgeo.eu

July 29, 2018

Morph reacting to Window being closed

by Peter UhnÃ¡k

Hi, how can a Morph react to its parent window being closed? E.g. Morph subclass: #MyMorph. MyMorph new openInWindow how can MyMorph cleanup itself on window close? I thought Morph>>delete would do the trick, but it is not being called. Thanks, Peter

July 29, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by Serge Stinckwich

On Sat, Jul 28, 2018 at 11:21 AM H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Hello > > What is the status of this project? > > > https://github.com/jmari/JupyterTalk > > âYou can ask the author of the software, Jesus Mari Aguirre. He is quite active. W âe talk together about be able to use Jupytalk with Tensorflow and PolyMath. He was able to reproduce part of my talk about Tensorflow: https://htmlpreview.github.io/?https://github.com/jmari/JupyterTalk/blob/ma… -- Serge Stinckwich UMI UMMISCO 209 (SU/IRD/UY1) "Programs must be written for people to read, and only incidentally for machines to execute."http://www.doesnotunderstand.org/

July 28, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Git Thermite Release

by peter yoo

Wow!! so great!!!

July 28, 2018

Re: [Pharo-users] Monticello default repositories & Iceberg

by Tim Mackinnon

Yeah - I had a similar problem and had forgotten that the global startup settings are applied every tine you launch an image. Not at my computer - but on OS X they are in the is Library subfolder, on Windows there is some profile directories. Tim Sent from my iPhone > On 28 Jul 2018, at 03:13, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Evan Donahue wrote >> I see a "default local repository" and a "local cache directory" that >> point to old obsolete paths >> from years ago on my machine. > > Could this be the result of an obsolete startup script? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

July 28, 2018