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

Re: [Pharo-project] Acire

by laurent laffont

Hi, take a look at ProfStefBrowser package in ProfStef repository. I should include it in ConfigurationfOfProfStef for Pharo 1.1. Maybe we can enhance it.... Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Mon, May 10, 2010 at 1:06 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Maybe we should enhance ProfStef with a list on the left > side and the transcript included at the bottom: > > > http://rickwagner.blogspot.com/2010/05/every-programming-language-should-ha… > > ;) > > Bye > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 10, 2010

[Pharo-project] [update 1.1] #11348

by StÃ©phane Ducasse

11348 ----- - Issue 2401: reduce: or fold: - made change events of MCPackageManager and MCRepositoryGroup a bit more useful Stef

May 10, 2010

[Pharo-project] Acire

by Torsten Bergmann

Maybe we should enhance ProfStef with a list on the left side and the transcript included at the bottom: http://rickwagner.blogspot.com/2010/05/every-programming-language-should-ha… ;) Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 10, 2010

Re: [Pharo-project] Bug PackageInfo >> classes return also Traits

by StÃ©phane Ducasse

not for 1.1 guy. it worked so far.... so let us finish 1.1 On May 10, 2010, at 11:15 AM, Mariano Martinez Peck wrote: > Hi folks. I've just discovered that PackageInfo >> classes return a collection of classes AND traits. This is incorrect. Solutions are: > > 1) Rename #classes to #classesAndTraits > 2) Modify #classes so that it ONLY answer classes > > I would like to fix it but I am not sure the consequences of such change. Maybe Monticello doesn't take into account Traits anymore hahha > > Thanks for any help you can give. > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 10, 2010

Re: [Pharo-project] add return its argument

by StÃ©phane Ducasse

consistency and this is linked to the work of nicolas to do the same in Squeak. Stef On May 10, 2010, at 10:06 AM, Norbert Hartl wrote: > I don't have time to scan the mailing list in detail. Was there any discussion that led to this change? Any pointers appreciated. I always thought the comfort of being able to chain selectors like add: outweighs the uniformity. > > Norbert > > On 08.05.2010, at 17:31, stephane ducasse wrote: > >> if somebody wants to check that the fixes I made are ok >> and that at:put: and add: return their arguments >> >> >> <addReturnValue.1.cs> >> >> 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

May 10, 2010

Re: [Pharo-project] Bug PackageInfo >> classes return also Traits

by Mariano Martinez Peck

On Mon, May 10, 2010 at 11:18 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > > Hi folks. I've just discovered that PackageInfo >> classes return a > > collection of classes AND traits. This is incorrect. > > Why is this wrong? Collections are mostly polymorphic to traits. > > I think they are not the same. Even if they are "mostly" polymorphic they are different things. They are not classes. If I ask classes, I want classes. Otherwise I will ask classesAndTraits or just behaviors, but not classes. That's why there are #allClasses, #allClassesAndTraits, #allBehaviorsDo: etc In addition, it is not uniform. It is confusing having places where you have #allClassesAndTraits (here you understand the allClasses doesn't take into account traits) and then you PackageInfo >> classes that answer all the classes but also traits. Cheers Mariano > > Solutions are: > > > > 1) Rename #classes to #classesAndTraits > > 2) Modify #classes so that it ONLY answer classes > > > > I would like to fix it but I am not sure the consequences of such change. > > Maybe Monticello doesn't take into account Traits anymore hahha > > Yes, all users of PackageInfo will break. > > Lukas > > -- > 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 >

May 10, 2010

Re: [Pharo-project] Bug PackageInfo >> classes return also Traits

by Lukas Renggli

>> Hi folks. I've just discovered that PackageInfo >> classesÂ return a >> collection of classes AND traits. This is incorrect. > > Why is this wrong? Collections are mostly polymorphic to traits. Ehh, classes are mostly polymorphic to traits. Lukas > >> Solutions are: >> >> 1) Rename #classes to #classesAndTraits >> 2) Modify #classes so that it ONLY answer classes >> >> I would like to fix it but I am not sure the consequences of such change. >> Maybe Monticello doesn't take into account Traits anymore hahha > > Yes, all users of PackageInfo will break. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

May 10, 2010

Re: [Pharo-project] Bug PackageInfo >> classes return also Traits

by Lukas Renggli

> Hi folks. I've just discovered that PackageInfo >> classesÂ return a > collection of classes AND traits. This is incorrect. Why is this wrong? Collections are mostly polymorphic to traits. > Solutions are: > > 1) Rename #classes to #classesAndTraits > 2) Modify #classes so that it ONLY answer classes > > I would like to fix it but I am not sure the consequences of such change. > Maybe Monticello doesn't take into account Traits anymore hahha Yes, all users of PackageInfo will break. Lukas -- Lukas Renggli www.lukas-renggli.ch

May 10, 2010

[Pharo-project] Bug PackageInfo >> classes return also Traits

by Mariano Martinez Peck

Hi folks. I've just discovered that PackageInfo >> classes return a collection of classes AND traits. This is incorrect. Solutions are: 1) Rename #classes to #classesAndTraits 2) Modify #classes so that it ONLY answer classes I would like to fix it but I am not sure the consequences of such change. Maybe Monticello doesn't take into account Traits anymore hahha Thanks for any help you can give. Mariano

May 10, 2010

Re: [Pharo-project] add return its argument

by Norbert Hartl

I don't have time to scan the mailing list in detail. Was there any discussion that led to this change? Any pointers appreciated. I always thought the comfort of being able to chain selectors like add: outweighs the uniformity. Norbert On 08.05.2010, at 17:31, stephane ducasse wrote: > if somebody wants to check that the fixes I made are ok > and that at:put: and add: return their arguments > > > <addReturnValue.1.cs> > > Stef_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 10, 2010