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

[Pharo-project] Opening image multiple times - bug or feature?

by Schwab,Wilhelm K

Hello all, I'm getting Ubuntu configured on my new $400 laptop, and just noticed that I can load one Pharo image at least twice w/o any error messages. Is that good or bad? I'm inclined to say it is bad, with caveats below. I mentioned caveats: I have mixed feelings about Pharo's emulated/MDI GUI. There have been (rare) times when it would have been nice to be able to do something similar on Dolphin. If there is a reason to run multiple IDEs on one box, having them clearly separated by a single main window has some advantages. Bill

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Mariano Martinez Peck

On Thu, Sep 24, 2009 at 2:07 PM, Bernhard Pieber <bernhard(a)pieber.com>wrote: > Hi Mariano, > > I agree it would be a cool feature to add to the TestRunner. I guess > it is even quite simple. > > In the meantime this is what I do: > 1. Shift-Click with middle mouse button on the list, so that the halos > for the PluggableListMorphPlus are show. > 2. Click on the red Menu halo and select the menu item "copy list to > clipboard". > Hi Bernhard! I tried but I didn't finde a "copy list to clipboard". I am using pharo1.0-10451-BETAdev09.09.3 > 3. VoilÃ ! > > There is even a "copy selection to clipboard". > > This is Morphic at its best IMO. > > Cheers, > Bernhard > > Am 24.09.2009 um 15:22 schrieb Mariano Martinez Peck: > > > Hi folks: Several times, I wanted to send by email for example, the > > results of running some tests. The only and ugly way I found to do > > this is using PrintScreen and send the screenshots. Now, the > > question is, is there a way to file out the results? Not only the > > amount (the number) of success, failures, error, expected failures, > > but also which tests where the failures, errors, etc. > > > > I would love to do this from the Test Runner, no by code. > > > > Best, > > > > Mariano > > _______________________________________________ > > 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 >

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Bernhard Pieber

Hi Mariano, I agree it would be a cool feature to add to the TestRunner. I guess it is even quite simple. In the meantime this is what I do: 1. Shift-Click with middle mouse button on the list, so that the halos for the PluggableListMorphPlus are show. 2. Click on the red Menu halo and select the menu item "copy list to clipboard". 3. VoilÃ ! There is even a "copy selection to clipboard". This is Morphic at its best IMO. Cheers, Bernhard Am 24.09.2009 um 15:22 schrieb Mariano Martinez Peck: > Hi folks: Several times, I wanted to send by email for example, the > results of running some tests. The only and ugly way I found to do > this is using PrintScreen and send the screenshots. Now, the > question is, is there a way to file out the results? Not only the > amount (the number) of success, failures, error, expected failures, > but also which tests where the failures, errors, etc. > > I would love to do this from the Test Runner, no by code. > > Best, > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by StÃ©phane Ducasse

Yes but so far I think that we should improve TestServerSimple. >> >>> Hi folks: Several times, I wanted to send by email for example, >>> the results of running some tests. The only and ugly way I found >>> to do this is using PrintScreen and send the screenshots. Now, the >>> question is, is there a way to file out the results? Not only the >>> amount (the number) of success, failures, error, expected >>> failures, but also which tests where the failures, errors, etc. >> >> You can take a look at http://www.squeaksource.com/TestServerSimple.html >> for some samples of code. >> >> >> Wow! I wasn't aware of that project. What's the idea of that >> project? I didn't find any information there. > > Just having a simple automated engine to run tests for Moose > automatically. The code is adapted from some previous project in > Switzerland and, to be honest, it's pretty much a hack leaving > plenty of dead code behind. Configuration of projects to test is > hard-coded. I am working on a new TestServer which would use > Metacello configurations. > > > Sounds excellent. I really would love to have continuous integration > in Pharo. > Are you aware of http://www.squeaksource.com/ > ContIntegration.html ?? > > Perhaps you can join efforts... > >> >> However, I was thinking in something much more simpler. For newbies >> (like me hahaha) or people who may want to contribute to Pharo just >> testing and sending the reports. Perhaps a simple button in Test >> Runner that says "Fileout results". So that he can send the file to >> the mailing list or whatever. >> >> what do you think ? > > That's a very good idea. We need more power tools for the tests > anyway. I would also like to see more powerful features for > regression testing (there is a basic test history only accessible > through the TestRunner right now) > > > Excellent! > > >> >>> >>> I would love to do this from the Test Runner, no by code. >>> >>> Best, >>> >>> Mariano >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> 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 > > -- > Simon > > > > > _______________________________________________ > 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

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by StÃ©phane Ducasse

it would be good to have a xml or kind of format to store results of tests. Philippe also suggested a format that is compatible with Junit this way we could use Java infrastrcture. So yes I woul dlike to get such behavior. Stef On Sep 24, 2009, at 3:34 PM, Mariano Martinez Peck wrote: > > > 2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > > On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: > >> Hi folks: Several times, I wanted to send by email for example, the >> results of running some tests. The only and ugly way I found to do >> this is using PrintScreen and send the screenshots. Now, the >> question is, is there a way to file out the results? Not only the >> amount (the number) of success, failures, error, expected failures, >> but also which tests where the failures, errors, etc. > > You can take a look at http://www.squeaksource.com/TestServerSimple.html > for some samples of code. > > > Wow! I wasn't aware of that project. What's the idea of that > project? I didn't find any information there. > > However, I was thinking in something much more simpler. For newbies > (like me hahaha) or people who may want to contribute to Pharo just > testing and sending the reports. Perhaps a simple button in Test > Runner that says "Fileout results". So that he can send the file to > the mailing list or whatever. > > what do you think ? > >> >> I would love to do this from the Test Runner, no by code. >> >> Best, >> >> Mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > 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

Sept. 24, 2009

[Pharo-project] closure fixes nearly released

by StÃ©phane Ducasse

Hi I created an image based on the script of mike (after running his script the packages are clean and the image is working normally). But before pushing that in the stream I would like to make sure that everything in under control. https://gforge.inria.fr/frs/download.php/23650/PharoCore-1.0-10456-BETA-clo… it would be great if you could have a look. You can see the difference between the test before and the tests after. Eliot apparently the decompiler generates the same code but with different name (number) so many tests are failing because of that. Eliot could you have a look to see if the broken tests looks suspicious to you or not? Thanks in advance. Stef

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Simon Denier

On 24 sept. 09, at 15:56, Mariano Martinez Peck wrote: > > > 2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > > On 24 sept. 09, at 15:34, Mariano Martinez Peck wrote: > >> >> >> 2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> >> >> On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: >> >>> Hi folks: Several times, I wanted to send by email for example, >>> the results of running some tests. The only and ugly way I found >>> to do this is using PrintScreen and send the screenshots. Now, the >>> question is, is there a way to file out the results? Not only the >>> amount (the number) of success, failures, error, expected >>> failures, but also which tests where the failures, errors, etc. >> >> You can take a look at http://www.squeaksource.com/TestServerSimple.html >> for some samples of code. >> >> >> Wow! I wasn't aware of that project. What's the idea of that >> project? I didn't find any information there. > > Just having a simple automated engine to run tests for Moose > automatically. The code is adapted from some previous project in > Switzerland and, to be honest, it's pretty much a hack leaving > plenty of dead code behind. Configuration of projects to test is > hard-coded. I am working on a new TestServer which would use > Metacello configurations. > > > Sounds excellent. I really would love to have continuous integration > in Pharo. > Are you aware of http://www.squeaksource.com/ > ContIntegration.html ?? > > Perhaps you can join efforts... Indeed, it looks interesting -- Simon

Sept. 24, 2009

Re: [Pharo-project] '.2e2' asNumber ?

by Nicolas Cellier

R1) RATIONALE FOR HAVING AN EXCEPTION RAISED BY DEFAULT: The Smalltalk way is the lazy way: raise an Exception, let it unhandled and let user interact in the Debugger to understand what went wrong. This work best if the Exception is raised soon after the error conditions, and that is why I generally prefer raising an Exception than answering nil, or even worse zero! R2) RATIONALE FOR HAVING PROGRAMMABLE ERROR: For a closed source application, you'll have to implement your own error handling... ...and the Kernel should propose, not impose the implementation style: - Exception handling ([] ifError: [], [] on: Error do: [:exc | ]) - exception block argument (at:ifAbsent:, readFrom:ifFail:) - isNil ifTrue: [] (very C-stylish) STATUS OF CURRENT IMPLEMENTATION: When reading fail for any reason then: SqNumberParser>>fail failBlock isNil ifFalse: [^failBlock value]. self error: 'Reading a number failed' Default behaviour is to raise an Exception. But SqNumberParser is programmable via failBlock. And this is used to answer 0 in case of failure... Number class>>readFrom: stringOrStream "Answer a number as described on aStream. The number may be any accepted Smalltalk literal Number format. It can include a leading radix specification, as in 16rFADE. It can as well be NaN, Infinity or -Infinity for conveniency. If stringOrStream does not start with a valid number description, answer 0 for backward compatibility. This is not clever and should better be changed." ^(SqNumberParser on: stringOrStream) failBlock: [^0]; nextNumber Unless you use the dedicated programmable entry point: Number class>>readFrom: stringOrStream ifFail: aBlock "Answer a number as described on aStream. The number may be any accepted Smalltalk literal Number format. It can include a leading radix specification, as in 16rFADE. It can as well be NaN, Infinity or -Infinity for conveniency. If input does not represent a valid number, then execute fail block and leave the stream positioned before offending character" ^(SqNumberParser on: stringOrStream) failBlock: aBlock; nextNumber CONCLUSION AND TODO: 1) R1 is not fulfilled, so better raise an Exception than answer zero 2) R2 is already fulfilled, just open a browser and see by yourself 3) Eventually create a dedicated exception like NumberParsingError... Nicolas 2009/9/24 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Nicolas, > > Silent failures are **BAD**. Â I always like to compare things to #at: and #at:ifAbsent:. Â #at: will answer the indicated item or raise an exception. #at:ifAbsent: allows one to customize the behavior and w/o the expense of setting up an exception handler, which is great if the error (bounds in this case) can be understood and corrected locally. Â Of course, structured exceptions arose to handle the common situation in which I find an error but only you can tell what to do about it, and we are working on completely different parts of the system. > > This whole debate arises again with end-of-stream exceptions: > > Â http://code.google.com/p/pharo/wiki/StreamsForRobustSoftware > > I am using the additional protocol approach with good results, but should try to make some time to test your pluggable exception idea. > > Bill > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Nicolas Cellier > Sent: Thursday, September 24, 2009 3:19 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] '.2e2' asNumber ? > > The two problems were identified from the beginning: > > 1) 2.e5 and .2 did work in old squeak images, but no more with SqNumberParser > Rationale: SqNumberParser is for parsing number literals in squeak syntax, and those extensions are not identified squeak syntax > > If you need these syntax, the best thing is to subclass the NumberParser. For example, I must have a FORTRANNumberParser available somewhere... > > 2) Silently returning zero in case of error. > This was one of the goal of SqNumberParser: let programmer choose the appropriate behaviour > - raise an Exception > - answer nil > - answer a default value (zero) > The last solution has been connected to Number class>>#readFrom: for historical compatibility reasons. > I agree this conservative choice was unfortunate. > Pharo should not fear and break compatibility on such dumb behaviours. > > Nicolas > > 2009/9/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> I imagine that nicolas will let us know. >> If you have tests we would love to integrate them so that we can >> detect that. >> >> Stef >> >> On Sep 23, 2009, at 11:25 PM, John M McIntosh wrote: >> >>> I noticed that in Squeak and earlier version of Pharo doing '.2e2' >>> asNumber would return 20.0 or '.2' asNumber would return 0.2 >>> >>> but currently in Pharo those return 0, without error, comment, or >>> other hand waving. >>> Good thing I have Sunits... >>> >>> So is this a bug or feature? >>> >>> Hint obviously in the Fractions calculator people are lazy and enter . >>> 2e2 or .2 without the leading zero... >>> >>> -- >>> = >>> = >>> = >>> = >>> = >>> ===================================================================== >>> = John M. McIntosh <johnmci(a)smalltalkconsulting.com> Â Twitter: >>> squeaker68882 >>> Corporate Smalltalk Consulting Ltd. Â http:// >>> www.smalltalkconsulting.com = = = = = >>> ===================================================================== >>> = >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Mariano Martinez Peck

2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > > On 24 sept. 09, at 15:34, Mariano Martinez Peck wrote: > > > > 2009/9/24 Simon Denier <Simon.Denier(a)inria.fr> > >> >> On 24 sept. 09, at 15:22, Mariano Martinez Peck wrote: >> >> Hi folks: Several times, I wanted to send by email for example, the >> results of running some tests. The only and ugly way I found to do this is >> using PrintScreen and send the screenshots. Now, the question is, is there a >> way to file out the results? Not only the amount (the number) of success, >> failures, error, expected failures, but also which tests where the failures, >> errors, etc. >> >> >> You can take a look at http://www.squeaksource.com/TestServerSimple.html for >> some samples of code. >> >> > Wow! I wasn't aware of that project. What's the idea of that project? I > didn't find any information there. > > > Just having a simple automated engine to run tests for Moose automatically. > The code is adapted from some previous project in Switzerland and, to be > honest, it's pretty much a hack leaving plenty of dead code behind. > Configuration of projects to test is hard-coded. I am working on a new > TestServer which would use Metacello configurations. > > Sounds excellent. I really would love to have continuous integration in Pharo. Are you aware of http://www.squeaksource.com/ContIntegration.html ?? Perhaps you can join efforts... > > However, I was thinking in something much more simpler. For newbies (like > me hahaha) or people who may want to contribute to Pharo just testing and > sending the reports. Perhaps a simple button in Test Runner that says > "Fileout results". So that he can send the file to the mailing list or > whatever. > > what do you think ? > > > That's a very good idea. We need more power tools for the tests anyway. I > would also like to see more powerful features for regression testing (there > is a basic test history only accessible through the TestRunner right now) > Excellent! > > > >> >> I would love to do this from the Test Runner, no by code. >> >> Best, >> >> Mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> -- >> Simon >> >> >> >> >> _______________________________________________ >> 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 > > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 24, 2009

Re: [Pharo-project] Fileout the test results

by Damien Cassou

2009/9/24 Mariano Martinez Peck <marianopeck(a)gmail.com>: > However, I was thinking in something much more simpler. For newbies (like me > hahaha) or people who may want to contribute to Pharo just testing and > sending the reports. Perhaps a simple button in Test Runner that says > "Fileout results". So that he can send the file to the mailing list or > whatever. > > what do you think ? That's a good idea. Adding it should be pretty straightforward. Could you please have a look? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 24, 2009