May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Frank Shearar

Why does ifTrue: use a compile-time transformation? There are LOTS of places where the Compiler (I can't speak for Opal, but it's almost certainly true of Pharo's Compiler unless you've already rewritten the whole thing before Opal) does all manner of code transformations. As for why, and what benchmarks, drop Josh Gargus or Ron Teitelbaum a mail. This stuff landed in Squeak via Croquet. frank On 22 May 2013 06:35, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Why Future required compiler changes? > What problem to implement #future message as any other method? > If it is about performance can you explain why basic implementation should > have bad speed? And what benchmarks was used to verify it? > > 2013/5/22 David T. Lewis <lewis(a)mail.msen.com> > >> On Mon, May 20, 2013 at 06:26:04PM +0200, Marcus Denker wrote: >> > >> > No, I know nothing about the Future implementation in Squeak? but >> > a Future node in the AST sounds extremely strange. >> >> I think that the background may be found in this thread: >> >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-December/142111… >> >> Dave >> >> >

May 22, 2013

Re: [Pharo-dev] WhatsUp from: 2013-05-20 until: 2013-05-31

by Christophe Demarey

Le 20 mai 2013 Ã 07:00, seaside(a)rmod.lille.inria.fr a Ã©crit : > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: Work on Metacello with Dale : - to include Pharo2 and Pharo3 as platforms to test on travis (Metacello is tested with travis CI) - to get MetacelloPreview working on Pharo2 and Pharo3 : we still need some work but not so far! ************************************************************************************** Results for #('BaselineOfMetacello') Test Suite 737 run, 722 passes, 0 skipped, 0 expected failures, 0 failures, 7 errors, 8 unexpected passes ************************************************************************************** > ### What's next, until 2013-05-31 (*): Include MetacelloPreview as default Metacello version in Pharo3 Get back on Versionner to use MetacelloPreview

May 22, 2013

Re: [Pharo-dev] Removing a package from Smalltalkhub

by Serge Stinckwich

Removing a package is nice, but I would like to delete project also. At the moment, I could not delete projects from a team. Thank you. On Tue, May 21, 2013 at 2:53 PM, roberto.minelli(a)usi.ch <roberto.minelli(a)usi.ch> wrote: > Hi, > > I was wondering if and how can I delete a package from Smalltalkhub. > > Thanks in avance, > R > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 2 regressions found. OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueEffect OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueValue

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 2 regressions found. OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueEffect OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueValue

May 22, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 2 regressions found. OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueEffect OpalCompiler.Tests.Misc.MustBeBooleanTests.testIfTrueValue

May 22, 2013

[update 3.0] #30154

by Marcus Denker

May 22, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Denis Kudriashov

Why Future required compiler changes? What problem to implement #future message as any other method? If it is about performance can you explain why basic implementation should have bad speed? And what benchmarks was used to verify it? 2013/5/22 David T. Lewis <lewis(a)mail.msen.com> > On Mon, May 20, 2013 at 06:26:04PM +0200, Marcus Denker wrote: > > > > No, I know nothing about the Future implementation in Squeak? but > > a Future node in the AST sounds extremely strange. > > I think that the background may be found in this thread: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-December/142111… > > Dave > > >

May 22, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by David T. Lewis

On Mon, May 20, 2013 at 06:26:04PM +0200, Marcus Denker wrote: > > No, I know nothing about the Future implementation in Squeak? but > a Future node in the AST sounds extremely strange. I think that the background may be found in this thread: http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-December/142111… Dave

May 22, 2013

Re: [Pharo-dev] Removing a package from Smalltalkhub

by Damien Cassou

On Tue, May 21, 2013 at 5:53 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > nah, it is a known missing feature (and really needed), there is a fix coming I think next week. the fix is already commited. Now, people can check if it is good: https://ci.inria.fr/pharo-contribution/job/SmalltalkHub/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

May 21, 2013