September 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] PharoKernel #12159

by Levente Uzonyi

On Thu, 30 Sep 2010, Pavel Krivanek wrote: > Hi, > > I uploaded the new version of PharoKernel > > https://gforge.inria.fr/frs/download.php/27540/PharoKernel-1.2-12159.zip > > The Compression package is now part of the kernel image because the > CompiledMethodTrailer requires it. It is on the next discussion whether we > should keep this state. As the result the image is more dirty now. I started the refactoring of CompiledMethodTrailers, but didn't finish it so far. The code is mostly complete, but untested and the migration/integration code is totally missing. I added a class for every kind of trailer, so the trailers which depend on the Compression package can be moved to the Compression package if the refactoring is ready and accepted. Levente > I added some code that enables to download primitive packages and run SUnit > tests. So it will be possible to create automatically the images with > Network and Monticello (after some fixing of this packages). > > Cheers, > -- Pavel >

Sept. 30, 2010

Re: [Pharo-project] About open lively community vs a closed, withdrawn group of programmers

by Alexandre Bergel

Yep Alexandre On 30 Sep 2010, at 08:49, Marcus Denker wrote: > > On Sep 30, 2010, at 2:33 PM, Alexandre Bergel wrote: > >>> While users can't affect the language itself >> >> This is not quite true. The Pizza Java extension about generics is now part of Java. Pizza is the first implementation of Java Generics. > > As far as I remember, Pizza Generics were different to what is now in Java. And it added more than just Generics. > |The Pizza language is an extension to Java with three new features: > |- Generics (aka Parametric polymorphism) > |- Function pointers (aka First-class functions) > |- Class cases and pattern matching (aka Algebraic types) > > Generic Java then was a subset with just the Generics. And that inspired the Generics in Java. > > And it took how long and how much pain to do that? I think people nearly got crazy over the whole thing. > Both Martin Odersky and Gilad Bracha gave up on Java over this, kind of. (Scala just uses the JVM, Newspeak not even that for good > reasons). > > Not really a success story for how one can influence Java, the language. Quite the opposite. > >> Pizza has been formulated with the EPFL. >> > Pizza was started when Martin Odersky was a C3 Prof (assistant-prof) at the University of Karlsruhe... this was when I started > to study there. A looong time ago. 1996? > > Marcus > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 30, 2010

Re: [Pharo-project] Should refactoring cope with symbols in Pharo or should we avoid symbols?

by Tudor Girba

Me too :) Doru On 30 Sep 2010, at 14:53, Simon Denier wrote: > > On 30 sept. 2010, at 14:34, TimM wrote: > >> I logged issue http://code.google.com/p/pharo/issues/detail?id=2817 where I noted that code using a symbol like the following example doesn't get refactored in pharo (e.g. changing the modelChanged method doesn't change this code): >> >> model announcer subscribe: ElephantModelChanged send: #modelChanged to: self >> >> I was surprised by this as in Dolphin it works - and I never thought twice about it - to me, symbol = selector. Renaming a method, or adding a parameter to a method would also affect matching symbols. >> >> So I guess my wider question is, should I simply never use symbols in Pharo? > > > > We have plenty of use for symbols as selectors in Moose/Mondrian/Glamour, so yes I concur with the issue. > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Sept. 30, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1.1 OneClickCogVm

by Tudor Girba

Thanks Mariano. I built the image and made it available. If you want to put it on the INRIA server, you can download it from here: http://www.tudorgirba.com/download/Pharo-1.1.1-dev30.09.1.zip Cheers, Doru On 30 Sep 2010, at 14:16, Mariano Martinez Peck wrote: > > > On Thu, Sep 30, 2010 at 1:44 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi Mariano, > > Is the 1.1.1 dev image available for the old VM? > > No, but you can do it by yourself. Just take the PharoCore 1.1.1 (https://gforge.inria.fr/frs/download.php/27526/PharoCore-1.1.1.zip) > And evaluate: > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > ((Smalltalk at: #ConfigurationOfPharo) project version: '1.1') perform: #silently: with: true; perform: #load. > > > > I was a bit away, and I am not sure of the status. If there is something I can do, please let me know. > > Cheers, > Doru > > > On 25 Sep 2010, at 19:49, Mariano Martinez Peck wrote: > > > > > > > On Sat, Sep 25, 2010 at 7:09 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > > Hi Mariano, > > > > This is a good and needed step. > > > > Now, just a problem: 1.1.1dev image does not work with the regular VM. This is probably because you saved it again after you opened it with the Cog VM. It would be great if the released dev image would work with both. > > > > Excellent suggestion :) > > Thanks doru. > > > > > > Cheers, > > Doru > > > > > > > > On 25 Sep 2010, at 17:56, Mariano Martinez Peck wrote: > > > > > Hi. This is not an official release. I didn't do all the formal procedure for releasing a Pharo image. My idea is try to push CogVM and try to get as much as testers as possible. Try to report issues and help Eliot. For that purpose, I think having a one click image is worth it. > > > > > > So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has some fixes over 1.1 and the CogVM necessary changes). I build the image with exactly the same versions of the external packages than Pharo 1.1. > > > > > > If you want to download that this Pharo1.1.1 dev image that works with Cog here is the link: > > > > > > https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip > > > > > > In addition, and thanks to Lukas, we could generate OneClicks with CogVM. Here you can have a OneClick using the above image: > > > > > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > > > > > Notice that this is not an official release and that there are failing/errors tests. I've already sent emails for them and hopefully someone may fix them. The only thing is not supported is the TestCoverage (since it uses objects as methods, with is not yet supported in CogVM). > > > > > > Cheers > > > > > > Mariano > > > _______________________________________________ > > > Pharo-users mailing list > > > Pharo-users(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > > -- > > www.tudorgirba.com > > > > "The coherence of a trip is given by the clearness of the goal." > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Sept. 30, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1.1 OneClickCogVm

by Levente Uzonyi

On Thu, 30 Sep 2010, laurent laffont wrote: > On up to date ArchLinux, 32 bits. > > 1. Open One Click > 2. Open MonticelloBrowser > 3. Save a packages (Tests for ex.) in package cache > 4. Dialog to enter commit message opens, click ok > 5. crash > > It reminds me about the UUID plugin as external problem. It should be built > as internal. No, it shouldn't. It immediately crashes, if libuuid is not available, which happens to be the case on some 64-bit version of Debian and Ubuntu. Levente > > $ sh Pharo.sh > > Segmentation fault > > > > Smalltalk stack dump: > 0xbfa9f80c I UUID>initialize 2023565392: a(n) UUID > 0xbfa9f824 M UUID class(Behavior)>new: 2000732936: a(n) UUID class > 0xbfa9f848 I UUID class>new 2000732936: a(n) UUID class > 0xbfa9f870 I MCWorkingAncestry>infoWithName:message: 2006007052: a(n) > MCWorkingAncestry > 0xbfa9f8a0 I MCWorkingCopy>newVersionWithName:message: 2001405256: a(n) > MCWorkingCopy > 0xbfa9f8cc I MCWorkingCopy>newVersion 2001405256: a(n) MCWorkingCopy > 0xbfa9f8ec M MCWorkingCopyBrowser>saveVersion 2022465908: a(n) > MCWorkingCopyBrowser > 0xbfa9f90c I PluggableButtonMorphPlus(PluggableButtonMorph)>performAction > 2022486348: a(n) PluggableButtonMorphPlus > 0xbfa9f92c I PluggableButtonMorphPlus>performAction 2022486348: a(n) > PluggableButtonMorphPlus > 0xbfa9f948 M [] in PluggableButtonMorphPlus(PluggableButtonMorph)>mouseUp: > 2022486348: a(n) PluggableButtonMorphPlus > 0xbfa9f96c M Array(SequenceableCollection)>do: 2022623240: a(n) Array > 0xbfa9f994 I PluggableButtonMorphPlus(PluggableButtonMorph)>mouseUp: > 2022486348: a(n) PluggableButtonMorphPlus > 0xbfa9f9b8 I PluggableButtonMorphPlus>mouseUp: 2022486348: a(n) > PluggableButtonMorphPlus > 0xbfa9f9d4 M PluggableButtonMorphPlus(Morph)>handleMouseUp: 2022486348: a(n) > PluggableButtonMorphPlus > 0xbfa9f9f0 M MouseButtonEvent>sentTo: 2022623200: a(n) MouseButtonEvent > 0xbfa9fa0c M PluggableButtonMorphPlus(Morph)>handleEvent: 2022486348: a(n) > PluggableButtonMorphPlus > 0xbfa9fa28 M PluggableButtonMorphPlus(Morph)>handleFocusEvent: 2022486348: > a(n) PluggableButtonMorphPlus > 0xbfa9fa50 M [] in HandMorph>sendFocusEvent:to:clear: 2001235900: a(n) > HandMorph > 0xbfa9fa6c M [] in PasteUpMorph>becomeActiveDuring: 2001524352: a(n) > PasteUpMorph > 0xbfa9fa88 M BlockClosure>on:do: 2022623148: a(n) BlockClosure > 0xbfa9fab4 M PasteUpMorph>becomeActiveDuring: 2001524352: a(n) PasteUpMorph > 0xbfa9fad8 M HandMorph>sendFocusEvent:to:clear: 2001235900: a(n) HandMorph > 0xbfa9fb00 M HandMorph>sendEvent:focus:clear: 2001235900: a(n) HandMorph > 0xbfa9fb24 M HandMorph>sendMouseEvent: 2001235900: a(n) HandMorph > 0xbfa9fb48 M HandMorph>handleEvent: 2001235900: a(n) HandMorph > 0xbfa9fb74 M HandMorph>processEvents 2001235900: a(n) HandMorph > 0xbfa9fb8c M [] in WorldState>doOneCycleNowFor: 2002154700: a(n) WorldState > 0xbfa9fbb0 M Array(SequenceableCollection)>do: 1999805528: a(n) Array > 0xbfa9fbcc M WorldState>handsDo: 2002154700: a(n) WorldState > 0xbfa9fbe8 M WorldState>doOneCycleNowFor: 2002154700: a(n) WorldState > 0xbfa9fc04 M WorldState>doOneCycleFor: 2002154700: a(n) WorldState > 0xbfa9fc20 M PasteUpMorph>doOneCycle 2001524352: a(n) PasteUpMorph > 0xbfa9fc40 I [] in Project class>? 2002234208: a(n) Project class > 2001355268 s [] in BlockClosure>? > > Most recent primitives > truncated > fractionPart > truncated > basicNew > truncated > basicNew > truncated > fractionPart > fractionPart > truncated > fractionPart > truncated > fractionPart > truncated > basicNew > truncated > perform:with: > perform:with: > basicNew > truncated > @ > @ > @ > basicNew > @ > @ > basicNew > @ > @ > primDisplayString:from:to:map:xTable:kern: > @ > primDisplayString:from:to:map:xTable:kern: > @ > @ > @ > @ > basicNew > @ > @ > basicNew > @ > @ > primDisplayString:from:to:map:xTable:kern: > @ > primDisplayString:from:to:map:xTable:kern: > @ > @ > @ > @ > basicNew > @ > @ > basicNew > @ > @ > primDisplayString:from:to:map:xTable:kern: > @ > primDisplayString:from:to:map:xTable:kern: > @ > @ > @ > @ > basicNew > @ > @ > basicNew > @ > @ > primDisplayString:from:to:map:xTable:kern: > @ > primDisplayString:from:to:map:xTable:kern: > @ > @ > @ > @ > basicNew > @ > @ > basicNew > @ > @ > primDisplayString:from:to:map:xTable:kern: > @ > primDisplayString:from:to:map:xTable:kern: > @ > basicNew > @ > @ > @ > basicNew > @ > perform:with: > @ > @ > perform:with: > @ > basicNew > @ > @ > basicNew > @ > copyBits > @ > @ > basicNew > at:put: > basicNew > new: > at:put: > species > basicNew > new: > species > basicNew > new: > species > basicNew > new: > at:put: > at:put: > species > basicNew > new: > @ > @ > basicNew > at:put: > @ > @ > basicNew > at:put: > species > species > species > species > species > species > replaceFrom:to:with:startingAt: > at:put: > new: > at:put: > at:put: > @ > @ > basicNew > shallowCopy > shallowCopy > basicNew > new: > at:put: > shallowCopy > new: > replaceFrom:to:with:startingAt: > at:put: > shallowCopy > basicNew > basicNew > @ > @ > basicNew > @ > perform:with: > @ > @ > perform:with: > @ > basicNew > @ > @ > basicNew > @ > perform:with: > @ > @ > perform:with: > @ > basicNew > copyBits > @ > @ > basicNew > at:put: > @ > @ > basicNew > shallowCopy > shallowCopy > basicNew > new: > at:put: > shallowCopy > new: > replaceFrom:to:with:startingAt: > at:put: > shallowCopy > basicNew > basicNew > @ > @ > basicNew > at:put: > @ > @ > @ > basicNew > @ > perform:with: > @ > @ > perform:with: > @ > basicNew > @ > @ > basicNew > @ > copyBits > @ > @ > basicNew > at:put: > basicNew > new: > species > basicNew > new: > species > basicNew > new: > at:put: > at:put: > at:put: > primShowRectLeft:right:top:bottom: > primShowRectLeft:right:top:bottom: > millisecondClockValue > signal > primSignal:atMilliseconds: > millisecondClockValue > wait > primGetNextEvent: > millisecondClockValue > wait > signal > millisecondClockValue > primSignal:atMilliseconds: > millisecondClockValue > wait > signal > wait > primShowRectLeft:right:top:bottom: > primitiveDeferUpdates: > forceDisplayUpdate > findNextUnwindContextUpTo: > terminateTo: > basicNew: > primMakeUUID > Abandon > > > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > > > On Thu, Sep 30, 2010 at 1:44 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > >> Hi Mariano, >> >> Is the 1.1.1 dev image available for the old VM? >> >> I was a bit away, and I am not sure of the status. If there is something I >> can do, please let me know. >> >> Cheers, >> Doru >> >> >> On 25 Sep 2010, at 19:49, Mariano Martinez Peck wrote: >> >>> >>> >>> On Sat, Sep 25, 2010 at 7:09 PM, Tudor Girba <tudor.girba(a)gmail.com> >> wrote: >>> Hi Mariano, >>> >>> This is a good and needed step. >>> >>> Now, just a problem: 1.1.1dev image does not work with the regular VM. >> This is probably because you saved it again after you opened it with the Cog >> VM. It would be great if the released dev image would work with both. >>> >>> Excellent suggestion :) >>> Thanks doru. >>> >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On 25 Sep 2010, at 17:56, Mariano Martinez Peck wrote: >>> >>>> Hi. This is not an official release. I didn't do all the formal >> procedure for releasing a Pharo image. My idea is try to push CogVM and try >> to get as much as testers as possible. Try to report issues and help Eliot. >> For that purpose, I think having a one click image is worth it. >>>> >>>> So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has >> some fixes over 1.1 and the CogVM necessary changes). I build the image with >> exactly the same versions of the external packages than Pharo 1.1. >>>> >>>> If you want to download that this Pharo1.1.1 dev image that works with >> Cog here is the link: >>>> >>>> >> https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip >>>> >>>> In addition, and thanks to Lukas, we could generate OneClicks with >> CogVM. Here you can have a OneClick using the above image: >>>> >>>> >> https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip >>>> >>>> Notice that this is not an official release and that there are >> failing/errors tests. I've already sent emails for them and hopefully >> someone may fix them. The only thing is not supported is the TestCoverage >> (since it uses objects as methods, with is not yet supported in CogVM). >>>> >>>> Cheers >>>> >>>> Mariano >>>> _______________________________________________ >>>> Pharo-users mailing list >>>> Pharo-users(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >>> >>> -- >>> www.tudorgirba.com >>> >>> "The coherence of a trip is given by the clearness of the goal." >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> www.tudorgirba.com >> >> "In a world where everything is moving ever faster, >> one might have better chances to win by moving slower." >> >> >> >> >> _______________________________________________ >> Pharo-users mailing list >> Pharo-users(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users >> >

Sept. 30, 2010

Re: [Pharo-project] Should refactoring cope with symbols in Pharo or should we avoid symbols?

by Simon Denier

On 30 sept. 2010, at 14:34, TimM wrote: > I logged issue http://code.google.com/p/pharo/issues/detail?id=2817 where I noted that code using a symbol like the following example doesn't get refactored in pharo (e.g. changing the modelChanged method doesn't change this code): > > model announcer subscribe: ElephantModelChanged send: #modelChanged to: self > > I was surprised by this as in Dolphin it works - and I never thought twice about it - to me, symbol = selector. Renaming a method, or adding a parameter to a method would also affect matching symbols. > > So I guess my wider question is, should I simply never use symbols in Pharo? We have plenty of use for symbols as selectors in Moose/Mondrian/Glamour, so yes I concur with the issue. -- Simon

Sept. 30, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.1.1 OneClickCogVm

by Levente Uzonyi

On Thu, 30 Sep 2010, Igor Stasenko wrote: > 2 years, we're plagued by this for two years! I wonder why does anyone expect that a single build will work on all un*x distributions? It just won't work. Levente > > On 30 September 2010 15:14, laurent laffont <laurent.laffont(a)gmail.com> wrote: >> On up to date ArchLinux, 32 bits. >> 1. Open One Click >> 2. Open MonticelloBrowser >> 3. Save a packages (Tests for ex.) in package cache >> 4. Dialog to enter commit message opens, click ok >> 5. crash >> It reminds me about the UUID plugin as external problem. It should be built >> as internal. >> $ sh Pharo.sh >> Segmentation fault >> >> >> Smalltalk stack dump: >> 0xbfa9f80c I UUID>initialize 2023565392: a(n) UUID >> 0xbfa9f824 M UUID class(Behavior)>new: 2000732936: a(n) UUID class >> 0xbfa9f848 I UUID class>new 2000732936: a(n) UUID class > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 30, 2010

Re: [Pharo-project] About open lively community vs a closed, withdrawn group of programmers

by Marcus Denker

On Sep 30, 2010, at 2:33 PM, Alexandre Bergel wrote: >> While users can't affect the language itself > > This is not quite true. The Pizza Java extension about generics is now part of Java. Pizza is the first implementation of Java Generics. As far as I remember, Pizza Generics were different to what is now in Java. And it added more than just Generics. |The Pizza language is an extension to Java with three new features: |- Generics (aka Parametric polymorphism) |- Function pointers (aka First-class functions) |- Class cases and pattern matching (aka Algebraic types) Generic Java then was a subset with just the Generics. And that inspired the Generics in Java. And it took how long and how much pain to do that? I think people nearly got crazy over the whole thing. Both Martin Odersky and Gilad Bracha gave up on Java over this, kind of. (Scala just uses the JVM, Newspeak not even that for good reasons). Not really a success story for how one can influence Java, the language. Quite the opposite. > Pizza has been formulated with the EPFL. > Pizza was started when Martin Odersky was a C3 Prof (assistant-prof) at the University of Karlsruhe... this was when I started to study there. A looong time ago. 1996? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 30, 2010

[Pharo-project] PharoKernel #12159

by Pavel Krivanek

Hi, I uploaded the new version of PharoKernel https://gforge.inria.fr/frs/download.php/27540/PharoKernel-1.2-12159.zip The Compression package is now part of the kernel image because the CompiledMethodTrailer requires it. It is on the next discussion whether we should keep this state. As the result the image is more dirty now. I added some code that enables to download primitive packages and run SUnit tests. So it will be possible to create automatically the images with Network and Monticello (after some fixing of this packages). Cheers, -- Pavel

Sept. 30, 2010

[Pharo-project] Pharo 1.1.1 OneClickCogVm

by Sven Van Caekenberghe

On 30 Sep 2010, at 14:28, Igor Stasenko wrote: > 2 years, we're plagued by this for two years! Less plugins, more Smalltalk code! I want to look at everything and never see C. Plugins/primitives should only be there when they are absolutely necessary (to access a platform feature or for crucial performance). Sven

Sept. 30, 2010