November 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Mariano Martinez Peck

On Fri, Nov 9, 2018 at 11:15 AM Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi, > > Le 9 nov. 2018 Ã 14:11, Mariano Martinez Peck <marianopeck(a)gmail.com> a > Ã©crit : > > > > On Fri, Nov 9, 2018, 10:06 Christophe Demarey <christophe.demarey(a)inria.fr > wrote: > >> Hi Mariano, >> >> Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com> a >> Ã©crit : >> > >> > Hi All, >> > >> > I am having this same problem with the #fileDescriptorType: in a >> PharoLauncher 1.4.6 64 bits trying to launch a >> Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 >> Bit). >> > >> > Any ideas? >> >> It is because your pharo 70 vm is too old. >> You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in >> pharo/vm/private) and it should work. >> >> >> >> > Hi Christophe, > > Thanks for the workaround. But let me ask.. Wasn't one of the launcher > purposes to automatically download the necessary correct VM for the image > you are creating? To avoid this exact kind of issue? > > > Launcher magic has its boundaries. > The information available to the launcher to determine the appropriate VM > to run an image is: > - the image format number (encoded in the image header) > - the pharo version (system version) of the image (need to run the image > to know that information). > > In your case, you have an image with the same image format number, same > pharo version (7.0) but with incompatible changes requiring a new VM. Pharo > Launcher has no way to get this information. > This problem only happens with moving Pharo versions : the development > version. > > The best option would be to encode the Pharo version as a semantic version > in the header of the image file but it requires a lot of changes. > > For now, to work around the problem, I will add a windows to easily update > the VMs from the launcher UI. > > OK, I understand. Thanks for the explanation Christophe. I can also confirm that the workaround of removing by hand the VM directory did fix my issue. Thanks! -- Mariano http://marianopeck.wordpress.com

Nov. 9, 2018

Re: [Pharo-dev] WELL512 PRNG

by Serge Stinckwich

Can you contribute your code to PolyMath: https://github.com/PolyMathOrg/PolyMath We have other RNGs available. Thank you. On Fri, Nov 9, 2018 at 3:23 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > By accident I came across a pseudo random number generator that I never > heard off before. It is supposed to be pretty good and had a very simple > implementation. So I ported it to Pharo. > > <class comment> > > I am RandomWELL512, a random number generator. > > I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed > long-period linear) with a 512 bit state. > > https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear > http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf > > Implementation algorithm (See #nextUInt32) > > http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris > Lomont, www.lomont.org) > > Usage > > RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] > ]. > > RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) > collect: [ :i | r next ] ]. > > RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 > ] ]. > > RandomWELL512 new in: [ :random | | count all | > random useUnixRandomGeneratorSeed. > count := 1024 * 1024. > all := Array new: count streamContents: [ :out | > count timesRepeat: [ out nextPut: random next ] ]. > { all min. all max. all average. all stdev } ]. > > [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] > ] timeToRun. > > Note that you should create one instance, seed it properly, and keep using > it. > > </class comment> > > It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I > compared the output with a fixed initial state to the C code that I started > from and I got the same numbers. Maybe some people find this interesting. > > I attached a file out. > > Sven > > > > -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Nov. 9, 2018

WELL512 PRNG

by Sven Van Caekenberghe

Hi, By accident I came across a pseudo random number generator that I never heard off before. It is supposed to be pretty good and had a very simple implementation. So I ported it to Pharo. <class comment> I am RandomWELL512, a random number generator. I use the PRNG (Pseudo Randon Number Generator) WELL (Well equidistributed long-period linear) with a 512 bit state. https://en.wikipedia.org/wiki/Well_equidistributed_long-period_linear http://www.iro.umontreal.ca/~lecuyer/myftp/papers/wellrng.pdf Implementation algorithm (See #nextUInt32) http://www.lomont.org/Math/Papers/2008/Lomont_PRNG_2008.pdf (Chris Lomont, www.lomont.org) Usage RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextUInt32 ] ]. RandomWELL512 new useUnixRandomGeneratorSeed; in: [ :r | (1 to: 10) collect: [ :i | r next ] ]. RandomWELL512 new in: [ :r | (1 to: 10) collect: [ :i | r nextInt: 1000 ] ]. RandomWELL512 new in: [ :random | | count all | random useUnixRandomGeneratorSeed. count := 1024 * 1024. all := Array new: count streamContents: [ :out | count timesRepeat: [ out nextPut: random next ] ]. { all min. all max. all average. all stdev } ]. [ RandomWELL512 new in: [ :random | 1 to: 1e6 do: [ :i | random next ] ] ] timeToRun. Note that you should create one instance, seed it properly, and keep using it. </class comment> It is acceptably fast, generating 1M [0,1) Floats in about 0.1s. I compared the output with a fixed initial state to the C code that I started from and I got the same numbers. Maybe some people find this interesting. I attached a file out. Sven

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Christophe Demarey

Hi, > Le 9 nov. 2018 Ã 14:11, Mariano Martinez Peck <marianopeck(a)gmail.com> a Ã©crit : > > > > On Fri, Nov 9, 2018, 10:06 Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr> wrote: > Hi Mariano, > > Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> a Ã©crit : > > > > Hi All, > > > > I am having this same problem with the #fileDescriptorType: in a PharoLauncher 1.4.6 64 bits trying to launch a Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 Bit). > > > > Any ideas? > > It is because your pharo 70 vm is too old. > You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in pharo/vm/private) and it should work. > > > > > Hi Christophe, > > Thanks for the workaround. But let me ask.. Wasn't one of the launcher purposes to automatically download the necessary correct VM for the image you are creating? To avoid this exact kind of issue? Launcher magic has its boundaries. The information available to the launcher to determine the appropriate VM to run an image is: - the image format number (encoded in the image header) - the pharo version (system version) of the image (need to run the image to know that information). In your case, you have an image with the same image format number, same pharo version (7.0) but with incompatible changes requiring a new VM. Pharo Launcher has no way to get this information. This problem only happens with moving Pharo versions : the development version. The best option would be to encode the Pharo version as a semantic version in the header of the image file but it requires a lot of changes. For now, to work around the problem, I will add a windows to easily update the VMs from the launcher UI.

Nov. 9, 2018

[Pharo 7.0-dev] Build #1374: 22650-add-Operations-as-Reifications

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1374 was: SUCCESS. The Pull Request #1961 was integrated: "22650-add-Operations-as-Reifications" Pull request url: https://github.com/pharo-project/pharo/pull/1961 Issue Url: https://pharo.fogbugz.com/f/cases/22650 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Mariano Martinez Peck

On Fri, Nov 9, 2018, 10:06 Christophe Demarey <christophe.demarey(a)inria.fr wrote: > Hi Mariano, > > Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com> a > Ã©crit : > > > > Hi All, > > > > I am having this same problem with the #fileDescriptorType: in a > PharoLauncher 1.4.6 64 bits trying to launch a > Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 > Bit). > > > > Any ideas? > > It is because your pharo 70 vm is too old. > You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in > pharo/vm/private) and it should work. > > > > Hi Christophe, Thanks for the workaround. But let me ask.. Wasn't one of the launcher purposes to automatically download the necessary correct VM for the image you are creating? To avoid this exact kind of issue? Thanks! > > Cheers, > Christophe. >

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Christophe Demarey

Hi Mariano, Le 8 nov. 2018 Ã 20:47, Mariano Martinez Peck <marianopeck(a)gmail.com> a Ã©crit : > > Hi All, > > I am having this same problem with the #fileDescriptorType: in a PharoLauncher 1.4.6 64 bits trying to launch a Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 Bit). > > Any ideas? It is because your pharo 70 vm is too old. You can drop the pharo/vm folder (or just 70 vm in pharo/vm and in pharo/vm/private) and it should work. Cheers, Christophe.

Nov. 9, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Mariano Martinez Peck

Hi All, I am having this same problem with the #fileDescriptorType: in a PharoLauncher 1.4.6 64 bits trying to launch a Pharo-7.0.0+rc1.build.1373.sha.c50749c3452952c3572527bed9ea18ec8c674855 (64 Bit). Any ideas? Thanks, On Thu, Aug 23, 2018 at 12:16 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > demarey wrote > > I just published a new version of the launcher > > Thanks! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > > -- Mariano http://marianopeck.wordpress.com

Nov. 8, 2018

[Pharo 7.0-dev] Build #1373: 22639-Clean-ComposablePresenter-icon-API

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1373 was: SUCCESS. The Pull Request #1959 was integrated: "22639-Clean-ComposablePresenter-icon-API" Pull request url: https://github.com/pharo-project/pharo/pull/1959 Issue Url: https://pharo.fogbugz.com/f/cases/22639 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 8, 2018

glamorous toolkit - moldable method coder

by Tudor Girba

Hi, We design the Glamorous Toolkit to enable moldable development. This is a new take on programming that is predicated on the idea that tools must adapt to the context of the software system in order to be effective. Until now, we mainly applied moldability to how we inspect/debug/search existing code and objects. The first incarnation of GT, the tools that are present in the Pharo distribution, already showed how moldable development can provide dramatic productivity gains, especially when combined with examples. To make the experience complete, more recently we started to build moldability into Coder, the new set of tools for creating code. The first tool we created is Method Coder, an editor for a single method. This is a working editor that has multiple new features, one of which being that it can be collapsed to only see the method pattern (header), and that the body is editable without affecting the method pattern. This editor is versatile and can be used in various places, such as class coder or a search: https://twitter.com/feenkcom/status/1058003761262743552 Yesterday, we reached a new milestone. In the example below we see how adding/removing <gtExample> to a method changes the shape of the method Coder dynamically without requiring a save. In our case, the changes affect: the example status label, the in-place example expanding toggle, and the run button. https://twitter.com/feenkcom/status/1060290294749560833 This just an example that is specific to the examples engine, but it shows how typing can be linked live to all details that make the surrounding tool. Of course, the mechanism behind the scene is available for you to adapt the editor to your code. This is a whole new uncharted world, and we think there is a great deal of potential in this area. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

Nov. 8, 2018