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

Re: [Pharo-project] [update] #10488

by George Herolyants

Pharo fails to condense .sources file. I get an error "Invalid utf8 input detected" and no PharoDebug.log at all. The last lines of the new .sources file are: !OBWebIcons methodsFor: 'icons' stamp: 'cwp 6/20/2009 00:55'! arrowDown ^ MIMEDocument contentType: 'image/png' content: 'Ðâ°PNG...<then other unprintable characters follow> George

Oct. 19, 2009

Re: [Pharo-project] [update] #10487

by Mariano Martinez Peck

On Mon, Oct 19, 2009 at 10:59 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > 10483 - 10487 > ----- > - Issue 1310: Make all tests green > This is grate news. Sorry for my ignorance, but when you refer to "all tests" are you talking about Pharo core or just Pharo? In addition, is a Pharo goal to have also all test green in the dev image ? > - Issue 1330: Better performance for tests > > Test result: 7168 run, 7150 passes, 18 expected failures, 0 failures, > 0 errors, 0 unexpected passes > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2009

[Pharo-project] New Pharo and pharo-web based on core 10487

by Damien Cassou

http://pharo-project.org/pharo-download -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Oct. 19, 2009

[Pharo-project] [update] #10488

by Adrian Lienhard

This change will condense the sources file and clean out the changes file. 10488 ----- Condense sources ___________________ http://www.adrian-lienhard.ch/

Oct. 19, 2009

Re: [Pharo-project] [update] #10487

by StÃ©phane Ducasse

excellent! On Oct 19, 2009, at 2:59 PM, Adrian Lienhard wrote: > 10483 - 10487 > ----- > - Issue 1310: Make all tests green > - Issue 1330: Better performance for tests > > Test result: 7168 run, 7150 passes, 18 expected failures, 0 failures, > 0 errors, 0 unexpected passes > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2009

[Pharo-project] [update] #10487

by Adrian Lienhard

10483 - 10487 ----- - Issue 1310: Make all tests green - Issue 1330: Better performance for tests Test result: 7168 run, 7150 passes, 18 expected failures, 0 failures, 0 errors, 0 unexpected passes ___________________ http://www.adrian-lienhard.ch/

Oct. 19, 2009

[Pharo-project] [update] #10483

by Adrian Lienhard

10483 ----- Issue 1330: Better performance for tests

Oct. 19, 2009

[Pharo-project] [update] #10482

by Adrian Lienhard

10482 ----- Issue 1310: Make all tests green (done now?) Issue 1319: [squeak trunk] Fix MNU #empty while Debugging Issue 1320: [squeak trunk] Sort the conflicts. This is required when merging a distant version, like Pharo for example... Issue 1327: TestRunner should set dummy author when running tests ___________________ http://www.adrian-lienhard.ch/

Oct. 19, 2009

Re: [Pharo-project] About TestCase >> assert:

by Mariano Martinez Peck

On Fri, Oct 16, 2009 at 4:45 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > There are inconsistencies that bother me. > > > > * TestCase>>assert: in most Smalltalks accepts only a boolean. In > > Pharo, > > it accepts either a boolean or a block. This makes tests less > > portable. > > +1 > > > * TestCase>>assert:equals: (a very useful method) does not accept a > > block. Anyone used to giving blocks to #assert: would probably expect > > this method to accept a block. > > +1 consistency is nice. > > > * Object assert: accepts a boolean or a block. I don't know of any > > standard for this. > > me neither > > > * BlockClosure>>assert does not take any arguments, so I feel it is > > very > > clean. > > +1 > > > Proposed changes: (based on earlier discussion plus personal opinion) > > > > TestCase>>assert: should only accept a boolean. This brings > > compatibility with other Smalltalks, and consistency with > > TestCase>>assert:equals:. > > + 1 > > > Object>>assert: should be removed/deprecated in favor of > > BlockClosure>>assert. This removes confusion with TestCase>>assert:. > > deprecation! > > > Object>>assert:description: and Object>>assert:descriptionBlock: > > should > > be removed/deprecated in favor of (new) > > BlockClosure>>assertWithDescription:, which accepts either a block > > or a > > string. This provides convenient invariant and pre/post condition > > testing. > > Let us do that. > Any taker? > > I don't have time right now for this, but at least I created the ticket: http://code.google.com/p/pharo/issues/detail?id=1329 Cheers, mariano > Stef > > > > > > Opinions? > > > > -Martin > > > > _______________________________________________ > > 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 >

Oct. 19, 2009

Re: [Pharo-project] Input problems

by Schwab,Wilhelm K

Stef, I assumed that was the purpose of the updated fix, but I explicitly did that, and again find that there is no "wow" effect. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Sunday, October 18, 2009 1:27 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Input problems did you executed InputEventSensor default initialize Stef On Oct 18, 2009, at 8:15 PM, Schwab,Wilhelm K wrote: > This time I copied the entire directory, filed in the change set and > saved/quit/re-opened. It really does not make any difference that I > can detect. Please keep at it. I will gladly try anything you think > improves the situation. > > Bill > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo- > project-bounces(a)lists.gforge.inria.fr] On Behalf Of Michael Rueger > Sent: Sunday, October 18, 2009 10:19 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Input problems > > Damien Cassou wrote: >> 2009/10/17 Michael Rueger <m.rueger(a)acm.org>: > >>> Please let me know if after filing in the change set the issues are >>> fixed, less often or unchanged. >> >> http://code.google.com/p/pharo/issues/detail?id=1323 > > OK, turns out the change set didn't actually do anything, so for Lukas > the placebo effect worked ;-) Just shows how ephemeral the problem can > be. > Attached an updated change set, that actually switches to > SharedQueue2. > > If there is someone who can reasonably reliably reproduce the missing > character problem, please contact me so I can work with you directly > on instrumenting a test image. > > Thanks > > Michael > > _______________________________________________ > 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

Oct. 18, 2009