Re: [Pharo-dev] OpalCompiler evaluate speed

Could not we do a task force to clean the compiler? We need a better infrastructure for the tool. Stef On Fri, Nov 24, 2017 at 11:35 AM, Nicolas Cellier wrote: > > > 2017-11-24 10:54 GMT+01:00 Marcus Denker : >> >> >> >> > On 23 Nov

[Pharo-dev] [Pharo 7.0-dev] Build #328: 20756-Secondary-selections-are-dark-after-switch-to-the-white-theme-in-Pharo-7

There is a new Pharo build available! The status of the build #328 was: SUCCESS. The Pull Request #540 was integrated: "20756-Secondary-selections-are-dark-after-switch-to-the-white-theme-in-Pharo-7" Pull request url: https://github.com/pharo-project/pharo/pull/540 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #327: 20729-Monticello-history-browser-should-enable-diffing-with-parent

There is a new Pharo build available! The status of the build #327 was: SUCCESS. The Pull Request #513 was integrated: "20729-Monticello-history-browser-should-enable-diffing-with-parent" Pull request url: https://github.com/pharo-project/pharo/pull/513 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #326: 20753-testStoreOn-using-the-compiler-should-have-a-more-descriptive-name

There is a new Pharo build available! The status of the build #326 was: SUCCESS. The Pull Request #534 was integrated: "20753-testStoreOn-using-the-compiler-should-have-a-more-descriptive-name" Pull request url: https://github.com/pharo-project/pharo/pull/534 Issue Url:

[Pharo-dev] [Pharo 7.0-dev] Build #325: 20754-make-longer-timeout-for-some-randomly-failing-tests

There is a new Pharo build available! The status of the build #325 was: SUCCESS. The Pull Request #536 was integrated: "20754-make-longer-timeout-for-some-randomly-failing-tests" Pull request url: https://github.com/pharo-project/pharo/pull/536 Issue Url:

Re: [Pharo-dev] [Pharo-users] I love the launcher!!!!

Hi Herby, normally people use different images for their different projects, different versions, trying things, etc. Which means we end up with many locations on disk, and it can be hard to track. So PharoLauncher is a nice tool where you can download fresh image just by clicking, and you see the

Re: [Pharo-dev] Bloc Tutorial Feedback

Aliaksei Syrel wrote > you probably have a shared repo of bloc > somewhere on your machine. > The tutorial's code is up-to date :) Aha! Yes, okay. I will (hopefully) get used to that gotcha soon!! - Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

[Pharo-dev] [Pharo 7.0-dev] Build #324: 20749-All-packages-need-to-be-reexported

There is a new Pharo build available! The status of the build #324 was: SUCCESS. The Pull Request #531 was integrated: "20749-All-packages-need-to-be-reexported" Pull request url: https://github.com/pharo-project/pharo/pull/531 Issue Url: https://pharo.fogbugz.com/f/cases/20749 Build

Re: [Pharo-dev] OpalCompiler evaluate speed

2017-11-24 10:54 GMT+01:00 Marcus Denker : > > > > On 23 Nov 2017, at 23:37, Clément Bera wrote: > > > > Hi Nicolas. > > > > Just some comments: > > > > Another thing you can try is to remove the allocation of Opal's IR. It > seems people use the

[Pharo-dev] [Pharo 7.0-dev] Build #323: 20549-CompiledMethod-isTestMethod-should-invert-the-query-clauses

There is a new Pharo build available! The status of the build #323 was: SUCCESS. The Pull Request #523 was integrated: "20549-CompiledMethod-isTestMethod-should-invert-the-query-clauses" Pull request url: https://github.com/pharo-project/pharo/pull/523 Issue Url:

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

Well said! Doru > On Nov 23, 2017, at 8:53 PM, Torsten Bergmann wrote: > > What is not visible in the list are the many enhancements happening also on > Calypso, Bloc, > Grease and many many others. > > Nonetheless the core image still needs love from more people. Remember

Re: [Pharo-dev] OpalCompiler evaluate speed

> On 23 Nov 2017, at 23:37, Clément Bera wrote: > > Hi Nicolas. > > Just some comments: > > Another thing you can try is to remove the allocation of Opal's IR. It seems > people use the IR only through the IRBuilder, so the API can be kept but it > can generate

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

In the VM primitiveSlotAt: / at:Put: mean access to any field (pointer or non pointer, sorry for the confusion Marcus earlier on) of an object. The primitive in the image can be named fieldAt:/fieldAt:put: if it makes more sense for Pharo. #[0] slotAt: 1 => 0 #(#a) slotAt: 1 => #a 0@2 slotAt: 1

Re: [Pharo-dev] Problem with primitive instVarAt: / instVarAt:put:, what should we do ?

> On 24 Nov 2017, at 00:21, Clément Bera wrote: > > > > On Fri, Nov 24, 2017 at 12:00 AM, Stephane Ducasse > wrote: > Did you talk with marcus? > > I don't understand the connection between slots and this

Re: [Pharo-dev] OpalCompiler evaluate speed

> On 22 Nov 2017, at 21:14, Stephane Ducasse wrote: > > Thanks this is good. > I think that Opal deserves more energy. > We are busy right now. Now marcus will certainly be interested. Yes, sadly I am over capacity. I can not react (or even read) every email send to

Re: [Pharo-dev] OpalCompiler evaluate speed

2017-11-23 23:37 GMT+01:00 Clément Bera : > Hi Nicolas. > > Just some comments: > > Another thing you can try is to remove the allocation of Opal's IR. It > seems people use the IR only through the IRBuilder, so the API can be kept > but it can generate directly bytecode

Re: [Pharo-dev] Bloc Tutorial Feedback

Hi Sean, That is awesome, thank you! :) - The booklet reached from the GH readme seems out of sync with Bloc. I had > to alter a lot of the animations from the loaded code e.g. > BlTransformAnimation did not exist (I used BlScaleAnimation instead), > animations didn't understand #absolute, `