April 2015 - Pharo-dev - lists.pharo.org

VM and .sources in separate dirs question

by Dmitri Zagidulin

While editing an Updated Pharo by Example chapter, I came across this: "The '.sources' file and the VM can be read-only, and can be shared between different users. All of these files can be placed in the same directory, but it is also possible to put the Virtual Machine and sources file in separate directory where everyone has access to them." Is this true, that you can keep the VM and .sources in different directories? How do you tell the VM where to locate the sources? I assume it's some sort of commandline parameter?

April 3, 2015

Ways to do 32-bit arithmetics?

by Stefan Marr

Hi: I am porting some benchmarks to Pharo, which rely on a deterministic random number generator that uses 32 bit values. In order to have properly comparable results across platforms, it needs to generated the same sequence of numbers. So, I am looking for efficient ways to implement it, any ideas? I am a little at a loss, with SmallInts and Long Ints, how to get the proper 32-bit values, and how to apply the correct shifts, especially the right shift can be problematic. Code examples below. Thanks Stefan In Java it looks like this: private static int seed; // Robert Jenkins' 32 bit integer hash function. public static int random() { seed = ((seed + 0x7ed55d16) + (seed << 12)) & 0xffffffff; seed = ((seed ^ 0xc761c23c) ^ (seed >>> 19)) & 0xffffffff; seed = ((seed + 0x165667b1) + (seed << 5)) & 0xffffffff; seed = ((seed + 0xd3a2646c) ^ (seed << 9)) & 0xffffffff; seed = ((seed + 0xfd7046c5) + (seed << 3)) & 0xffffffff; seed = ((seed ^ 0xb55a4f09) ^ (seed >>> 16)) & 0xffffffff; return seed; } In SOM Smalltalk, it looks like this: JenkinsRandom = ( ---- | seed | seed: val = ( seed := val ) "Robert Jenkins' 32 bit integer hash function." random = ( seed := ((seed + 2127912214 "0x7ed55d16") + (seed as32BitUnsignedValue << 12) as32BitSignedValue) as32BitSignedValue. seed := ((seed bitXor: 3345072700 "0xc761c23c") bitXor: (seed as32BitUnsignedValue >>> 19)) as32BitSignedValue. seed := ((seed + 374761393 "0x165667B1") + (seed as32BitUnsignedValue << 5) as32BitSignedValue) as32BitSignedValue. seed := ((seed + 3550635116 "0xd3a2646c") bitXor: (seed as32BitUnsignedValue << 9) as32BitSignedValue) as32BitSignedValue. seed := ((seed + 4251993797 "0xfd7046c5") + (seed as32BitUnsignedValue << 3) as32BitSignedValue) as32BitSignedValue. seed := ((seed bitXor: 3042594569 "0xb55a4f09") bitXor: (seed as32BitUnsignedValue >>> 16)) as32BitSignedValue. ^ seed ) ) -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

April 3, 2015

Re: [Pharo-dev] Pharo 4 Beta, first impressions

by Sven Van Caekenberghe

> On 03 Apr 2015, at 15:57, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > Date: 3 Apr 2015 15:53:56 CEST > From: Benoit St-Jean <bstjean(a)yahoo.com> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] Pharo 4 Beta, first impressions > > > Kilon, > > I can perfectly understand that "not everything has to be in the image" and that, ultimately, someone has to maintain that code. The only problem I have with the removal of that theme is that more than 55% of users are running some flavor of Windows. It's not as if someone would ask for an OS/2 or a Motif UI theme! There are *LOTS* of people on Windows still ! There is no such thing as *one* Windows look (or version), there are many: http://en.wikipedia.org/wiki/Microsoft_Windows#Usage_share We simply cannot maintain them, nor do we want to. Note that we do not maintain any other platform specific look&feels. > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > From: kilon alios <kilon.alios(a)gmail.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Sent: Friday, April 3, 2015 9:25 AM > Subject: Re: [Pharo-dev] Pharo 4 Beta, first impressions > > > > > "The point is, every piece of code needs to be written and maintained which takes time and energy from other activities." > > > I completely agree with you. I have zero issues of main pharo developers kicking out libraries that are not so much used by pharo users. Those libraries are perfectly capable of existing as third party. > > I also love the plan to make pharo modular, remove libraries from inside and make it easy to install. This way each one of us can easily make an image tailor made for his/her needs. Each pharo user is an individual with individual needs. > > Installing libraries is dead easy with the Configuration Browser , including their dependencies , just one click away. > > Of course that leaves whos going to maintain that stuff. I agree with Marcus here, "you want it in pharo , code it".The theme support in Pharo is very powerful , I know because I created my own custom blue theme and a tool to allow easy customization of theme colors with zero coding (Nireas). I expected that by now Nireas would be replaced by another way more powerful theme manager but it has not. Why ? Not because my theme manager is very good, but because the community is just too small. I love using my blue theme and fits perfect to my taste and needs ;) > > In the end no code can be more personal than the code you create. > > There is no need for everything to exist inside the image , great things can exist outside too. All it needs people who really care about pharo by coding for it. > > > > >

April 3, 2015

[pharo-project/pharo-core] ad5e24: 40594

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: ad5e24c4e2de21b16deccb51c4876f804d372e97 https://github.com/pharo-project/pharo-core/commit/ad5e24c4e2de21b16deccb51… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-03 (Fri, 03 Apr 2015) Changed paths: A Nautilus.package/extension/AbstractGroup/instance/asNautilusItemPath.st M Polymorph-Widgets.package/TickDialogWindow.class/README.md M Polymorph-Widgets.package/TickDialogWindow.class/instance/display/openInWorld.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script593.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script594.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40593.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40594.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40594 15278 Filtering on a Dynamic Group throws a DNU https://pharo.fogbugz.com/f/cases/15278 15295 TickDialogWindow open invokes not existing method https://pharo.fogbugz.com/f/cases/15295 http://files.pharo.org/image/40/40594.zip

April 3, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40594 Home: https://github.com/pharo-project/pharo-core

April 3, 2015

Re: [Pharo-dev] Pharo 4 Beta, first impressions

by Benoit St-Jean

Kilon, I can perfectly understand that "not everything has to be in the image" and that, ultimately, someone has to maintain that code.Â The only problem I have with the removal of that theme is that more than 55% of users are running some flavor of Windows.Â It's not as if someone would ask for an OS/2 or a Motif UI theme!Â There are *LOTS* of people on Windows still ! Â ----------------- Benoit St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) From: kilon alios <kilon.alios(a)gmail.com> To: Pharo Development List <pharo-dev(a)lists.pharo.org> Sent: Friday, April 3, 2015 9:25 AM Subject: Re: [Pharo-dev] Pharo 4 Beta, first impressions "The point is, every piece of code needs to be written and maintained which takes time and energy from other activities." I completely agree with you. I have zero issues of main pharo developers kicking out libraries that are not so much used by pharo users. Those libraries are perfectly capable of existing as third party. I also love the plan to make pharo modular, remove libraries from inside and make it easy to install. This way each one of us can easily make an image tailor made for his/her needs. Each pharo user is an individual with individual needs. Installing libraries is dead easy with the Configuration Browser , including their dependencies , just one click away. Of course that leaves whos going to maintain that stuff.Â I agree with Marcus here, "you want it in pharo , code it".The theme support in Pharo is very powerful , I know because I created my own custom blue theme and a tool to allow easy customization of theme colors with zero coding (Nireas). I expected that by now Nireas would be replaced by another way more powerful theme manager but it has not. Why ? Not because my theme manager is very good, but because the community is just too small. I love using my blue theme and fits perfect to my taste and needs ;) In the end no code can be more personal than the code you create. There is no need for everything to exist inside the image , great things can exist outside too. All it needs people who really care about pharo by coding for it.

April 3, 2015

Re: [Pharo-dev] Pharo 4 Beta, first impressions

by Sven Van Caekenberghe

> On 03 Apr 2015, at 14:11, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > 2) Am I the only one annoyed by the fact that the Collection class still holds on to 2 class variables (one of them being an instance of Random, the other a mutex) for the sole purpose of accommodating the #atRandom & #atRandom: methods ? Even worse, the Integer class' implementation of #atRandom references the Collection class to use that random instance! In other words, Integer>>#atRandom --> Collection>>#randomForPicking --> Random ! I've always been a fan of the "mind your own business" approach. Wouldn't it make a lot more sense to have the Random class provide a default instance (a singleton) whenever other classes need such an object instead of crippling the code with class variables and singleton instance all over the place? This always annoyed me big time. Not just for what you said, but also because the access protection should not be there at all.

April 3, 2015

Re: [Pharo-dev] In Debugger: block variables nil

by Peter UhnÃ¡k

Hi Stefan, it is a know issue ( https://pharo.fogbugz.com/f/cases/15174/, https://pharo.fogbugz.com/f/cases/14606/ ) and it is currently being worked on. Peter On Fri, Apr 3, 2015 at 3:19 PM, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > While debugging the beautiful method below, I noticed that the debugger > shows data1 to be `nil`, while it actually has a proper value. That is, the > pane on the right bottom shows the wrong value. > When inspecting `data1` within the source code pane, it is correctly shown > in the inspector. > > Is this a known issue? Should I file a bug? > > Best regards > Stefan > > createWorker: identity priority: priority work: work state: state > | data | > data := RichWorkerTaskDataRecord create. > self > createTask: identity > priority: priority > work: work > state: state > function: > [:work1 :word | | data1 | > data1 := word. > RichObject NoWork == work1 > ifTrue: [self wait] > ifFalse: > [data1 destination: (RichObject HandlerA = data1 > destination > ifTrue: [RichObject HandlerB] > ifFalse: [RichObject HandlerA]). > work1 identity: data1 destination. > work1 datum: 1. > 1 to: 4 do: [ :i | > data1 count: data1 count + 1. > data1 count > 26 ifTrue: [data1 count: 1]. > work1 data at: i put: $A asInteger + data1 count - > 1]. > self queuePacket: work1]] > data: data > > > -- > Stefan Marr > INRIA Lille - Nord Europe > http://stefan-marr.de/research/ > > > > >

April 3, 2015

Re: [Pharo-dev] Pharo 4 Beta, first impressions

by kilon alios

"The point is, every piece of code needs to be written and maintained which takes time and energy from other activities." I completely agree with you. I have zero issues of main pharo developers kicking out libraries that are not so much used by pharo users. Those libraries are perfectly capable of existing as third party. I also love the plan to make pharo modular, remove libraries from inside and make it easy to install. This way each one of us can easily make an image tailor made for his/her needs. Each pharo user is an individual with individual needs. Installing libraries is dead easy with the Configuration Browser , including their dependencies , just one click away. Of course that leaves whos going to maintain that stuff. I agree with Marcus here, "you want it in pharo , code it".The theme support in Pharo is very powerful , I know because I created my own custom blue theme and a tool to allow easy customization of theme colors with zero coding (Nireas). I expected that by now Nireas would be replaced by another way more powerful theme manager but it has not. Why ? Not because my theme manager is very good, but because the community is just too small. I love using my blue theme and fits perfect to my taste and needs ;) In the end no code can be more personal than the code you create. There is no need for everything to exist inside the image , great things can exist outside too. All it needs people who really care about pharo by coding for it.

April 3, 2015

In Debugger: block variables nil

by Stefan Marr

Hi: While debugging the beautiful method below, I noticed that the debugger shows data1 to be `nil`, while it actually has a proper value. That is, the pane on the right bottom shows the wrong value. When inspecting `data1` within the source code pane, it is correctly shown in the inspector. Is this a known issue? Should I file a bug? Best regards Stefan createWorker: identity priority: priority work: work state: state | data | data := RichWorkerTaskDataRecord create. self createTask: identity priority: priority work: work state: state function: [:work1 :word | | data1 | data1 := word. RichObject NoWork == work1 ifTrue: [self wait] ifFalse: [data1 destination: (RichObject HandlerA = data1 destination ifTrue: [RichObject HandlerB] ifFalse: [RichObject HandlerA]). work1 identity: data1 destination. work1 datum: 1. 1 to: 4 do: [ :i | data1 count: data1 count + 1. data1 count > 26 ifTrue: [data1 count: 1]. work1 data at: i put: $A asInteger + data1 count - 1]. self queuePacket: work1]] data: data -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/

April 3, 2015