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

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Denis Kudriashov

2013/5/22 Frank Shearar <frank.shearar(a)gmail.com> > Why does ifTrue: use a compile-time transformation? But what makes #future be similar to "ifTrue" case? What makes it so special? > 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

[update 3.0] #30154

by Marcus Denker

30154 ----- 10678 Failing Regressiontest: FLSortedCollectionSerializationTest https://pharo.fogbugz.com/f/cases/10678 10713 verbose error log in privSaveImageWithCleanup https://pharo.fogbugz.com/f/cases/10713 10692 BasicCodeLoader and a subclass directly references ParserNotification https://pharo.fogbugz.com/f/cases/10692/ Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelTests-MarcusDenker.317.di… http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-CommandLine-MarcusDenk…

May 22, 2013

Re: [Pharo-dev] 3.0 git tracker

by Camillo Bruni

On 2013-05-19, at 03:23, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 18 May 2013 02:31, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> Pharo 3.0 is now properly tracked on github >> >> - https://github.com/pharo-project/pharo-core >> - the update messages are properly shown >> - html output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… >> - diff output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… >> - patch output: https://github.com/pharo-project/pharo-core/commit/cc3a428b19e2696e0540c4cc… > > You are my hero! > Now can we have same for VM sources? > I would really love to simplify a process of changing VM by simply modifying > file either on disk (in platform sources) or in image (VMMaker & friends) > and then do > > git ci -m "new fix/feature integrated" well it works only 1 way right now. I have not implemented any mapping from my fileformat to monticello (even though it shouldn't be that hard).

May 22, 2013

Re: [Pharo-dev] AST Everywhere, Reflectivity

by Camillo Bruni

On 2013-05-22, at 09:53, Frank Shearar <frank.shearar(a)gmail.com> wrote: > 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. Futures in the compiler do only make sense in two cases: a) the VM has special bytecode support for futures b) there is a special new syntax for it AFAIK neither of it is the case.

May 22, 2013

do not forget to register to the pharo web day

by StÃ©phane Ducasse

Please register for the pharo web day http://www.inria.fr/centre/lille/agenda/conference-web-3.0-avec-pharo

May 22, 2013

Re: [Pharo-dev] TxText new version 0.8

by StÃ©phane Ducasse

I would use TextModelCore TextModelExtensions TextModelCore-Tests No extra dash in the middle. Stef On May 21, 2013, at 10:24 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2013/5/21 stephane ducasse <stephane.ducasse(a)free.fr> > > On May 21, 2013, at 9:00 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > >> 2013/5/20 stephane ducasse <stephane.ducasse(a)free.fr> >> >>> Hello. >>> >>> New TxText version 0.8 is ready: >>> >>> - editor stuff extracted to separate packages TxText-Editor and TxTextTests-Editor >> >> may be you should call the second package TxTextEditor-Tests >> >> I just follow convention of other TxText packages: TxText-Model -> TxTextTests-Model, TxText-Layout -> TxTextTests-Layout and etc. >> Some times ago I suggest such repackaging and nobody was against it > > Still I think that the packages names are not good. I do not hitnk that having tests mixed with the package name is a good approach > and we should clean all of them for 3.0 > > So what the correct way (Pharo way) to name test packages? > For example I have 'MyPackage-SubCat1-SubCat2'. What name for test package should be? > > > Stef > > > > >

May 22, 2013

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

by stephane ducasse

cool :) On May 22, 2013, at 9:34 AM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > 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] [update 3.0] #30154

by Marcus Denker

On May 22, 2013, at 10:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Marcus, there are some problems with renamed Morphic package. In the Monticello packages list I see Morphic (MarcusDenker.1). > In the class PluggableMenuSpec there is a category named *Morphic-Menus, that now should be *Morphic-Base-Menus. So I guess this mess has origin in the Spec update integration. > > I think we should revert whole this update. So I retracted it. Now just *how* do I know that a SLICE is bad? It did not lead to a conflict, there is no way to realize that there is a problem. Marcus

May 22, 2013

Re: [Pharo-dev] [update 3.0] #30154

by Marcus Denker

On May 22, 2013, at 10:00 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > Marcus, there are some problems with renamed Morphic package. In the Monticello packages list I see Morphic (MarcusDenker.1). > In the class PluggableMenuSpec there is a category named *Morphic-Menus, that now should be *Morphic-Base-Menus. So I guess this mess has origin in the Spec update integration. > > I think we should revert whole this update. > So does that mean as soon as we rename a package we just can never merge in anything anymore? Maybe then we should have spend some time to finish reviewing all the pending issues before doing the rename? This will now cost hours and hours of workâ¦. > -- Pavel > > On Wed, May 22, 2013 at 8:30 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 30154 > ----- > > 10715 Spec update > https://pharo.fogbugz.com/f/cases/10715 > > 10701 Remove non-boolean setting > https://pharo.fogbugz.com/f/cases/10701 > > 10678 Failing Regressiontest: FLSortedCollectionSerializationTest > https://pharo.fogbugz.com/f/cases/10678 > > 10716 update shrinking methods > https://pharo.fogbugz.com/f/cases/10716 > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.182… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.127.di… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Settings-Compiler-MarcusDenke… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusSpec-MarcusDenker.1.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-MarcusDenker.1.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1460.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelTests-MarcusDenker.316.di… > > >

May 22, 2013

Re: [Pharo-dev] [update 3.0] #30154

by Pavel Krivanek

Marcus, there are some problems with renamed Morphic package. In the Monticello packages list I see Morphic (MarcusDenker.1). In the class PluggableMenuSpec there is a category named *Morphic-Menus, that now should be *Morphic-Base-Menus. So I guess this mess has origin in the Spec update integration. I think we should revert whole this update. -- Pavel On Wed, May 22, 2013 at 8:30 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 30154 > ----- > > 10715 Spec update > https://pharo.fogbugz.com/f/cases/10715 > > 10701 Remove non-boolean setting > https://pharo.fogbugz.com/f/cases/10701 > > 10678 Failing Regressiontest: FLSortedCollectionSerializationTest > https://pharo.fogbugz.com/f/cases/10678 > > 10716 update shrinking methods > https://pharo.fogbugz.com/f/cases/10716 > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/System-Support-MarcusDenker.8… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Widgets-MarcusDenker.182… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Core-MarcusDenker.127.di… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Settings-Compiler-MarcusDenke… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/NautilusSpec-MarcusDenker.1.d… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-MarcusDenker.1.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1460.diff > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelTests-MarcusDenker.316.di… > > >

May 22, 2013