June 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Trait recent change

by Damien Cassou

On Wed, Jun 11, 2008 at 6:03 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Damien, > > Yes. I recently did a refactoring to reduce the number of traits in the > kernel. That is, most of the traits are flattened down and now are only used > for code reuse between the traits and the classes inheritance branches > (traits count went down from 17 to 6). > > So if your packages change methods in traits that are now gone, you have to > adapt your packages. However, all changes I did are behavior preserving. Thank you -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

June 12, 2008

Re: [Pharo-project] [ANN] New release

by StÃ©phane Ducasse

It is there. http://pharo.gforge.inria.fr/PharoReady.cs

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by StÃ©phane Ducasse

On Jun 12, 2008, at 1:43 AM, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> > wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. > >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. Yes I think that having only one flow of fixes is important. > > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. Yes > > The issue tracker should be the *one* place where you can find what > nees to be done. Yes > > > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". Yes if you have some clearer ideas than me shoot stef > > > Saludos, > > VÃctor RodrÃguez. > > >> Norbert >> >> >> _______________________________________________ >> 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 >

June 12, 2008

Re: [Pharo-project] Bug for harvesting

by StÃ©phane Ducasse

yes you are right. I will ping samuel for a logo and a nice coloring scheme On Jun 11, 2008, at 11:20 PM, Norbert Hartl wrote: > On Wed, 2008-06-11 at 14:50 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 1:12 PM, Norbert Hartl <norbert(a)hartl.name> >> wrote: >>> Hi, >>> >>> I opened a bug a few minutes ago which you may find interesting >>> for harvest. >>> >>> http://bugs.squeak.org/view.php?id=7090 >> >> I have filed this as Issue 13. I left the state as NEW. >> > I don't think it is good to open tickets in two different bug > trackers. I opened it on squeak.org because it is a defect that > doesn't belong to pharo. Things get messed quickly this way. > There is a wiki page MantisBugsHarvested. Why shouldn't we have > another page for bugs supposed to be harvested. They exist for > 3.10 already. > > Norbert > > P.S.: I cannot create pages in the wiki. Can someone add me, please! > The account is my email address. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

It turns a 3.9.1 image into pharo image which is able to receive the pharo update stream. It's just were everything began :) Norbert On Thu, 2008-06-12 at 10:23 +0200, Serge Stinckwich wrote: > Sorry what is the purpose of this file ? > > 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > >> > <stephane.ducasse(a)inria.fr> wrote: > >> > [snip] > >> >> Is is politically really important that we use the inria infrastructure. > >> >> It will help us building Smalltalk presence inside INRIA. > >> >> So at then end we will not use the forge but only the file because we need > >> >> these counters > >> >> at that place :) > >> > > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. > >> > >> I thought things better and just turned the "Downloads" tab into a > >> wiki page to redirect people to the right place. > >> > >> BTW, PharoReady.cs is not available. Stephane, could you please add it? > >> > > I added it. I've put it into the svn and linked it from there. I don't > > think the initial cs has be add inria. > > > > Norbert > > > >> Thanks, > >> > >> Victor. > >> > >> > >> > VÃctor. > >> > > >> >>> I will volunteer again and move all the existing files over. (As a > >> >>> matter of fact, I had been thinking of moving the files then proposing > >> >>> the change, but I just haven't had a chance to do it.) > >> >> > >> >> Please don't there are issues more complex under the surface but this is not > >> >> linked with pharo by itself. > >> >> > >> >>> > >> >>> > >> >>> Victor. > >> >>> > >> >>> > >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >> >>>> > >> >>>>> > >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >> >>>>> "pharo-dev" on the downloads page. > >> >>>>> > >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >> >>>>> > >> >>>>> - on > >> >>>>> > >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >> >>>>> > >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> Great! > >> >>>>>>> > >> >>>>>>> Just noticed two things: > >> >>>>>>> > >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >> >>>>>> > >> >>>>>> > >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >> >>>>>> you want a prepared pharo image for developers. > >> >>>>>> > >> >>>>>> -- > >> >>>>>> Damien Cassou > >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >> >>>>>> > >> >>>>>> _______________________________________________ > >> >>>>>> 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 > >> >>>> > >> >>> > >> >>> _______________________________________________ > >> >>> 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 > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Serge Stinckwich > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://blog.doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Serge Stinckwich

Sorry what is the purpose of this file ? 2008/6/12 Norbert Hartl <norbert(a)hartl.name>: > On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: >> On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: >> > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse >> > <stephane.ducasse(a)inria.fr> wrote: >> > [snip] >> >> Is is politically really important that we use the inria infrastructure. >> >> It will help us building Smalltalk presence inside INRIA. >> >> So at then end we will not use the forge but only the file because we need >> >> these counters >> >> at that place :) >> > >> > Fair enough. I have disabled the "Downloads" tab in googlecode. >> >> I thought things better and just turned the "Downloads" tab into a >> wiki page to redirect people to the right place. >> >> BTW, PharoReady.cs is not available. Stephane, could you please add it? >> > I added it. I've put it into the svn and linked it from there. I don't > think the initial cs has be add inria. > > Norbert > >> Thanks, >> >> Victor. >> >> >> > VÃctor. >> > >> >>> I will volunteer again and move all the existing files over. (As a >> >>> matter of fact, I had been thinking of moving the files then proposing >> >>> the change, but I just haven't had a chance to do it.) >> >> >> >> Please don't there are issues more complex under the surface but this is not >> >> linked with pharo by itself. >> >> >> >>> >> >>> >> >>> Victor. >> >>> >> >>> >> >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: >> >>>> >> >>>>> >> >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under >> >>>>> "pharo-dev" on the downloads page. >> >>>>> >> >>>>> http://gforge.inria.fr/frs/?group_id=1299 >> >>>>> >> >>>>> - on >> >>>>> >> >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: >> >>>>> >> >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> >> >>>>>> wrote: >> >>>>>>> >> >>>>>>> Great! >> >>>>>>> >> >>>>>>> Just noticed two things: >> >>>>>>> >> >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? >> >>>>>> >> >>>>>> >> >>>>>> I think Pharo should not care about such things. Just use pharo-dev if >> >>>>>> you want a prepared pharo image for developers. >> >>>>>> >> >>>>>> -- >> >>>>>> Damien Cassou >> >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >>>>>> >> >>>>>> _______________________________________________ >> >>>>>> 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 >> >>>> >> >>> >> >>> _______________________________________________ >> >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008

Re: [Pharo-project] Pharo, squeak and the tickets

by Serge Stinckwich

2008/6/12 Victor Rodriguez <victorr(a)gmail.com>: > On Wed, Jun 11, 2008 at 5:49 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > [snip] >> What would you prefer? >> >> 1. Opening issues where they belong first and let "the others" >> harvest what they think they need? >> 2. Playing back the issues to bugs.squeak.org if we find a bug >> that belongs also to squeak and bring them back by harvesting? > > This is what I propose: > > * If an issue applies to Squeak, file a report on Mantis. Yes we could be nice with Squeak ;-) >> How do we want to harvest fixes from other places? >> >> 1. Having a wiki page where issues found are written down? >> 2. Opening tickets on the google tracker for this? This would >> be "to harvest" tickets. > > * File an issue for everything we want to do in Pharo in the google > tracker, *including* for "harvesting" fixes in other projects. > > Thus, I would still file an issue on the google tracker for Mantis > reports. Such issues should probably follow a template, and have a > label that indicates their origin (in addition to the description). > > As a matter of fact, I think we should file an issue for every fix > listed in the wiki pages in ThreeDotTenFixes, ThreeDotTenDotOneFixes, > etc.. This way, people can assign to themselves a given fix, and we > can more easily keep a handle on things. > > The issue tracker should be the *one* place where you can find what > nees to be done. I agree with this plan. > BTW, this leads to something else I wanted to bring up. Currently, > "harvest" means two things: 1) Put in Pharo a fix available in Squeak > (or Croquet, etc..); and 2) Move a package from the PharoInbox into > the Pharo update stream. Could we come up with a different name for > 2? Something along the lines of 'integrate', 'validate', 'process', > etc.. "Stephane is processing fix X in the PharoInbox". > Yes and after the vocabulary is fixed, can we document this vocabulary and the harvesting process in the Wiki. I think we need something like a workflow. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 12, 2008

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 18:03, Adrian Lienhard wrote: > IIRC Marcus introduced Behavior>>hash in 3.9 and later realized that > this is not a good idea. The reason is that names of behaviors are > not constant because when a class is deleted its name is changed to > AnAbsolete..., which makes the name not suitable for hashing. > Yes, that was the reason. > Looking through ScriptLoader, #update10020 is where Behavior>>hash > is removed again. Unfortunately the changes log is a bit unspecific > as it mentions only: "changes from Reflectivity"... > I will try to be more specific next time... > Cheers, > Adrian > > On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: > >> >> What was his fix? >> >> How can I tell what was changed? >> >> Is Behaviour>>hash missing in your image too? I don't trust >> anything anymore. >> >> - on >> >> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >> >>> Marcus should have a look since this is fix he reverted. >>> >>> Stef >>> >>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> These tests are fine in Squeak 3.9 too. >>>> >>>> Further investigation reveals that Behaviour>>hash is missing in >>>> Pharo! >>>> >>>> So hash reverts to Object>>hash, which sends Object>>identityHash. >>>> >>>> In Pharo: >>>> >>>> Array hash --> 2455 >>>> Object identityHash --> 2274 >>>> >>>> In Squeak: >>>> >>>> Array hash --> 259007228 >>>> Object identityHash --> 2274 >>>> >>>> Looks like someone removed >>>> >>>> Behaviour>>hash >>>> ^ self name hash >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Excellent! >>>>> may be this is the hash of class that changed. Marcus >>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>> And may be in 3.10 they changed class hash too. >>>>> >>>>> Now I do not know if in 3.9 these tests were broken. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> OK, I investigated more deeply. >>>>>> >>>>>> It appears that SequenceableCollection>>hash behaves >>>>>> differently in Pharo and Squeak 3.10. >>>>>> >>>>>> Squeak: >>>>>> >>>>>> #(1) hash --> 22516953 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> #(1) hash --> 61541560 >>>>>> >>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>> Array>>hash (inherited from SequenceableCollection), this test >>>>>> fails. >>>>>> >>>>>> Not yet sure why these two behave differently ... >>>>>> >>>>>> Already the first line (self species hash) is different: >>>>>> >>>>>> Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> >>>>>> Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> We checked with lukas what is strange is that the same tests >>>>>>> are green in 3.10. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>> Number tests run, and in the Issues page I propose to delete >>>>>>>> a bunch of nonsensical testHash tests. With these changes >>>>>>>> the Kernel tests should all be green. >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>> >> >> >> _______________________________________________ >> 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 Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] Behaviour>>hash is missing!

by Marcus Denker

On 11.06.2008, at 19:11, StÃ©phane Ducasse wrote: > Yes I have the impression that this would be a good things to do > because > they do not have add that much important information. > > Yes, that is my impression too. > On Jun 11, 2008, at 6:11 PM, Oscar Nierstrasz wrote: > >> >> OK, so that is why all these silly testHash tests are broken. They >> depend on Behaviour>>#hash to return a specific hash value. I >> suggest trashing them as the tests are not robust. >> >> - on >> >> >> On Jun 11, 2008, at 6:03 PM, Adrian Lienhard wrote: >> >>> IIRC Marcus introduced Behavior>>hash in 3.9 and later realized >>> that this is not a good idea. The reason is that names of >>> behaviors are not constant because when a class is deleted its >>> name is changed to AnAbsolete..., which makes the name not >>> suitable for hashing. >>> >>> Looking through ScriptLoader, #update10020 is where Behavior>>hash >>> is removed again. Unfortunately the changes log is a bit >>> unspecific as it mentions only: "changes from Reflectivity"... >>> >>> Cheers, >>> Adrian >>> >>> On Jun 10, 2008, at 22:54 , Oscar Nierstrasz wrote: >>> >>>> >>>> What was his fix? >>>> >>>> How can I tell what was changed? >>>> >>>> Is Behaviour>>hash missing in your image too? I don't trust >>>> anything anymore. >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 10:13 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Marcus should have a look since this is fix he reverted. >>>>> >>>>> Stef >>>>> >>>>> On Jun 10, 2008, at 10:04 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> These tests are fine in Squeak 3.9 too. >>>>>> >>>>>> Further investigation reveals that Behaviour>>hash is missing >>>>>> in Pharo! >>>>>> >>>>>> So hash reverts to Object>>hash, which sends >>>>>> Object>>identityHash. >>>>>> >>>>>> In Pharo: >>>>>> >>>>>> Array hash --> 2455 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> In Squeak: >>>>>> >>>>>> Array hash --> 259007228 >>>>>> Object identityHash --> 2274 >>>>>> >>>>>> Looks like someone removed >>>>>> >>>>>> Behaviour>>hash >>>>>> ^ self name hash >>>>>> >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 9:43 PM, StÃ©phane Ducasse wrote: >>>>>> >>>>>>> Excellent! >>>>>>> may be this is the hash of class that changed. Marcus >>>>>>> retrochanged the hash behavior that we harvested in 3.9. >>>>>>> And may be in 3.10 they changed class hash too. >>>>>>> >>>>>>> Now I do not know if in 3.9 these tests were broken. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> On Jun 10, 2008, at 9:32 PM, Oscar Nierstrasz wrote: >>>>>>> >>>>>>>> >>>>>>>> OK, I investigated more deeply. >>>>>>>> >>>>>>>> It appears that SequenceableCollection>>hash behaves >>>>>>>> differently in Pharo and Squeak 3.10. >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> #(1) hash --> 22516953 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> #(1) hash --> 61541560 >>>>>>>> >>>>>>>> Since DateAndTime>>hash is ultimately implemented in terms of >>>>>>>> Array>>hash (inherited from SequenceableCollection), this >>>>>>>> test fails. >>>>>>>> >>>>>>>> Not yet sure why these two behave differently ... >>>>>>>> >>>>>>>> Already the first line (self species hash) is different: >>>>>>>> >>>>>>>> Squeak: >>>>>>>> >>>>>>>> Array hash --> 259007228 >>>>>>>> >>>>>>>> Pharo: >>>>>>>> >>>>>>>> Array hash --> 2455 >>>>>>>> >>>>>>>> - on >>>>>>>> >>>>>>>> On Jun 10, 2008, at 6:34 PM, StÃ©phane Ducasse wrote: >>>>>>>> >>>>>>>>> We checked with lukas what is strange is that the same tests >>>>>>>>> are green in 3.10. >>>>>>>>> >>>>>>>>> Stef >>>>>>>>> >>>>>>>>> On Jun 10, 2008, at 3:48 PM, Oscar Nierstrasz wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I have posted some patches to the inbox to make the Kernel >>>>>>>>>> Number tests run, and in the Issues page I propose to >>>>>>>>>> delete a bunch of nonsensical testHash tests. With these >>>>>>>>>> changes the Kernel tests should all be green. >>>>>>>>>> >>>>>>>>>> - on >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> 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 >>>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

June 12, 2008

Re: [Pharo-project] [ANN] New release

by Norbert Hartl

On Wed, 2008-06-11 at 21:22 -0400, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 7:54 PM, Victor Rodriguez <victorr(a)gmail.com> wrote: > > On Wed, Jun 11, 2008 at 3:51 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > > [snip] > >> Is is politically really important that we use the inria infrastructure. > >> It will help us building Smalltalk presence inside INRIA. > >> So at then end we will not use the forge but only the file because we need > >> these counters > >> at that place :) > > > > Fair enough. I have disabled the "Downloads" tab in googlecode. > > I thought things better and just turned the "Downloads" tab into a > wiki page to redirect people to the right place. > > BTW, PharoReady.cs is not available. Stephane, could you please add it? > I added it. I've put it into the svn and linked it from there. I don't think the initial cs has be add inria. Norbert > Thanks, > > Victor. > > > > VÃctor. > > > >>> I will volunteer again and move all the existing files over. (As a > >>> matter of fact, I had been thinking of moving the files then proposing > >>> the change, but I just haven't had a chance to do it.) > >> > >> Please don't there are issues more complex under the surface but this is not > >> linked with pharo by itself. > >> > >>> > >>> > >>> Victor. > >>> > >>> > >>>> On Jun 11, 2008, at 1:39 PM, Oscar Nierstrasz wrote: > >>>> > >>>>> > >>>>> Ah, I thought it *was* a pharo-dev image -- it was listed under > >>>>> "pharo-dev" on the downloads page. > >>>>> > >>>>> http://gforge.inria.fr/frs/?group_id=1299 > >>>>> > >>>>> - on > >>>>> > >>>>> On Jun 11, 2008, at 11:12, Damien Cassou wrote: > >>>>> > >>>>>> On Wed, Jun 11, 2008 at 9:56 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> > >>>>>> wrote: > >>>>>>> > >>>>>>> Great! > >>>>>>> > >>>>>>> Just noticed two things: > >>>>>>> > >>>>>>> - Test Runner is missing from the Tools flap -- shouldn't it be there? > >>>>>> > >>>>>> > >>>>>> I think Pharo should not care about such things. Just use pharo-dev if > >>>>>> you want a prepared pharo image for developers. > >>>>>> > >>>>>> -- > >>>>>> Damien Cassou > >>>>>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > >>>>>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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 > >>>> > >>> > >>> _______________________________________________ > >>> 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

June 12, 2008