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

[Pharo-project] Fwd: Comment on BrokenTests in pharo

by Pharo Smalltalk

My apologies if this message is forwarded to the list twice. Victor Rodriguez. ---------- Forwarded message ---------- From: <codesite-noreply(a)google.com> Date: Wed, Jun 11, 2008 at 12:05 PM Subject: Comment on BrokenTests in pharo To: pharo.smalltalk(a)gmail.com Comment by oscar.nierstrasz: FloatTests>>#testNaN5 currently reads as follows: {{{ testNaN5 "self assert: (Float nan asIEEE32BitWord printPaddedWith: $0 to: 32 base: 2) = '01111111110000000000000000000000'." ... }}} I believe this is over-specified. Instead it should just read as follows: {{{ testNaN5 self assert: ((Float nan asIEEE32BitWord printPaddedWith: $0 to: 32 base: 2) copyFrom: 2 to: 9) = '11111111'. ... }}} This would be consistent with the NaN spec (according to wikipedia). However it does not explain why these tests pass in 3.9 and 3.10. Have there been changes in the VM to the way that Floats are represented? For more information: http://code.google.com/p/pharo/wiki/BrokenTests

June 12, 2008

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

by Victor Rodriguez

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? 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 >> >

June 12, 2008

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

by Victor Rodriguez

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. 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 >

June 11, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Victor Rodriguez

On Wed, Jun 11, 2008 at 5:08 PM, Norbert Hartl <norbert(a)hartl.name> wrote: [snip] > Yes, I'll open a ticket. I think we are using google. So after all > we use: > > - google for wiki and bugs > - inria for file downloads > - squeaksource for code upload - inria for the mailing list. VÃctor. > > we seem not to use: > > - bugs.squeak.org (we should someone remove the project from there) > > Norbert >> I will ask samuel if he has some ideas for the logo because we should >> move on >> for the infrastructure of the web site (I'm sorry about the current >> state of affair). >> >> >> On Jun 11, 2008, at 7:43 PM, Norbert Hartl wrote: >> >> > Hmmm, it has something to do with the name pharo :) I checked >> > the available images. Sapphire 10018 doesn't show up this. But >> > Pharo 10021 does. And in 10021 there is one additional test in >> > ClassTest >> > >> > testHaSharedPools >> > >> > Author seems to be Stephane. Do you know anything which have >> > introduced this? >> > >> > Norbert >> > >> > >> > On Wed, 2008-06-11 at 19:24 +0200, Norbert Hartl wrote: >> >> If you open a test runner and select only KernelTests-ClassTest and >> >> TraitsTests-TraitsTestCase you may find a failure >> >> >> >> ClassTest>>testRootsOfTheWorld >> >> >> >> But I don't understand fully why it appears. I had once >> >> the chance to get a debugger on the failure (which does >> >> usually not work on this failure) and so I know that the >> >> rootsOfTheWorld (which is usually 3) is 6 in size containing >> >> additionally classes C3 C4 and C6. The ones which are created >> >> by TraitsTestCase (see my last mail "Bug for harvest"). >> >> >> >> They all have a superclass of nil but they aren't included >> >> in the SystemNavigation. (conditions for being included in >> >> the rootsOfTheWorld) >> >> >> >> If you press "Run selected" again the same error occurrs >> >> while pressing "Run failures" gives you all green (ok, it >> >> is this way in my case) >> >> >> >> And I can't reproduce the same in a 3.10 image. >> >> >> >> It seems that there is a timing problem involved. Selecting >> >> only the two test cases I get the failure every time (or nearly). >> >> Selecting all tests it appears only at random. >> >> >> >> Any hints? >> >> >> >> 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 >> > >> >> >> _______________________________________________ >> 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 11, 2008

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

by Victor Rodriguez

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. 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. 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". 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 >

June 11, 2008

[Pharo-project] Pharo, squeak and the tickets

by Norbert Hartl

I had a look at the tickets in the google tracker. A lot of them appear to me that they belong to squeak as well. I'm quite unsure what would be the best way to deal with both sides (pharo and squeak) because there are bugs found through working on pharo that belong to squeak as well. On the other hand we harvest things from squeak. 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? 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. Norbert

June 11, 2008

Re: [Pharo-project] Bug for harvesting

by Serge Stinckwich

2008/6/11 Norbert Hartl <norbert(a)hartl.name>: > 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. I add you. -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 11, 2008

Re: [Pharo-project] Bug for harvesting

by Norbert Hartl

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.

June 11, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Norbert Hartl

On Wed, 2008-06-11 at 21:50 +0200, StÃ©phane Ducasse wrote: > No may be this is related with the hash fixes of marcus. I will have > to check :) > Thanks for reporting that. > Can you add that in a bug tracking system? > Which one do we use? > Yes, I'll open a ticket. I think we are using google. So after all we use: - google for wiki and bugs - inria for file downloads - squeaksource for code upload we seem not to use: - bugs.squeak.org (we should someone remove the project from there) Norbert > I will ask samuel if he has some ideas for the logo because we should > move on > for the infrastructure of the web site (I'm sorry about the current > state of affair). > > > On Jun 11, 2008, at 7:43 PM, Norbert Hartl wrote: > > > Hmmm, it has something to do with the name pharo :) I checked > > the available images. Sapphire 10018 doesn't show up this. But > > Pharo 10021 does. And in 10021 there is one additional test in > > ClassTest > > > > testHaSharedPools > > > > Author seems to be Stephane. Do you know anything which have > > introduced this? > > > > Norbert > > > > > > On Wed, 2008-06-11 at 19:24 +0200, Norbert Hartl wrote: > >> If you open a test runner and select only KernelTests-ClassTest and > >> TraitsTests-TraitsTestCase you may find a failure > >> > >> ClassTest>>testRootsOfTheWorld > >> > >> But I don't understand fully why it appears. I had once > >> the chance to get a debugger on the failure (which does > >> usually not work on this failure) and so I know that the > >> rootsOfTheWorld (which is usually 3) is 6 in size containing > >> additionally classes C3 C4 and C6. The ones which are created > >> by TraitsTestCase (see my last mail "Bug for harvest"). > >> > >> They all have a superclass of nil but they aren't included > >> in the SystemNavigation. (conditions for being included in > >> the rootsOfTheWorld) > >> > >> If you press "Run selected" again the same error occurrs > >> while pressing "Run failures" gives you all green (ok, it > >> is this way in my case) > >> > >> And I can't reproduce the same in a 3.10 image. > >> > >> It seems that there is a timing problem involved. Selecting > >> only the two test cases I get the failure every time (or nearly). > >> Selecting all tests it appears only at random. > >> > >> Any hints? > >> > >> 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 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2008

Re: [Pharo-project] Bug for harvesting

by StÃ©phane Ducasse

thanks for that. Adrian will certainly have a look since he implemented traits :) Stef On Jun 11, 2008, at 7:12 PM, Norbert Hartl 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 > > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

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

by StÃ©phane Ducasse

On Jun 11, 2008, at 8:44 PM, Victor Rodriguez wrote: > On Wed, Jun 11, 2008 at 1:01 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> yes my mistake >> this interface is just crap. > > Are you referring to the INRIA Pharo project page? If so, why don't > we move the files to google code? 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 :) > 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 >

June 11, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by StÃ©phane Ducasse

No may be this is related with the hash fixes of marcus. I will have to check :) Thanks for reporting that. Can you add that in a bug tracking system? Which one do we use? I will ask samuel if he has some ideas for the logo because we should move on for the infrastructure of the web site (I'm sorry about the current state of affair). On Jun 11, 2008, at 7:43 PM, Norbert Hartl wrote: > Hmmm, it has something to do with the name pharo :) I checked > the available images. Sapphire 10018 doesn't show up this. But > Pharo 10021 does. And in 10021 there is one additional test in > ClassTest > > testHaSharedPools > > Author seems to be Stephane. Do you know anything which have > introduced this? > > Norbert > > > On Wed, 2008-06-11 at 19:24 +0200, Norbert Hartl wrote: >> If you open a test runner and select only KernelTests-ClassTest and >> TraitsTests-TraitsTestCase you may find a failure >> >> ClassTest>>testRootsOfTheWorld >> >> But I don't understand fully why it appears. I had once >> the chance to get a debugger on the failure (which does >> usually not work on this failure) and so I know that the >> rootsOfTheWorld (which is usually 3) is 6 in size containing >> additionally classes C3 C4 and C6. The ones which are created >> by TraitsTestCase (see my last mail "Bug for harvest"). >> >> They all have a superclass of nil but they aren't included >> in the SystemNavigation. (conditions for being included in >> the rootsOfTheWorld) >> >> If you press "Run selected" again the same error occurrs >> while pressing "Run failures" gives you all green (ok, it >> is this way in my case) >> >> And I can't reproduce the same in a 3.10 image. >> >> It seems that there is a timing problem involved. Selecting >> only the two test cases I get the failure every time (or nearly). >> Selecting all tests it appears only at random. >> >> Any hints? >> >> 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 11, 2008

Re: [Pharo-project] Bug for harvesting

by Victor Rodriguez

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. Saludos, Victor. > Norbert > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

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

by Victor Rodriguez

On Wed, Jun 11, 2008 at 1:01 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > yes my mistake > this interface is just crap. Are you referring to the INRIA Pharo project page? If so, why don't we move the files to google code? 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.) 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 >

June 11, 2008

Re: [Pharo-project] Strange bug in TraitsTest

by Norbert Hartl

Hmmm, it has something to do with the name pharo :) I checked the available images. Sapphire 10018 doesn't show up this. But Pharo 10021 does. And in 10021 there is one additional test in ClassTest testHaSharedPools Author seems to be Stephane. Do you know anything which have introduced this? Norbert On Wed, 2008-06-11 at 19:24 +0200, Norbert Hartl wrote: > If you open a test runner and select only KernelTests-ClassTest and > TraitsTests-TraitsTestCase you may find a failure > > ClassTest>>testRootsOfTheWorld > > But I don't understand fully why it appears. I had once > the chance to get a debugger on the failure (which does > usually not work on this failure) and so I know that the > rootsOfTheWorld (which is usually 3) is 6 in size containing > additionally classes C3 C4 and C6. The ones which are created > by TraitsTestCase (see my last mail "Bug for harvest"). > > They all have a superclass of nil but they aren't included > in the SystemNavigation. (conditions for being included in > the rootsOfTheWorld) > > If you press "Run selected" again the same error occurrs > while pressing "Run failures" gives you all green (ok, it > is this way in my case) > > And I can't reproduce the same in a 3.10 image. > > It seems that there is a timing problem involved. Selecting > only the two test cases I get the failure every time (or nearly). > Selecting all tests it appears only at random. > > Any hints? > > Norbert > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2008

[Pharo-project] Strange bug in TraitsTest

by Norbert Hartl

If you open a test runner and select only KernelTests-ClassTest and TraitsTests-TraitsTestCase you may find a failure ClassTest>>testRootsOfTheWorld But I don't understand fully why it appears. I had once the chance to get a debugger on the failure (which does usually not work on this failure) and so I know that the rootsOfTheWorld (which is usually 3) is 6 in size containing additionally classes C3 C4 and C6. The ones which are created by TraitsTestCase (see my last mail "Bug for harvest"). They all have a superclass of nil but they aren't included in the SystemNavigation. (conditions for being included in the rootsOfTheWorld) If you press "Run selected" again the same error occurrs while pressing "Run failures" gives you all green (ok, it is this way in my case) And I can't reproduce the same in a 3.10 image. It seems that there is a timing problem involved. Selecting only the two test cases I get the failure every time (or nearly). Selecting all tests it appears only at random. Any hints? Norbert

June 11, 2008

[Pharo-project] Bug for harvesting

by Norbert Hartl

Hi, I opened a bug a few minutes ago which you may find interesting for harvest. http://bugs.squeak.org/view.php?id=7090 Norbert

June 11, 2008

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

by StÃ©phane Ducasse

Yes I have the impression that this would be a good things to do because they do not have add that much important information. 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 >

June 11, 2008

Re: [Pharo-project] Broken tests

by StÃ©phane Ducasse

excellent! Stef On Jun 11, 2008, at 4:04 PM, Oscar Nierstrasz wrote: > > Just for phun, I ran all the tests in the Pharo image. There are > only 13 failures, 2 expected failures, and no errors! > > I have started a page to give an overview: > > http://code.google.com/p/pharo/wiki/BrokenTests > > Please update this page with an appropriate comment if you are > working on any of these (or if you fix them). > > - on > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

Re: [Pharo-project] New pharo-dev based on latest release

by StÃ©phane Ducasse

thanks a lot. I cleaned my mess. Stef On Jun 11, 2008, at 1:17 PM, Damien Cassou wrote: > I've just published a new pharo-dev based on 10036: > https://gforge.inria.fr/frs/download.php/4978/pharo0.1-10036dev08.06.2.zip > > -- > 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 >

June 11, 2008

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

by StÃ©phane Ducasse

yes my mistake this interface is just crap. 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 >

June 11, 2008

Re: [Pharo-project] HaveALookAt

by StÃ©phane Ducasse

I got some problems with the bootstrap. I think that it would be great to have an effort for another milestone and make it rock solid and integrated. Stef > This is an effort I started few years ago. > I loaded the it recently, and all tests but one go green. > > I will work on it, I hope soon... > > Alexandre > > > On 10 Jun 2008, at 09:58, Norbert Hartl wrote: > >> I think the link to the packages issue should point to >> >> http://www.squeaksource.com/PackagesForSqueak/ >> >> Norbert >> >> >> _______________________________________________ >> 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

[Pharo-project] MVC removal step2 investigations

by Alain Plantec

Hi all, below is given a minute that briefly describes what I suggest for MVC removal. It's an aggressive update especially because a lot of classes are removed. (see all *ST80* system categories before and after having applied the patch and see Controller hierarchy also) I've attached the .cs. Maybe you can make a try and give your opinion. thanks alain MVC removal step2 proposition 1 : * Object>>couldOpenInMorphic : senders updated and method set as deprecated (as for Project>>isMorphic and SystemDictionary>>isMorphic) * Remove method openAsMVC and openInMVC * ST80-Editors system category seems removeable o BitEditor, FormEditor and al : are strongly related to MVC and seems not used * ScheduledControllers : o Remove all methods which are referencing it, this leads to remove class ControlManager; o Remove ControlManager refs in SystemDictionary>>initialize and o cleanup StartUpList and ShutDownList SystemDictionary class variables with a script. * ST80-Framework system category seems removeable o View class seems removable (see ST80-Views system category point) o Then, ModalController, NoController are not referenced anymore, they can be removed o WindowingTransformation is only used by GraphicSymbolInstance which is removable (see ST80-Symbols system category point) * ST80-Views system category can be removed: o StandardSystemView>>Comment: "I represent a view that has a label above its top left corner. The text in the label identifies the kind of view. In addition to a label, I add control over the maximum and minimum size of the display box of my instance. My default controller is StandardSystemController. The elements of ScheduledControllers, the sole instance of ControlManager, are usually controllers for instances of me". o StandardSystemView hierarchy seems removable, (subclasses are ColorSystemView, ModalSystemWindowView, PluggableFileListView and ProjectView ) o MorphWorldView class removed * ST80-Pluggable Views system category o PluggableListView removed * ST80-Symbols system category seems removable o GraphicSymbol and GraphicSymbolInstance are not refed and have no instance, seems removable * WorldViewModel, MVCWiWPasteUpMorph, MorphWorldController and CautiousModel: all these classes are not used, to be removed o MorphicExtras-ST80 system category is then removed * ST80-Support system category o StandardSystemController class>>initialize removed: it only initialize unused class variables HBorderCursor, ScheduledBlueButtonMenu ScheduledBlueButtonMessages and VBorderCursor (these class variables are removed) o StandardSystemController: remove all methods that are related to view (mvc view) o StandardSystemController: class seems to be unused, therefore removed o FillInTheBlankController: class removed o ColorSystemView: class removed * ST80-Kernel-Remnants o Controller and its subclasses: remove all methods that are related to view (mvc view) o Controler: MinActivityLapse class variable seems unused o ControlManager seems removeable o ScrollController seems removeable o MouseMenuController seems removeable * Remove all view classes refs: o SelectorBrowser>>classListIndex: depends on PluggableListView o Browser>>couldBrowseAnyClass depends on PluggableListView * Kernel-ST80 Remnants o ParagraphEditor and TextMorphEditor: kept but have to be cleaned up * ST80-Pluggable Views system category removed * Preferences o removed #mvcProjectsAllowed from flags dictionary * MorphicExtras-ST80 o MorphWorldController class removed * ParagraphEditor o made direct subclass of Controller (get rid of MouseMenuController) o renoved view instance variable o TextMorphEditor is the unique ParagraphEditor subclass, maybe we should only have one class now (ParagraphEditor was more for mvc ?)

June 11, 2008

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

by Oscar Nierstrasz

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 >

June 11, 2008

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

by Adrian Lienhard

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

June 11, 2008

Re: [Pharo-project] Trait recent change

by Adrian Lienhard

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. Cheers, Adrian On Jun 11, 2008, at 12:34 , Damien Cassou wrote: > Hi, > > I'm building a new pharo dev and get a message about missing > TCommentDescription. Is it normal? > > -- > 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

June 11, 2008

[Pharo-project] Broken tests

by Oscar Nierstrasz

Just for phun, I ran all the tests in the Pharo image. There are only 13 failures, 2 expected failures, and no errors! I have started a page to give an overview: http://code.google.com/p/pharo/wiki/BrokenTests Please update this page with an appropriate comment if you are working on any of these (or if you fix them). - on

June 11, 2008

[Pharo-project] Re: New pharo-dev based on latest release

by Damien Cassou

On Wed, Jun 11, 2008 at 1:17 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I've just published a new pharo-dev based on 10036: > https://gforge.inria.fr/frs/download.php/4978/pharo0.1-10036dev08.06.2.zip A pharo-web is also downloadable at: https://gforge.inria.fr/frs/download.php/4985/pharo0.1-10036web08.06.2.zip -- 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 11, 2008

Re: [Pharo-project] New pharo-dev based on latest release

by Damien Cassou

On Wed, Jun 11, 2008 at 1:41 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > Why does the Installer package continue to show up as being out-of-date in > the Monticello browser in this image? I don't know -- 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 11, 2008

Re: [Pharo-project] New pharo-dev based on latest release

by Damien Cassou

On Wed, Jun 11, 2008 at 1:37 PM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > Why are both images grouped under "pharo-dev"? > > http://gforge.inria.fr/frs/?group_id=1299 I guess StÃ©phane did a mistake when release the previous file. I sent him an email already. -- 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 11, 2008

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

by Serge Stinckwich

I think there to much different stuff at the same place : Pharo, Pharo-dev, fonts (?), SBE, ... Could we put the Pharo downloads alone somewhere ? 2008/6/11 Oscar Nierstrasz <oscar(a)iam.unibe.ch>: > > 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 > -- Serge Stinckwich Smalltalkers do: [:it | All with: Class, (And love: it)] http://blog.doesnotunderstand.org/

June 11, 2008

Re: [Pharo-project] New pharo-dev based on latest release

by Oscar Nierstrasz

Why does the Installer package continue to show up as being out-of- date in the Monticello browser in this image? - on On Jun 11, 2008, at 13:17, Damien Cassou wrote: > I've just published a new pharo-dev based on 10036: > https://gforge.inria.fr/frs/download.php/4978/pharo0.1-10036dev08.06.2.zip > > -- > 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 >

June 11, 2008

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

by Oscar Nierstrasz

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 >

June 11, 2008

Re: [Pharo-project] New pharo-dev based on latest release

by Oscar Nierstrasz

Why are both images grouped under "pharo-dev"? http://gforge.inria.fr/frs/?group_id=1299 - on On Jun 11, 2008, at 13:17, Damien Cassou wrote: > I've just published a new pharo-dev based on 10036: > https://gforge.inria.fr/frs/download.php/4978/pharo0.1-10036dev08.06.2.zip > > -- > 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 >

June 11, 2008

[Pharo-project] New pharo-dev based on latest release

by Damien Cassou

I've just published a new pharo-dev based on 10036: https://gforge.inria.fr/frs/download.php/4978/pharo0.1-10036dev08.06.2.zip -- 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 11, 2008

[Pharo-project] Trait recent change

by Damien Cassou

Hi, I'm building a new pharo dev and get a message about missing TCommentDescription. Is it normal? -- 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 11, 2008

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

by Damien Cassou

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)

June 11, 2008

Re: [Pharo-project] HaveALookAt

by Alexandre Bergel

This is an effort I started few years ago. I loaded the it recently, and all tests but one go green. I will work on it, I hope soon... Alexandre On 10 Jun 2008, at 09:58, Norbert Hartl wrote: > I think the link to the packages issue should point to > > http://www.squeaksource.com/PackagesForSqueak/ > > Norbert > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 11, 2008

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

by Oscar Nierstrasz

Great! Just noticed two things: - Test Runner is missing from the Tools flap -- shouldn't it be there? - Installer is not there -- has it been replaced by something better? (just curious) - on On Jun 11, 2008, at 6:32, StÃ©phane Ducasse wrote: > > We are happy to produce a new release. It includes: trait > simplification, nebraska removal, MVC removal preparation, tests > fixed (float array), semaphore fixes, ... > Thanks alain, adrian, norbert, serge and other for their time. > > Stef > > Here is the log: > > update10028 > Fixing MC > ------------------------------------------------------ > update10030 > Fixing Delay > 0006834: Delay class>>timeoutSemaphore:afterMSecs: doesn t. > Description The implementation for Delay > class>>timeoutSemaphore:afterMSecs: doesn t even use its first > parameter, so it can t do what it says it does. > > This method should be deprecated or removed entirely. > Additional Information + tests > > Fixing Obsolete references > ------------------------------------------------------ > withUdpateLog: > 1.0 / (FloatArray with: 2.0) answer unexpected result. > Bug is in FloatArray>>adaptToNumber:andSend: > See : http://bugs.squeak.org/view.php?id=6782 > > fixing files left by tests > ------------------------------------------------------ > update10032 > Fixing Number parsing > > Cleaning nebraska > ------------------------------------------------------ > update10033 > Simplifying Traits usage in kernel > > Simplifying Traits usage in kernel > ------------------------------------------------------ > update10034 > Fixing tests (serge stinckwich) > > http://bugs.squeak.org/view.php?id=6936 > #asHTMLColor is inaccurate for certain values. > Attached fix resolves that, also gives 10x speed-up. > ------------------------------------------------------ > update10035 > Merging MVC removal step one of Alain Plantec > ------------------------------------------------------ > update10036 > Merging MVC removal step one of Alain Plantec (missing part) > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2008

Re: [Pharo-project] Harvesting some fixes

by StÃ©phane Ducasse

>> >> >> I will harvest the MVC cleaning step one. >> I harvested some changes. I suggest you to reload 10034. because of >> some >> manipulations I did with the scriptloader > > Does that mean that the contents of update 10034 have been changed? > How do I reload it? You cannot sorry. > I have been looking at the updates as a sort of "revision history", > and thus I think it is not a good idea to change updates once they are > published, is that not so? Indeed but I realized latter that there was a problem that was simpler to fix by reloading fresh a package. The point is that the update stream is by default not stable else we do not have enough freedom. The stable part of the update stream is when we publish a new image with that part of the stream loaded. Sorry but this is easier like that. Now in general a problem like that should not happen. Just my mistake. Stef > > > Thanks, > > VÃctor. > >> _______________________________________________ >> 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 11, 2008

Re: [Pharo-project] self halt in RxParserTest>>testMatchesInwW

by StÃ©phane Ducasse

> > >> Ok I will publish a new version of the package on squeaksource > > Is this a good idea? Yes it is. Because we only publish packages (and only we forced we have side effect snippet). > How will the patch make it images that have been > updated? Will the patch make it into a "Pharo-from-scratch" image? Rx is not in the image by default. If he would I would publish a package and issue a "load that package" update item. Stef > > > VÃctor. > >> stef >> >> On Jun 10, 2008, at 9:04 PM, Oscar Nierstrasz wrote: >> >>> >>> You har the image-meister, so you should patch it, I think. I can >>> only >>> add a patch into the PharoInbox, but this is so trivial it is >>> easier if you >>> just update your master image. >>> >>> - on >>> >>> On Jun 10, 2008, at 6:33 PM, StÃ©phane Ducasse wrote: >>> >>>> Yes go ahead. >>>> >>>> Stef >>>> >>>> On Jun 10, 2008, at 2:06 PM, Oscar Nierstrasz wrote: >>>> >>>>> >>>>> Stef, >>>>> >>>>> RxParserTest>>testMatchesInwW >>>>> >>>>> has a self halt in it dating from 2006, apparently added by you. >>>>> >>>>> I guess you should remove it ... The test runs fine otherwise. >>>>> >>>>> - 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 >

June 11, 2008

[Pharo-project] [ANN] New release

by StÃ©phane Ducasse

We are happy to produce a new release. It includes: trait simplification, nebraska removal, MVC removal preparation, tests fixed (float array), semaphore fixes, ... Thanks alain, adrian, norbert, serge and other for their time. Stef Here is the log: update10028 Fixing MC ------------------------------------------------------ update10030 Fixing Delay 0006834: Delay class>>timeoutSemaphore:afterMSecs: doesn t. Description The implementation for Delay class>>timeoutSemaphore:afterMSecs: doesn t even use its first parameter, so it can t do what it says it does. This method should be deprecated or removed entirely. Additional Information + tests Fixing Obsolete references ------------------------------------------------------ withUdpateLog: 1.0 / (FloatArray with: 2.0) answer unexpected result. Bug is in FloatArray>>adaptToNumber:andSend: See : http://bugs.squeak.org/view.php?id=6782 fixing files left by tests ------------------------------------------------------ update10032 Fixing Number parsing Cleaning nebraska ------------------------------------------------------ update10033 Simplifying Traits usage in kernel Simplifying Traits usage in kernel ------------------------------------------------------ update10034 Fixing tests (serge stinckwich) http://bugs.squeak.org/view.php?id=6936 #asHTMLColor is inaccurate for certain values. Attached fix resolves that, also gives 10x speed-up. ------------------------------------------------------ update10035 Merging MVC removal step one of Alain Plantec ------------------------------------------------------ update10036 Merging MVC removal step one of Alain Plantec (missing part)

June 11, 2008

Re: [Pharo-project] Harvesting some fixes

by Victor Rodriguez

On Mon, Jun 9, 2008 at 7:44 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi all > > I will harvest the MVC cleaning step one. > I harvested some changes. I suggest you to reload 10034. because of some > manipulations I did with the scriptloader Does that mean that the contents of update 10034 have been changed? How do I reload it? I have been looking at the updates as a sort of "revision history", and thus I think it is not a good idea to change updates once they are published, is that not so? Thanks, VÃctor. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2008

Re: [Pharo-project] self halt in RxParserTest>>testMatchesInwW

by Victor Rodriguez

On Tue, Jun 10, 2008 at 3:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok I will publish a new version of the package on squeaksource Is this a good idea? How will the patch make it images that have been updated? Will the patch make it into a "Pharo-from-scratch" image? VÃctor. > stef > > On Jun 10, 2008, at 9:04 PM, Oscar Nierstrasz wrote: > >> >> You har the image-meister, so you should patch it, I think. I can only >> add a patch into the PharoInbox, but this is so trivial it is easier if you >> just update your master image. >> >> - on >> >> On Jun 10, 2008, at 6:33 PM, StÃ©phane Ducasse wrote: >> >>> Yes go ahead. >>> >>> Stef >>> >>> On Jun 10, 2008, at 2:06 PM, Oscar Nierstrasz wrote: >>> >>>> >>>> Stef, >>>> >>>> RxParserTest>>testMatchesInwW >>>> >>>> has a self halt in it dating from 2006, apparently added by you. >>>> >>>> I guess you should remove it ... The test runs fine otherwise. >>>> >>>> - 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 >

June 11, 2008

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

by Oscar Nierstrasz

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 >

June 10, 2008

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

by StÃ©phane Ducasse

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 >

June 10, 2008

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

by Oscar Nierstrasz

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 >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by StÃ©phane Ducasse

No problem. Stef On Jun 10, 2008, at 9:51 PM, Oscar Nierstrasz wrote: > > Very strange. > > I updated earlier today and did not get Integer>>hex. Now it is > there. > > Of course your implementation is better since it reuses existing > functionality. > > Gremlins are definitely at work here ;-) > > Sorry for the confusion, though I really do not understand why my > image stayed out of sync and now it is ok. > > - on > > On Jun 10, 2008, at 9:35 PM, Oscar Nierstrasz wrote: > >> >> Wow. >> >> I took pharo0.1-10032-7075dev08.06.1 and updated it. There is no >> Integer>>hex there. >> >> Damien, can you help? It looks like the pharo-dev image is somehow >> out of sync. >> >> I will try both again now. >> >> - on >> >> On Jun 10, 2008, at 9:21 PM, StÃ©phane Ducasse wrote: >> >>> Hi oscar >>> >>> I took the pharo image Pharo0.1-10028-2008-05-24 available on the >>> pharo web site >>> and did an update. >>> >>> and there is >>> Integer>>hex >>> ^ self printStringBase: 16 >>> >>> I checked the version and it is from 25 of may >>> >>> Stef >>> >>>> >>>> Hi Stef, >>>> >>>> I loaded a fresh pharo-dev image and updated everything. Then >>>> the testHex tests failed, so I fixed them. >>>> >>>> Can you please tell me which implementors of hex you find in your >>>> image? >>>> >>>> I only find Character>>hex and Float>>hex. I had to implement >>>> Integer>>hex myself. >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: >>>> >>>>> testHex >>>>> self assert: $a hex '61' = '61'. >>>>> self assert: Character space hex = '20' >>>>> >>>>> is green on my image >>>>> >>>>> as well as this one >>>>> >>>>> testHex >>>>> self assert: 0 hex = '0'. >>>>> self assert: 12 hex = 'C'. >>>>> self assert: 1234 hex = '4D2'. >>>>> >>>>> They are red in yours? >>>>> >>>>> Stef >>>>> >>>>> >>>>> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> Well, I thought we would start to fix the existing broken tests >>>>>> before adding new broken tests. >>>>>> >>>>>> I would also be very happy to see some comments when someone >>>>>> adds a new broken test, so I know what the plan is. >>>>>> >>>>>> Now I added an implementation of Integer>>hex, for example, but >>>>>> I am not so sure why we need this. >>>>>> Ain't too many senders. An easier fix would have been to remove >>>>>> the broken test. >>>>>> >>>>>> Cheers, >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>>>>> >>>>>>> Is your concern that the new tests are broken (which seems >>>>>>> normal to me >>>>>>> that they would start out that way), or are you objecting to >>>>>>> their being >>>>>>> included in the image? >>>>>>> >>>>>>> I can see arguments either way on the latter. If code in the >>>>>>> image is >>>>>>> wrong and a clearly correct but currently failing test >>>>>>> highlights it, >>>>>>> I'd rather be alerted to it. You are also correct that having >>>>>>> them >>>>>>> included draws attention that could easily encourage >>>>>>> duplication of >>>>>>> effort. >>>>>>> >>>>>>> Comments? >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wilhelm K. Schwab, Ph.D. >>>>>>> University of Florida >>>>>>> Department of Anesthesiology >>>>>>> PO Box 100254 >>>>>>> Gainesville, FL 32610-0254 >>>>>>> >>>>>>> Email: bschwab(a)anest.ufl.edu >>>>>>> Tel: (352) 846-1285 >>>>>>> FAX: (352) 392-7029 >>>>>>> >>>>>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>>>>> >>>>>>> I looked at the wiki page >>>>>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>>>>> but it does not say much. >>>>>>> >>>>>>> I would like to work through some tests, but I cannot find an >>>>>>> overview. >>>>>>> >>>>>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>>>>> broken >>>>>>> but seem to be very new. Stef, are you working on these? You >>>>>>> seem to >>>>>>> have written the tests ... >>>>>>> >>>>>>> - 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 >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

No, the pharo-dev image is ok now too. Time to go to bed. - on On Jun 10, 2008, at 9:47 PM, StÃ©phane Ducasse wrote: > aha. > may be squeakdev is based on another image or there is package that > when loading remove hex. > > Stef > > On Jun 10, 2008, at 9:35 PM, Oscar Nierstrasz wrote: > >> >> Wow. >> >> I took pharo0.1-10032-7075dev08.06.1 and updated it. There is no >> Integer>>hex there. >> >> Damien, can you help? It looks like the pharo-dev image is somehow >> out of sync. >> >> I will try both again now. >> >> - on >> >> On Jun 10, 2008, at 9:21 PM, StÃ©phane Ducasse wrote: >> >>> Hi oscar >>> >>> I took the pharo image Pharo0.1-10028-2008-05-24 available on the >>> pharo web site >>> and did an update. >>> >>> and there is >>> Integer>>hex >>> ^ self printStringBase: 16 >>> >>> I checked the version and it is from 25 of may >>> >>> Stef >>> >>>> >>>> Hi Stef, >>>> >>>> I loaded a fresh pharo-dev image and updated everything. Then >>>> the testHex tests failed, so I fixed them. >>>> >>>> Can you please tell me which implementors of hex you find in your >>>> image? >>>> >>>> I only find Character>>hex and Float>>hex. I had to implement >>>> Integer>>hex myself. >>>> >>>> - on >>>> >>>> On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: >>>> >>>>> testHex >>>>> self assert: $a hex '61' = '61'. >>>>> self assert: Character space hex = '20' >>>>> >>>>> is green on my image >>>>> >>>>> as well as this one >>>>> >>>>> testHex >>>>> self assert: 0 hex = '0'. >>>>> self assert: 12 hex = 'C'. >>>>> self assert: 1234 hex = '4D2'. >>>>> >>>>> They are red in yours? >>>>> >>>>> Stef >>>>> >>>>> >>>>> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >>>>> >>>>>> >>>>>> Well, I thought we would start to fix the existing broken tests >>>>>> before adding new broken tests. >>>>>> >>>>>> I would also be very happy to see some comments when someone >>>>>> adds a new broken test, so I know what the plan is. >>>>>> >>>>>> Now I added an implementation of Integer>>hex, for example, but >>>>>> I am not so sure why we need this. >>>>>> Ain't too many senders. An easier fix would have been to remove >>>>>> the broken test. >>>>>> >>>>>> Cheers, >>>>>> - on >>>>>> >>>>>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>>>>> >>>>>>> Is your concern that the new tests are broken (which seems >>>>>>> normal to me >>>>>>> that they would start out that way), or are you objecting to >>>>>>> their being >>>>>>> included in the image? >>>>>>> >>>>>>> I can see arguments either way on the latter. If code in the >>>>>>> image is >>>>>>> wrong and a clearly correct but currently failing test >>>>>>> highlights it, >>>>>>> I'd rather be alerted to it. You are also correct that having >>>>>>> them >>>>>>> included draws attention that could easily encourage >>>>>>> duplication of >>>>>>> effort. >>>>>>> >>>>>>> Comments? >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> Wilhelm K. Schwab, Ph.D. >>>>>>> University of Florida >>>>>>> Department of Anesthesiology >>>>>>> PO Box 100254 >>>>>>> Gainesville, FL 32610-0254 >>>>>>> >>>>>>> Email: bschwab(a)anest.ufl.edu >>>>>>> Tel: (352) 846-1285 >>>>>>> FAX: (352) 392-7029 >>>>>>> >>>>>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>>>>> >>>>>>> I looked at the wiki page >>>>>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>>>>> but it does not say much. >>>>>>> >>>>>>> I would like to work through some tests, but I cannot find an >>>>>>> overview. >>>>>>> >>>>>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>>>>> broken >>>>>>> but seem to be very new. Stef, are you working on these? You >>>>>>> seem to >>>>>>> have written the tests ... >>>>>>> >>>>>>> - 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 >

June 10, 2008

Re: [Pharo-project] Who is working on which tests? Why are there new, broken tests?

by Oscar Nierstrasz

Very strange. I updated earlier today and did not get Integer>>hex. Now it is there. Of course your implementation is better since it reuses existing functionality. Gremlins are definitely at work here ;-) Sorry for the confusion, though I really do not understand why my image stayed out of sync and now it is ok. - on On Jun 10, 2008, at 9:35 PM, Oscar Nierstrasz wrote: > > Wow. > > I took pharo0.1-10032-7075dev08.06.1 and updated it. There is no > Integer>>hex there. > > Damien, can you help? It looks like the pharo-dev image is somehow > out of sync. > > I will try both again now. > > - on > > On Jun 10, 2008, at 9:21 PM, StÃ©phane Ducasse wrote: > >> Hi oscar >> >> I took the pharo image Pharo0.1-10028-2008-05-24 available on the >> pharo web site >> and did an update. >> >> and there is >> Integer>>hex >> ^ self printStringBase: 16 >> >> I checked the version and it is from 25 of may >> >> Stef >> >>> >>> Hi Stef, >>> >>> I loaded a fresh pharo-dev image and updated everything. Then the >>> testHex tests failed, so I fixed them. >>> >>> Can you please tell me which implementors of hex you find in your >>> image? >>> >>> I only find Character>>hex and Float>>hex. I had to implement >>> Integer>>hex myself. >>> >>> - on >>> >>> On Jun 10, 2008, at 6:38 PM, StÃ©phane Ducasse wrote: >>> >>>> testHex >>>> self assert: $a hex '61' = '61'. >>>> self assert: Character space hex = '20' >>>> >>>> is green on my image >>>> >>>> as well as this one >>>> >>>> testHex >>>> self assert: 0 hex = '0'. >>>> self assert: 12 hex = 'C'. >>>> self assert: 1234 hex = '4D2'. >>>> >>>> They are red in yours? >>>> >>>> Stef >>>> >>>> >>>> On Jun 10, 2008, at 4:00 PM, Oscar Nierstrasz wrote: >>>> >>>>> >>>>> Well, I thought we would start to fix the existing broken tests >>>>> before adding new broken tests. >>>>> >>>>> I would also be very happy to see some comments when someone >>>>> adds a new broken test, so I know what the plan is. >>>>> >>>>> Now I added an implementation of Integer>>hex, for example, but >>>>> I am not so sure why we need this. >>>>> Ain't too many senders. An easier fix would have been to remove >>>>> the broken test. >>>>> >>>>> Cheers, >>>>> - on >>>>> >>>>> On Jun 10, 2008, at 15:53, Bill Schwab wrote: >>>>> >>>>>> Is your concern that the new tests are broken (which seems >>>>>> normal to me >>>>>> that they would start out that way), or are you objecting to >>>>>> their being >>>>>> included in the image? >>>>>> >>>>>> I can see arguments either way on the latter. If code in the >>>>>> image is >>>>>> wrong and a clearly correct but currently failing test >>>>>> highlights it, >>>>>> I'd rather be alerted to it. You are also correct that having >>>>>> them >>>>>> included draws attention that could easily encourage >>>>>> duplication of >>>>>> effort. >>>>>> >>>>>> Comments? >>>>>> >>>>>> Bill >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Wilhelm K. Schwab, Ph.D. >>>>>> University of Florida >>>>>> Department of Anesthesiology >>>>>> PO Box 100254 >>>>>> Gainesville, FL 32610-0254 >>>>>> >>>>>> Email: bschwab(a)anest.ufl.edu >>>>>> Tel: (352) 846-1285 >>>>>> FAX: (352) 392-7029 >>>>>> >>>>>>>>> oscar(a)iam.unibe.ch 06/10/08 8:31 AM >>> >>>>>> >>>>>> I looked at the wiki page >>>>>> http://code.google.com/p/pharo/wiki/CurrentlyWorkingOn >>>>>> but it does not say much. >>>>>> >>>>>> I would like to work through some tests, but I cannot find an >>>>>> overview. >>>>>> >>>>>> The tests CharacterTest>>testHex and IntegerTest>>testHex are >>>>>> broken >>>>>> but seem to be very new. Stef, are you working on these? You >>>>>> seem to >>>>>> have written the tests ... >>>>>> >>>>>> - 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 >

June 10, 2008