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

[Pharo 8.0] Build #240: 3241-install-probot-to-suggest-us-to-not-forget-reviews

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

There is a new Pharo build available! The status of the build #240 was: SUCCESS. The Pull Request #3248 was integrated: "3241-install-probot-to-suggest-us-to-not-forget-reviews" Pull request url: https://github.com/pharo-project/pharo/pull/3248 Issue Url: https://github.com/pharo-project/pharo/issues/3241 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 26, 2019

[Pharo 8.0] Build #239: 2590-We-can-get-two-times-the-mouseEntermouseLeave-event-when-subscribing-to-the-eventHandler-of-a-Morph

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

There is a new Pharo build available! The status of the build #239 was: SUCCESS. The Pull Request #2724 was integrated: "2590-We-can-get-two-times-the-mouseEntermouseLeave-event-when-subscribing-to-the-eventHandler-of-a-Morph" Pull request url: https://github.com/pharo-project/pharo/pull/2724 Issue Url: https://github.com/pharo-project/pharo/issues/2590 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 26, 2019

[Pharo 8.0] Build #238: 3217-copy-class-do-not-copy-class-side-instanceVariableNames

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

There is a new Pharo build available! The status of the build #238 was: SUCCESS. The Pull Request #3230 was integrated: "3217-copy-class-do-not-copy-class-side-instanceVariableNames" Pull request url: https://github.com/pharo-project/pharo/pull/3230 Issue Url: https://github.com/pharo-project/pharo/issues/3217 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 26, 2019

Re: [Pharo-dev] FloatArray

by ducasse

Thanks nicolas. We will discuss this during the sprint tomorrow. > On 25 Apr 2019, at 22:43, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > I've just published a new ConfigurationOfSmallapack > > Currently, there is one test failing because I did not finish the support of LegacyFFI for invoking methods with more than 15 arguments (see below). > The other tests are passing, so you may try it now. > > gory details: > The failing test requires the Opal Compiler to generate fallback code for invoking primitive 117 (ExternalFunction invokeWithArguments:) under the hood... > Old Compiler workaround was hackish, and is extremely complex to implement in cleaner Opal architecture > (Old compiler enabled mixing AST rewrite/code generation phase without a problem) > The plan was either to enhance primitive 120 to handle the case of many arguments passed through a single array... > Or to switch to UnifiedFFI (but even there, I don't remember if invoking primitive 117 was that straight forward...) > > Le jeu. 25 avr. 2019 Ã 20:16, Jimmie Houchin <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> a Ã©crit : > Thanks. > > I appreciate your working to make this happen. No pressure from me on time. I am blessed that you are contributing this to the community and that I can benefit from your labors. At your convenience. > > I look forward to using Smallapack when available. I am thrilled to be able to stay with Pharo and not have to use Python/Numpy. :) > Thanks. > > Jimmie > > On 4/25/19 12:38 PM, Nicolas Cellier wrote: >> Hi Jimmie, >> The Metacello Configuration is not ready for Pharo7. >> I have succeeded in loading Smallapack yesterday without Metacello, and could run some of the tests. >> I had to modify a few methods because of Pharo refactorings, and there is still some work to make it fully operational. >> When ready, I'll update the Metacello configuration and keep you informed. >> >> Le jeu. 25 avr. 2019 Ã 19:06, Jimmie Houchin <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> a Ã©crit : >> When I attempt to install via Metacello in Pharo 7, I get the following warning. >> >> This package depends on the following classes: >> Parser >> MessageAsTempNode >> Compiler >> MessageNode >> >> I do not know how to proceed from there. Any help greatly appreciated. >> Thanks. >> >> Jimmie >> >> On 4/24/19 12:20 AM, Nicolas Cellier wrote: >>> Hi, >>> I recommand inquiring about Smallapack, the Smalltalk interface to LAPACK, on squeaksource.com <http://squeaksource.com/> or github. You'll get the speed of numpy. There is a Metacello configuration. I have not checked the port on current >>> Pharo, but I can reactivate if there is some interest. >>> >>> Le mer. 24 avr. 2019 Ã 05:55, Jimmie Houchin <jlhouchin(a)gmail.com <mailto:jlhouchin@gmail.com>> a Ã©crit : >>> I just recently discovered FloatArray by accident. >>> >>> I was close to having to use Python/Numpy due to considerable >>> performance differences. Performance is very important. >>> >>> In one of my test using a 212000 item array of floats and doing a sum on >>> each iteration through the array Pharo was taking 17 minutes verses >>> Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 >>> seconds. That is acceptable. >>> >>> However when looking at the FloatArray comment it says it uses 32bit >>> floats. I need 64bit. I don't even know where to look to create 64bit >>> FloatArrays. I am surprised that they didn't get converted when moving >>> to 64bit Pharo. >>> >>> Would I need to change VM source? Compile a new VM and create image side >>> classes? I have not messed with VM in years. I do not know where the >>> FloatArray plugin would be. >>> >>> Any pointers would be a great help. If this needs to be on the vm-dev >>> list I can move it there. >>> >>> Thanks. >>> >>> Jimmie >>> >>>

April 25, 2019

Re: [Pharo-dev] FloatArray

by Nicolas Cellier

I've just published a new ConfigurationOfSmallapack Currently, there is one test failing because I did not finish the support of LegacyFFI for invoking methods with more than 15 arguments (see below). The other tests are passing, so you may try it now. gory details: The failing test requires the Opal Compiler to generate fallback code for invoking primitive 117 (ExternalFunction invokeWithArguments:) under the hood... Old Compiler workaround was hackish, and is extremely complex to implement in cleaner Opal architecture (Old compiler enabled mixing AST rewrite/code generation phase without a problem) The plan was either to enhance primitive 120 to handle the case of many arguments passed through a single array... Or to switch to UnifiedFFI (but even there, I don't remember if invoking primitive 117 was that straight forward...) Le jeu. 25 avr. 2019 Ã 20:16, Jimmie Houchin <jlhouchin(a)gmail.com> a Ã©crit : > Thanks. > > I appreciate your working to make this happen. No pressure from me on > time. I am blessed that you are contributing this to the community and that > I can benefit from your labors. At your convenience. > > I look forward to using Smallapack when available. I am thrilled to be > able to stay with Pharo and not have to use Python/Numpy. :) > > Thanks. > > Jimmie > > > On 4/25/19 12:38 PM, Nicolas Cellier wrote: > > Hi Jimmie, > The Metacello Configuration is not ready for Pharo7. > I have succeeded in loading Smallapack yesterday without Metacello, and > could run some of the tests. > I had to modify a few methods because of Pharo refactorings, and there is > still some work to make it fully operational. > When ready, I'll update the Metacello configuration and keep you informed. > > Le jeu. 25 avr. 2019 Ã 19:06, Jimmie Houchin <jlhouchin(a)gmail.com> a > Ã©crit : > >> When I attempt to install via Metacello in Pharo 7, I get the following >> warning. >> >> This package depends on the following classes: >> Parser >> MessageAsTempNode >> Compiler >> MessageNode >> >> >> I do not know how to proceed from there. Any help greatly appreciated. >> >> Thanks. >> >> Jimmie >> >> >> On 4/24/19 12:20 AM, Nicolas Cellier wrote: >> >> Hi, >> I recommand inquiring about Smallapack, the Smalltalk interface to >> LAPACK, on squeaksource.com or github. You'll get the speed of numpy. >> There is a Metacello configuration. I have not checked the port on current >> Pharo, but I can reactivate if there is some interest. >> >> Le mer. 24 avr. 2019 Ã 05:55, Jimmie Houchin <jlhouchin(a)gmail.com> a >> Ã©crit : >> >>> I just recently discovered FloatArray by accident. >>> >>> I was close to having to use Python/Numpy due to considerable >>> performance differences. Performance is very important. >>> >>> In one of my test using a 212000 item array of floats and doing a sum on >>> each iteration through the array Pharo was taking 17 minutes verses >>> Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 >>> seconds. That is acceptable. >>> >>> However when looking at the FloatArray comment it says it uses 32bit >>> floats. I need 64bit. I don't even know where to look to create 64bit >>> FloatArrays. I am surprised that they didn't get converted when moving >>> to 64bit Pharo. >>> >>> Would I need to change VM source? Compile a new VM and create image side >>> classes? I have not messed with VM in years. I do not know where the >>> FloatArray plugin would be. >>> >>> Any pointers would be a great help. If this needs to be on the vm-dev >>> list I can move it there. >>> >>> Thanks. >>> >>> Jimmie >>> >>> >>>

April 25, 2019

Re: [Pharo-dev] FloatArray

by Jimmie Houchin

Thanks. I appreciate your working to make this happen. No pressure from me on time. I am blessed that you are contributing this to the community and that I can benefit from your labors. At your convenience. I look forward to using Smallapack when available. I am thrilled to be able to stay with Pharo and not have to use Python/Numpy. :) Thanks. Jimmie On 4/25/19 12:38 PM, Nicolas Cellier wrote: > Hi Jimmie, > The Metacello Configuration is not ready for Pharo7. > I have succeeded in loading Smallapack yesterday without Metacello, > and could run some of the tests. > I had to modify a few methods because of Pharo refactorings, and there > is still some work to make it fully operational. > When ready, I'll update the Metacello configuration and keep you informed. > > LeÂ jeu. 25 avr. 2019 Ã Â 19:06, Jimmie Houchin <jlhouchin(a)gmail.com > <mailto:jlhouchin@gmail.com>> a Ã©critÂ : > > When I attempt to install via Metacello in Pharo 7, I get the > following warning. > > This package depends on the following classes: > Â Parser > Â MessageAsTempNode > Â Compiler > Â MessageNode > > > I do not know how to proceed from there. Any help greatly appreciated. > > Thanks. > > Jimmie > > > On 4/24/19 12:20 AM, Nicolas Cellier wrote: >> Hi, >> I recommand inquiring about Smallapack, the Smalltalk interface >> to LAPACK, on squeaksource.com <http://squeaksource.com> or >> github. You'll get the speed of numpy. There is a Metacello >> configuration. I have not checked the port on current >> Pharo, but I can reactivate if there is some interest. >> >> Le mer. 24 avr. 2019 Ã 05:55, Jimmie Houchin <jlhouchin(a)gmail.com >> <mailto:jlhouchin@gmail.com>> a Ã©critÂ : >> >> I just recently discovered FloatArray by accident. >> >> I was close to having to use Python/Numpy due to considerable >> performance differences. Performance is very important. >> >> In one of my test using a 212000 item array of floats and >> doing a sum on >> each iteration through the array Pharo was taking 17 minutes >> verses >> Python/Numpy taking 20 seconds. Using FloatArray closes the >> gap to 40 >> seconds. That is acceptable. >> >> However when looking at the FloatArray comment it says it >> uses 32bit >> floats. I need 64bit. I don't even know where to look to >> create 64bit >> FloatArrays. I am surprised that they didn't get converted >> when moving >> to 64bit Pharo. >> >> Would I need to change VM source? Compile a new VM and create >> image side >> classes? I have not messed with VM in years. I do not know >> where the >> FloatArray plugin would be. >> >> Any pointers would be a great help. If this needs to be on >> the vm-dev >> list I can move it there. >> >> Thanks. >> >> Jimmie >> >>

April 25, 2019

[Pharo 8.0] Build #237: newbutton2

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

There is a new Pharo build available! The status of the build #237 was: SUCCESS. The Pull Request #3232 was integrated: "newbutton2" Pull request url: https://github.com/pharo-project/pharo/pull/3232 Issue Url: https://github.com/pharo-project/pharo/issues/newbutton2 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 25, 2019

Re: [Pharo-dev] FloatArray

by Nicolas Cellier

Hi Jimmie, The Metacello Configuration is not ready for Pharo7. I have succeeded in loading Smallapack yesterday without Metacello, and could run some of the tests. I had to modify a few methods because of Pharo refactorings, and there is still some work to make it fully operational. When ready, I'll update the Metacello configuration and keep you informed. Le jeu. 25 avr. 2019 Ã 19:06, Jimmie Houchin <jlhouchin(a)gmail.com> a Ã©crit : > When I attempt to install via Metacello in Pharo 7, I get the following > warning. > > This package depends on the following classes: > Parser > MessageAsTempNode > Compiler > MessageNode > > > I do not know how to proceed from there. Any help greatly appreciated. > > Thanks. > > Jimmie > > > On 4/24/19 12:20 AM, Nicolas Cellier wrote: > > Hi, > I recommand inquiring about Smallapack, the Smalltalk interface to LAPACK, on > squeaksource.com or github. You'll get the speed of numpy. There is a > Metacello configuration. I have not checked the port on current > Pharo, but I can reactivate if there is some interest. > > Le mer. 24 avr. 2019 Ã 05:55, Jimmie Houchin <jlhouchin(a)gmail.com> a > Ã©crit : > >> I just recently discovered FloatArray by accident. >> >> I was close to having to use Python/Numpy due to considerable >> performance differences. Performance is very important. >> >> In one of my test using a 212000 item array of floats and doing a sum on >> each iteration through the array Pharo was taking 17 minutes verses >> Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 >> seconds. That is acceptable. >> >> However when looking at the FloatArray comment it says it uses 32bit >> floats. I need 64bit. I don't even know where to look to create 64bit >> FloatArrays. I am surprised that they didn't get converted when moving >> to 64bit Pharo. >> >> Would I need to change VM source? Compile a new VM and create image side >> classes? I have not messed with VM in years. I do not know where the >> FloatArray plugin would be. >> >> Any pointers would be a great help. If this needs to be on the vm-dev >> list I can move it there. >> >> Thanks. >> >> Jimmie >> >> >>

April 25, 2019

Re: [Pharo-dev] FloatArray

by Jimmie Houchin

When I attempt to install via Metacello in Pharo 7, I get the following warning. This package depends on the following classes: Â Parser Â MessageAsTempNode Â Compiler Â MessageNode I do not know how to proceed from there. Any help greatly appreciated. Thanks. Jimmie On 4/24/19 12:20 AM, Nicolas Cellier wrote: > Hi, > I recommand inquiring about Smallapack, the Smalltalk interface to > LAPACK, on squeaksource.com <http://squeaksource.com> or github. > You'll get the speed of numpy. There is a Metacello configuration. I > have not checked the port on current > Pharo, but I can reactivate if there is some interest. > > Le mer. 24 avr. 2019 Ã 05:55, Jimmie Houchin <jlhouchin(a)gmail.com > <mailto:jlhouchin@gmail.com>> a Ã©critÂ : > > I just recently discovered FloatArray by accident. > > I was close to having to use Python/Numpy due to considerable > performance differences. Performance is very important. > > In one of my test using a 212000 item array of floats and doing a > sum on > each iteration through the array Pharo was taking 17 minutes verses > Python/Numpy taking 20 seconds. Using FloatArray closes the gap to 40 > seconds. That is acceptable. > > However when looking at the FloatArray comment it says it uses 32bit > floats. I need 64bit. I don't even know where to look to create 64bit > FloatArrays. I am surprised that they didn't get converted when > moving > to 64bit Pharo. > > Would I need to change VM source? Compile a new VM and create > image side > classes? I have not messed with VM in years. I do not know where the > FloatArray plugin would be. > > Any pointers would be a great help. If this needs to be on the vm-dev > list I can move it there. > > Thanks. > > Jimmie > >

April 25, 2019

[Pharo 8.0] Build #236: Exporting MCZ from the BaselineOfMetacello

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

There is a new Pharo build available! The status of the build #236 was: SUCCESS. The Pull Request #3215 was integrated: "Exporting MCZ from the BaselineOfMetacello" Pull request url: https://github.com/pharo-project/pharo/pull/3215 Issue Url: https://github.com/pharo-project/pharo/issues/exporting Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 25, 2019