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

Re: [Pharo-project] In Latest OB I cannot add a class variable

by Mariano Martinez Peck

On Sat, Oct 2, 2010 at 1:54 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > Ok, I fixed that. The refactoring engine now supports all the 24 (!!!) > distinct patterns of defining a subclass/trait in Pharo (see below). > > Name: Refactoring-Changes-lr.15 > Author: lr > Time: 2 October 2010, 1:50:13 pm > UUID: 82093dfb-e7f2-4ff7-afe7-ac7196632196 > Ancestors: Refactoring-Changes-lr.14 > > - also support subclasses of nil > > Hi Lukas. I tried with nil and it works. However, putting ProtoObject, it didn't, since definitionClass ^ Smalltalk globals at: (self superclassName ifNil: [ ^ ProtoObject ]) self superclassName answers a Text for 'ProtoObject variableSubclass: #MessageCatchingProxy instanceVariableNames: '''' classVariableNames: '''' poolDictionaries: '''' category: ''Proxies''' Cheers Mariano > The undo operation of the respective actions should work as well. The > exception here is an asymmetry (bug?) in the Pharo class definition > strings that causes classes without traits to be printed without the > #uses: claus. Evaluating this definition string does not remove the > trait composition if the class happens to have one though. > > Lukas > > #('`className class instanceVariableNames: `#instanceVariableNames' > '`className class uses: `@traitComposition instanceVariableNames: > `#instanceVariableNames' '`@superclass subclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject subclass: `#className instanceVariableNames: > `#instanceVariableNames classVariableNames: `#classVariableNames > poolDictionaries: `#poolDictionaries category: `#category. `className > superclass: `@superclass' '`@superclass subclass: `#className uses: > `@traitComposition instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category' 'ProtoObject subclass: > `#className uses: `@traitComposition instanceVariableNames: > `#instanceVariableNames classVariableNames: `#classVariableNames > poolDictionaries: `#poolDictionaries category: `#category. `className > superclass: `@superclass' '`@superclass variableByteSubclass: > `#className instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category' 'ProtoObject > variableByteSubclass: `#className instanceVariableNames: > `#instanceVariableNames classVariableNames: `#classVariableNames > poolDictionaries: `#poolDictionaries category: `#category. `className > superclass: `@superclass' '`@superclass variableByteSubclass: > `#className uses: `@traitComposition instanceVariableNames: > `#instanceVariableNames classVariableNames: `#classVariableNames > poolDictionaries: `#poolDictionaries category: `#category' > 'ProtoObject variableByteSubclass: `#className uses: > `@traitComposition instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category. `className superclass: > `@superclass' '`@superclass variableSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject variableSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category. `className superclass: `@superclass' '`@superclass > variableSubclass: `#className uses: `@traitComposition > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject variableSubclass: `#className uses: > `@traitComposition instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category. `className superclass: > `@superclass' '`@superclass variableWordSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject variableWordSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category. `className superclass: `@superclass' '`@superclass > variableWordSubclass: `#className uses: `@traitComposition > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject variableWordSubclass: `#className uses: > `@traitComposition instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category. `className superclass: > `@superclass' '`@superclass weakSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject weakSubclass: `#className > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category. `className superclass: `@superclass' '`@superclass > weakSubclass: `#className uses: `@traitComposition > instanceVariableNames: `#instanceVariableNames classVariableNames: > `#classVariableNames poolDictionaries: `#poolDictionaries category: > `#category' 'ProtoObject weakSubclass: `#className uses: > `@traitComposition instanceVariableNames: `#instanceVariableNames > classVariableNames: `#classVariableNames poolDictionaries: > `#poolDictionaries category: `#category. `className superclass: > `@superclass' '`traitName classTrait uses: `@traitComposition' 'Trait > named: `#traitName uses: `@traitComposition category: `#category') > > On 2 October 2010 13:01, Lukas Renggli <renggli(a)gmail.com> wrote: > >> Lukas, now I have another problem. I am not sure if it is OB latest code > >> related, but I think so. > > > > No, that was always the case. > > > >> If you take any class, suppose RBSemanticTest and go to its definition. > >> Change it so that it extends from ProtoObject instead of TestCase. When > you > >> accept the code (save it), the browser goes directly to Browse > ProtoObject, > >> actually to : > >> > >> ProtoObject subclass: #ProtoObject > >> instanceVariableNames: '' > >> classVariableNames: '' > >> poolDictionaries: '' > >> category: 'Kernel-Objects'. > >> ProtoObject superclass: nil > > > > Creating a subclass like this was never supported by the refactoring > engine. > > > > You have to write it like: > > > > nil subclass: #ProtoObject > > instanceVariableNames: '' > > classVariableNames: '' > > poolDictionaries: '' > > category: 'Kernel-Objects' > > > > Lukas > > > > -- > > Lukas Renggli > > www.lukas-renggli.ch > > > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 2, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by StÃ©phane Ducasse

On Oct 2, 2010, at 7:01 PM, Igor Stasenko wrote: > On 2 October 2010 19:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Hi igor >> >> do you understand why the previous definition was >> >> cachedDefinitions >> Definitions ifNil: [Definitions := WeakIdentityKeyDictionary new. WeakArray addWeakDependent: Definitions]. >> ^ Definitions >> > i don't. :) > > It just a way to free memory as fast as possible. > But its really not worth spending so much CPU in order to save few > bytes of memory. :) I looked a bit at the code and it is used just so that MCDefinition flush them if they are not already GCed. So I understand. Stef

Oct. 2, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by Igor Stasenko

On 2 October 2010 19:47, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi igor > > do you understand why the previous definition was > > cachedDefinitions > Â Â Â Â Definitions ifNil: [Definitions := WeakIdentityKeyDictionary new. Â WeakArray addWeakDependent: Definitions]. > Â Â Â Â ^ Definitions > i don't. :) It just a way to free memory as fast as possible. But its really not worth spending so much CPU in order to save few bytes of memory. > Stef > > On Oct 1, 2010, at 7:34 PM, Igor Stasenko wrote: > >> Here the simple fix for it. >> >> >> >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> <mc-cache-fix.1.cs>_______________________________________________ >> 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 > -- Best regards, Igor Stasenko AKA sig.

Oct. 2, 2010

Re: [Pharo-project] Another fixes to finalization (was Re: [update 1.2] #12161 - #12172)

by StÃ©phane Ducasse

Hi igor do you understand why the previous definition was cachedDefinitions Definitions ifNil: [Definitions := WeakIdentityKeyDictionary new. WeakArray addWeakDependent: Definitions]. ^ Definitions Stef On Oct 1, 2010, at 7:34 PM, Igor Stasenko wrote: > Here the simple fix for it. > > > > > > -- > Best regards, > Igor Stasenko AKA sig. > <mc-cache-fix.1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2010

[Pharo-project] [update 1.2] #12167

by StÃ©phane Ducasse

12167 ----- - Issue 3036: SUnit Refactoring (introduced class factory). Thanks Thanks Sean De Nigris. - Issue 3047: Added intention revealing helper method to AppRegistry class>>register:. Thanks Sean De Nigris. - Issue 3055: postCopy in StrikeFontSet. Thanks Nicolas Cellier. - Issue 3056: EventManager uses postCopy. Thanks Nicolas Cellier. - Issue 3054: Heap improvements. Thanks Nicolas Cellier. - Issue 3053: Better showMenu. Thanks Tobias Pape.

Oct. 2, 2010

Re: [Pharo-project] Issue 3036: SUnit Refactoring

by Sean P. DeNigris

StÃ©phane Ducasse wrote: > > Sean we just merged SUnit 4.0 so can you have a look. > Okay, thanks. -- View this message in context: http://forum.world.st/Issue-3036-SUnit-Refactoring-tp2914375p2952516.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 2, 2010

Re: [Pharo-project] Statistic tools in Pharo

by Alexandre Bergel

Ok. I am personally more interested in regression models Alexandre On 2 Oct 2010, at 07:15, CÃ©drick BÃ©ler wrote: > > Le 29 sept. 2010 Ã 15:39, Alexandre Bergel a Ã©crit : > >>>> Thanks Jimmie. >>>> About half of the tests are red. This library is about linear Algebra. Not really about statistics. >>>> But thanks for the link! >>>> >>>> Alexandre >>> >>> If it's the same as what you can find in VW, in addition to linear algebra, it includes numerical methods for quite a few probability distributions as well though. >> >> Ok, thanks for the input! > > > FWIW, I plan to implement Bayesian Network in Smalltalk... Nevertheless, it will be more a research project... > > Until now, I haven't found any project nor code in that direction... except maybe SBN (Simple Bayesian Network) in ruby... > > Cheers > > > > > >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 2, 2010

Re: [Pharo-project] In Latest OB I cannot add a class variable

by Lukas Renggli

Ok, I fixed that. The refactoring engine now supports all the 24 (!!!) distinct patterns of defining a subclass/trait in Pharo (see below). Name: Refactoring-Changes-lr.15 Author: lr Time: 2 October 2010, 1:50:13 pm UUID: 82093dfb-e7f2-4ff7-afe7-ac7196632196 Ancestors: Refactoring-Changes-lr.14 - also support subclasses of nil The undo operation of the respective actions should work as well. The exception here is an asymmetry (bug?) in the Pharo class definition strings that causes classes without traits to be printed without the #uses: claus. Evaluating this definition string does not remove the trait composition if the class happens to have one though. Lukas #('`className class instanceVariableNames: `#instanceVariableNames' '`className class uses: `@traitComposition instanceVariableNames: `#instanceVariableNames' '`@superclass subclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject subclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass subclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject subclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableByteSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableByteSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableByteSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableByteSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableWordSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableWordSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass variableWordSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject variableWordSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass weakSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject weakSubclass: `#className instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`@superclass weakSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category' 'ProtoObject weakSubclass: `#className uses: `@traitComposition instanceVariableNames: `#instanceVariableNames classVariableNames: `#classVariableNames poolDictionaries: `#poolDictionaries category: `#category. `className superclass: `@superclass' '`traitName classTrait uses: `@traitComposition' 'Trait named: `#traitName uses: `@traitComposition category: `#category') On 2 October 2010 13:01, Lukas Renggli <renggli(a)gmail.com> wrote: >> Lukas, now I have another problem. I am not sure if it is OB latest code >> related, but I think so. > > No, that was always the case. > >> If you take any class, suppose RBSemanticTest and go to its definition. >> Change it so that it extends from ProtoObject instead of TestCase. When you >> accept the code (save it), the browser goes directly to Browse ProtoObject, >> actually to : >> >> ProtoObject subclass: #ProtoObject >> Â Â Â instanceVariableNames: '' >> Â Â Â classVariableNames: '' >> Â Â Â poolDictionaries: '' >> Â Â Â category: 'Kernel-Objects'. >> ProtoObject superclass: nil > > Creating a subclass like this was never supported by the refactoring engine. > > You have to write it like: > > nil subclass: #ProtoObject > Â Â Â Â instanceVariableNames: '' > Â Â Â Â classVariableNames: '' > Â Â Â Â poolDictionaries: '' > Â Â Â Â category: 'Kernel-Objects' > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

Oct. 2, 2010

Re: [Pharo-project] Statistic tools in Pharo

by CÃ©drick BÃ©ler

Le 29 sept. 2010 Ã 15:39, Alexandre Bergel a Ã©crit : >>> Thanks Jimmie. >>> About half of the tests are red. This library is about linear Algebra. Not really about statistics. >>> But thanks for the link! >>> >>> Alexandre >> >> If it's the same as what you can find in VW, in addition to linear algebra, it includes numerical methods for quite a few probability distributions as well though. > > Ok, thanks for the input! FWIW, I plan to implement Bayesian Network in Smalltalk... Nevertheless, it will be more a research project... Until now, I haven't found any project nor code in that direction... except maybe SBN (Simple Bayesian Network) in ruby... Cheers > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2010

Re: [Pharo-project] In Latest OB I cannot add a class variable

by Lukas Renggli

> Lukas, now I have another problem. I am not sure if it is OB latest code > related, but I think so. No, that was always the case. > If you take any class, suppose RBSemanticTest and go to its definition. > Change it so that it extends from ProtoObject instead of TestCase. When you > accept the code (save it), the browser goes directly to Browse ProtoObject, > actually to : > > ProtoObject subclass: #ProtoObject > Â Â Â instanceVariableNames: '' > Â Â Â classVariableNames: '' > Â Â Â poolDictionaries: '' > Â Â Â category: 'Kernel-Objects'. > ProtoObject superclass: nil Creating a subclass like this was never supported by the refactoring engine. You have to write it like: nil subclass: #ProtoObject Â Â Â instanceVariableNames: '' Â Â Â classVariableNames: '' Â Â Â poolDictionaries: '' Â Â Â category: 'Kernel-Objects' Lukas -- Lukas Renggli www.lukas-renggli.ch

Oct. 2, 2010