- Pharo-dev - lists.pharo.org

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