December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] I have a problem with 11126

by StÃ©phane Ducasse

I'm back from christmas shpping mess. ok I will do it. On Dec 30, 2009, at 5:20 PM, Igor Stasenko wrote: > 2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> hi igor >> >> >> up to 11125 it works well and after when I was trying to do the last two cs using MC >> >> in 11125 I get >> >> new >> ^ self trailerClass basicNew initialize >> trailerClass >> ^ TrailerClass ifNil: [ OldMethodTrailer ] >> >> in 11126 when I try to load these packages. >> >> I get CompiledMethodTrailer new >> does understand trailerClass >> >> > > You seem stepped on same trap as Andreas did. :) > MC minds own method removal order, > and removes #trailerClass before #new, > which then leads to DNU. > > Split cleanup into two stages: > - in first update, remove just #new > - in second , remove #trailerClass and the rest of stuff > > so, MC will have no chances to interfere with removal order. > > -- > 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

Dec. 30, 2009

Re: [Pharo-project] Pharo-beginner mailing list ?

by StÃ©phane Ducasse

My point is that some people may be bored by too technical discussions Miguel I agree on the number of list. We should check if there is enough people. @Adrian: the forum idea is nice but I do not why it did not work for Smalltalk. I went to the site you mentioned but I could not get how it works. > +1 I would create it. It is not more than 1 hour or so of work. 3min :) > We don't loose nothing. Only the time will say if this was a good idea or not :) > > > On Wed, Dec 30, 2009 at 5:07 PM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > +1 > > Its ok to separate the development of pharo from the > use/promotion/welcome to Pharo. > > Just don't let this become a mess with dozens of lists with a couple > of posts each. This won't > help Pharo cohesion in the long term. > > Miguel CobÃ¡ > > On Wed, Dec 30, 2009 at 5:41 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > Hi all > > > > I remember that the squeak-beginner mailing-list (our ideas) was a huge success > > since it enabled people to ask questions and have less mails. > > So a question to you: do you think that it would be good to have a pharo-beginner mailing list? > > > > Stef > > _______________________________________________ > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 30, 2009

Re: [Pharo-project] New class factory for tests (and other use cases)

by Alexandre Bergel

Yeah, I will give a try Alexandre On 30 Dec 2009, at 17:54, Adrian Kuhn wrote: > Alexandre Bergel <alexandre@...> writes: > >> I feel yes. In the code you gave, there are 4 hard-to-remember >> keywords (ClassFactory, newSubclass:, with:, metaSide), without >> counting the block declaration. >> Variable declaration is possible using a method >> #createClassNamed:superclass:ivs: > > It's a new API, so you have to learn it, yes. > > It's regular and rather small though. You start with > > #newClass > #newClassWith: aBlock > #newSubclass: aClass > #newSubclass: aClass with: aBlock > > and continue within the block with > > #classSide ... > #declareInstVar: name > #compileGetterFor: name > #compileSetterFor: name > #compileAccessorsFor: name > #compile: sourceString > > of which you typically need the last two only. > > C'est tout :) > > --AA > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 30, 2009

Re: [Pharo-project] New class factory for tests (and other use cases)

by Adrian Kuhn

Alexandre Bergel <alexandre@...> writes: > I feel yes. In the code you gave, there are 4 hard-to-remember > keywords (ClassFactory, newSubclass:, with:, metaSide), without > counting the block declaration. > Variable declaration is possible using a method > #createClassNamed:superclass:ivs: It's a new API, so you have to learn it, yes. It's regular and rather small though. You start with #newClass #newClassWith: aBlock #newSubclass: aClass #newSubclass: aClass with: aBlock and continue within the block with #classSide ... #declareInstVar: name #compileGetterFor: name #compileSetterFor: name #compileAccessorsFor: name #compile: sourceString of which you typically need the last two only. C'est tout :) --AA

Dec. 30, 2009

Re: [Pharo-project] akuhn/SUnit, christmas edition :)

by Alexandre Bergel

> This is an aspect that I changed. An outcome is unexpected if and > only if it > does not match what is in the stored history. (For compatibility only > #expectedFailures are added to the stored history.) So the preferred > way to > mark an outcome as unexpected is to store the history. Ok, I understand now. Could be okay. But how can I distinguish an expected failure from a real failure ? At the first run, I get some failed tests. Are they real or expected failures? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 30, 2009

Re: [Pharo-project] I have a problem with 11126

by Igor Stasenko

2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > hi igor > > > up to 11125 it works well and after when I was trying to do the last two cs using MC > > in 11125 I get > > new > Â Â Â Â ^ self trailerClass basicNew initialize > trailerClass > Â Â Â Â ^ TrailerClass ifNil: [ OldMethodTrailer ] > > in 11126 when I try to load these packages. > > I get Â CompiledMethodTrailer new > Â Â Â Â Â Â Â Â Â Â Â Â does understand trailerClass > > You seem stepped on same trap as Andreas did. :) MC minds own method removal order, and removes #trailerClass before #new, which then leads to DNU. Split cleanup into two stages: - in first update, remove just #new - in second , remove #trailerClass and the rest of stuff so, MC will have no chances to interfere with removal order. -- Best regards, Igor Stasenko AKA sig.

Dec. 30, 2009

Re: [Pharo-project] Pharo-beginner mailing list ?

by Mariano Martinez Peck

+1 I would create it. It is not more than 1 hour or so of work. We don't loose nothing. Only the time will say if this was a good idea or not :) On Wed, Dec 30, 2009 at 5:07 PM, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > +1 > > Its ok to separate the development of pharo from the > use/promotion/welcome to Pharo. > > Just don't let this become a mess with dozens of lists with a couple > of posts each. This won't > help Pharo cohesion in the long term. > > Miguel CobÃ¡ > > On Wed, Dec 30, 2009 at 5:41 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > Hi all > > > > I remember that the squeak-beginner mailing-list (our ideas) was a huge > success > > since it enabled people to ask questions and have less mails. > > So a question to you: do you think that it would be good to have a > pharo-beginner mailing list? > > > > Stef > > _______________________________________________ > > 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 >

Dec. 30, 2009

Re: [Pharo-project] New class factory for tests (and other use cases)

by Alexandre Bergel

>> You propose: >>> class := ClassFactory newSubclass: Point with: [ :f | >>> f metaSide compile: 'somePoint ^ self x: 2 y: 3'. >>> f compile: '+ arg ^ self x + arg x ..... 3' ]. >>> ]. >> >> I find this difficult to remember. > > What is difficult to remember, the API names? I feel yes. In the code you gave, there are 4 hard-to-remember keywords (ClassFactory, newSubclass:, with:, metaSide), without counting the block declaration. Variable declaration is possible using a method #createClassNamed:superclass:ivs: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 30, 2009

Re: [Pharo-project] Pharo-beginner mailing list ?

by Miguel CobÃ¡

+1 Its ok to separate the development of pharo from the use/promotion/welcome to Pharo. Just don't let this become a mess with dozens of lists with a couple of posts each. This won't help Pharo cohesion in the long term. Miguel CobÃ¡ On Wed, Dec 30, 2009 at 5:41 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all > > I remember that the squeak-beginner mailing-list (our ideas) was a huge success > since it enabled people to ask questions and have less mails. > So a question to you: do you think that it would be good to have a pharo-beginner mailing list? > > Stef > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 30, 2009

Re: [Pharo-project] Pharo-beginner mailing list ?

by Johan Fabry

+1 for pharo-users mailing list. Excellent idea! On 30 Dec 2009, at 09:42, StÃ©phane Ducasse wrote: > Ok > (we are all beginners :) at least I'm :) ). > > > On Dec 30, 2009, at 1:35 PM, George Herolyants wrote: > >> Hi >> >> Maybe it would be better to name it pharo-user(s) and leave this list >> for the developers of pharo? Because "beginner" has too narrow >> meaning. >> >> >> George >> >> 2009/12/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Hi all >>> >>> I remember that the squeak-beginner mailing-list (our ideas) was a >>> huge success >>> since it enabled people to ask questions and have less mails. >>> So a question to you: do you think that it would be good to have a >>> pharo-beginner mailing list? >>> >>> Stef >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Dec. 30, 2009