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

Re: [Pharo-project] DictionaryTest

by Alexandre Bergel

I took the last version of Pharo, and loading my change. I will publish it. Alexandre On 5 Jan 2009, at 13:14, StÃ©phane Ducasse wrote: > Alex > > I do not really understand since 139, 138 are also empty when I browse > them via the squeaksource web ui > I can move everything to treated and you republish the package. > I really want to see this code can you send to me a package via email? > > Stef > > On Jan 5, 2009, at 3:58 PM, Lukas Renggli wrote: > >>> If I browse the file CollectionsTests-AlexandreBergel.140 within >>> Squeak stored on PharoInbox, I see the content. If I go on >>> squeaksource, and look the content of the version that I saved, it >>> is >>> empty. I tried to save CollectionTests, but the content is empty. >>> Any >>> hint? >> >> The Pharo image uses the cache in memory or on your file-system to >> display mcz files you recently committed. You should ask an >> administrator of the PharoInbox to delete the defective version from >> the repository and try to copy your local version to squeaksource.com >> again. >> >> Lukas >> >> -- >> Lukas Renggli >> http://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 >> > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by StÃ©phane Ducasse

Alex I do not really understand since 139, 138 are also empty when I browse them via the squeaksource web ui I can move everything to treated and you republish the package. I really want to see this code can you send to me a package via email? Stef On Jan 5, 2009, at 3:58 PM, Lukas Renggli wrote: >> If I browse the file CollectionsTests-AlexandreBergel.140 within >> Squeak stored on PharoInbox, I see the content. If I go on >> squeaksource, and look the content of the version that I saved, it is >> empty. I tried to save CollectionTests, but the content is empty. Any >> hint? > > The Pharo image uses the cache in memory or on your file-system to > display mcz files you recently committed. You should ask an > administrator of the PharoInbox to delete the defective version from > the repository and try to copy your local version to squeaksource.com > again. > > Lukas > > -- > Lukas Renggli > http://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 >

Jan. 5, 2009

Re: [Pharo-project] #traits

by Damien Cassou

On Mon, Jan 5, 2009 at 1:45 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I wanted to know if we could not have > traits defined in Behavior and whose behavior would be > > self traitComposition allTraits > > BTW will you have some time to look at my improvements? http://code.google.com/p/pharo/issues/detail?id=433 I propose to send #traits instead of #allTraits. #traits returns the collection of traits used in a behavior whereas #allTraits also returns the traits that are used by those traits. -- Damien Cassou http://damiencassou.seasidehosting.st

Jan. 5, 2009

Re: [Pharo-project] Collection extensions

by Piers Cawley

On Mon, Jan 5, 2009 at 3:06 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Jan 5, 2009, at 3:56 PM, Lukas Renggli wrote: > >>> I published to the inbox some cool collection extension methods that >>> we use all the time in Moose. >>> flatCollect:, collectAsSet:, and groupedBy: >> >> I think Squeak already has far too many of these methods. I would >> rather like to see them all removed, than new ones added. As an author >> and maintainer of many Smalltalk framework I experience daily the pain >> such methods cause, as they are inherently non-portable not only >> between smalltalk dialects but even between users of exactly the same >> image. > > But these ones are since they are coming from VisualWorks. > >> Let me give you an example: Seaside used >> SequenceableCollection>>#pairsDo: in various places. The we got >> complaints that almost all Smalltalk platforms already provide such a >> method, but they all implement it entirely different. Some iterate >> over the combinatorial pairs, some over the consecutive pairs, some >> ignore an odd number of arguments, some raise an exception, etc. At >> some point we learned that a famous company using Seaside has their >> own proprietary override of this method. Today we use the ANSI >> #to:do:. It is ugly, but it works everywhere as it is part of ANSI >> Smalltalk. > > So why do we do pharo. Really. If everything as to be compatible with > other > smalltalk. Terrible. > Can't we get smarter? > Why can't we tag the methods with <notAnsi> and build a tool that > check when you > do a fill out. I do not write code to be portable to VisualWorks so? > >> I would prefer to have such extension methods separate from the core. > > Me not. Because then in a lot of places I will have to inline their > body. Would it not be possible to implement a macro refactoring at a package level that walks the package looking for non ANSI compatible messages sent to collections and suggests appropriate inlinings to make things compliant (or at least flags up problematic methods). That way implementers who use Pharo as their development platform can work with the Pharo specific extensions as they develop, but can publish variants of the code that are ANSI compliant. No, I don't have the skills to implement such a thing, but I'm sure they could be acquired.

Jan. 5, 2009

Re: [Pharo-project] Collection extensions

by StÃ©phane Ducasse

On Jan 5, 2009, at 3:56 PM, Lukas Renggli wrote: >> I published to the inbox some cool collection extension methods that >> we use all the time in Moose. >> flatCollect:, collectAsSet:, and groupedBy: > > I think Squeak already has far too many of these methods. I would > rather like to see them all removed, than new ones added. As an author > and maintainer of many Smalltalk framework I experience daily the pain > such methods cause, as they are inherently non-portable not only > between smalltalk dialects but even between users of exactly the same > image. But these ones are since they are coming from VisualWorks. > Let me give you an example: Seaside used > SequenceableCollection>>#pairsDo: in various places. The we got > complaints that almost all Smalltalk platforms already provide such a > method, but they all implement it entirely different. Some iterate > over the combinatorial pairs, some over the consecutive pairs, some > ignore an odd number of arguments, some raise an exception, etc. At > some point we learned that a famous company using Seaside has their > own proprietary override of this method. Today we use the ANSI > #to:do:. It is ugly, but it works everywhere as it is part of ANSI > Smalltalk. So why do we do pharo. Really. If everything as to be compatible with other smalltalk. Terrible. Can't we get smarter? Why can't we tag the methods with <notAnsi> and build a tool that check when you do a fill out. I do not write code to be portable to VisualWorks so? > I would prefer to have such extension methods separate from the core. Me not. Because then in a lot of places I will have to inline their body. Stef

Jan. 5, 2009

Re: [Pharo-project] Collection extensions

by Alexandre Bergel

Maybe some lint rules could detect the usage of non portable methods... Alexandre On 5 Jan 2009, at 11:56, Lukas Renggli wrote: >> I published to the inbox some cool collection extension methods that >> we use all the time in Moose. >> flatCollect:, collectAsSet:, and groupedBy: > > I think Squeak already has far too many of these methods. I would > rather like to see them all removed, than new ones added. As an author > and maintainer of many Smalltalk framework I experience daily the pain > such methods cause, as they are inherently non-portable not only > between smalltalk dialects but even between users of exactly the same > image. > > Let me give you an example: Seaside used > SequenceableCollection>>#pairsDo: in various places. The we got > complaints that almost all Smalltalk platforms already provide such a > method, but they all implement it entirely different. Some iterate > over the combinatorial pairs, some over the consecutive pairs, some > ignore an odd number of arguments, some raise an exception, etc. At > some point we learned that a famous company using Seaside has their > own proprietary override of this method. Today we use the ANSI > #to:do:. It is ugly, but it works everywhere as it is part of ANSI > Smalltalk. > > I would prefer to have such extension methods separate from the core. > > Lukas > > -- > Lukas Renggli > http://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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by Lukas Renggli

> If I browse the file CollectionsTests-AlexandreBergel.140 within > Squeak stored on PharoInbox, I see the content. If I go on > squeaksource, and look the content of the version that I saved, it is > empty. I tried to save CollectionTests, but the content is empty. Any > hint? The Pharo image uses the cache in memory or on your file-system to display mcz files you recently committed. You should ask an administrator of the PharoInbox to delete the defective version from the repository and try to copy your local version to squeaksource.com again. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 5, 2009

Re: [Pharo-project] Collection extensions

by Lukas Renggli

> I published to the inbox some cool collection extension methods that > we use all the time in Moose. > flatCollect:, collectAsSet:, and groupedBy: I think Squeak already has far too many of these methods. I would rather like to see them all removed, than new ones added. As an author and maintainer of many Smalltalk framework I experience daily the pain such methods cause, as they are inherently non-portable not only between smalltalk dialects but even between users of exactly the same image. Let me give you an example: Seaside used SequenceableCollection>>#pairsDo: in various places. The we got complaints that almost all Smalltalk platforms already provide such a method, but they all implement it entirely different. Some iterate over the combinatorial pairs, some over the consecutive pairs, some ignore an odd number of arguments, some raise an exception, etc. At some point we learned that a famous company using Seaside has their own proprietary override of this method. Today we use the ANSI #to:do:. It is ugly, but it works everywhere as it is part of ANSI Smalltalk. I would prefer to have such extension methods separate from the core. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by Alexandre Bergel

That's very strange... If I browse the file CollectionsTests-AlexandreBergel.140 within Squeak stored on PharoInbox, I see the content. If I go on squeaksource, and look the content of the version that I saved, it is empty. I tried to save CollectionTests, but the content is empty. Any hint? Alexandre On 5 Jan 2009, at 11:10, StÃ©phane Ducasse wrote: > alex > > it seems that your package is empty. > can you check. > > Stef > On Jan 5, 2009, at 1:14 PM, Alexandre Bergel wrote: > >> New tests on DictionaryTest. The method categories accesssing, >> adding, >> comparing, enumerating, printing, removing, and testing are covered. >> This represents a coreverage of 66% >> >> In PharoInbox. I am continuing the coverage... >> >> 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009

Re: [Pharo-project] DictionaryTest

by Alexandre Bergel

That's very strange... If I browse the file CollectionsTests-AlexandreBergel.140 within Squeak stored on PharoInbox, I see the content. If I go on squeaksource, and look the content of the version that I saved, it is empty. I tried to save CollectionTests, but the content is empty. Any hint? Alexandre On 5 Jan 2009, at 11:10, StÃ©phane Ducasse wrote: > alex > > it seems that your package is empty. > can you check. > > Stef > On Jan 5, 2009, at 1:14 PM, Alexandre Bergel wrote: > >> New tests on DictionaryTest. The method categories accesssing, >> adding, >> comparing, enumerating, printing, removing, and testing are covered. >> This represents a coreverage of 66% >> >> In PharoInbox. I am continuing the coverage... >> >> 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 5, 2009