January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] What are Owners ???

by Martin McClure

Mariano Martinez Peck wrote: > Also, can I remove Morph >> allOwners ? I checked and it has no sender > neither in: Dev, Moose, Seaside, Pier... I don't know the Squeak/Pharo/ST80 history of #allOwners, but in VW #allOwners invokes a primitive that answers all objects that contain a pointer to the receiver of #allOwners. Hope that helps... Regards, -Martin

Jan. 20, 2010

Re: [Pharo-project] A dog-slow browser

by Levente Uzonyi

On Wed, 20 Jan 2010, John M McIntosh wrote: > > On 2010-01-20, at 8:08 AM, Igor Stasenko wrote: > >> 2010/1/20 Marcus Denker <marcus.denker(a)inria.fr>: >> Caching should in contrary increase the speed, isnt? >> And i wouldn't say that my machine is slow >> CPU0: AMD Phenom(tm) 8450 Triple-Core Processor stepping 03 >> '85618729 bytecodes/sec; 4708854 sends/sec' > > > *slow* > > A *tuned* VM on Ubuntu on my macbook pro 2.33 intel Core 2 Duo gives > 573,991,031 bytescodes/sec and 14,406,658 sends/sec. What's tuned? Levente > > -- > =========================================================================== > 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 >

Jan. 20, 2010

Re: [Pharo-project] A dog-slow browser

by John M McIntosh

On 2010-01-20, at 8:08 AM, Igor Stasenko wrote: > 2010/1/20 Marcus Denker <marcus.denker(a)inria.fr>: > Caching should in contrary increase the speed, isnt? > And i wouldn't say that my machine is slow > CPU0: AMD Phenom(tm) 8450 Triple-Core Processor stepping 03 > '85618729 bytecodes/sec; 4708854 sends/sec' *slow* A *tuned* VM on Ubuntu on my macbook pro 2.33 intel Core 2 Duo gives 573,991,031 bytescodes/sec and 14,406,658 sends/sec. -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 20, 2010

Re: [Pharo-project] ocompletion bug fix

by Sean Allen

I see it was fixed once I went to check the Ocompletion version, in the next version after what we had installed: Ocompletion-DannyChan.44 fixes the bug. I didn't find a ticket in the issue tracker though. On Wed, Jan 20, 2010 at 1:06 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > It is best to create an issue in our tracker and put Romain Robbes, the maintainer of Ocompletion, in cc. Also post the issue URL to the mailing list. > > This problem, though, sounds familiar to me. Which versions are you using? You may find already closed reports of this problem in the tracker. > > Thanks, > Adrian > > On Jan 20, 2010, at 18:59 , Sean Allen wrote: > >> I just fixed a bug that has been driving me crazy for a while in the >> Ocompletion package. >> >> When you select an area of text and delete, if you are deleting all of >> it, it throws a subscript out of bounds error. >> >> What is the proper process for getting this change integrated? >> I'm not really sure who this small fix should be sent to. >> >> _______________________________________________ >> 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 >

Jan. 20, 2010

Re: [Pharo-project] ocompletion bug fix

by Sean Allen

I could find anything in the tracker... We are currently using: Pharo image: Pharo Pharo core version: PharoCore1.0rc1 Latest update: #10500 Virtual machine used: pharo-vm-0.15.2f-linux On Wed, Jan 20, 2010 at 1:06 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > It is best to create an issue in our tracker and put Romain Robbes, the maintainer of Ocompletion, in cc. Also post the issue URL to the mailing list. > > This problem, though, sounds familiar to me. Which versions are you using? You may find already closed reports of this problem in the tracker. > > Thanks, > Adrian > > On Jan 20, 2010, at 18:59 , Sean Allen wrote: > >> I just fixed a bug that has been driving me crazy for a while in the >> Ocompletion package. >> >> When you select an area of text and delete, if you are deleting all of >> it, it throws a subscript out of bounds error. >> >> What is the proper process for getting this change integrated? >> I'm not really sure who this small fix should be sent to. >> >> _______________________________________________ >> 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 >

Jan. 20, 2010

Re: [Pharo-project] [Seaside] Seaside + TDD

by Mariano Abel Coca

Excelent! I'll try it as soon as I can. Kind Regards, Mariano. On Wed, Jan 20, 2010 at 3:17 PM, Johan Brichau <Johan.Brichau(a)uclouvain.be>wrote: > Hi Mariano, > > I'm currently also looking at using Seaside Testing with Seaside 3.0. > > I have succeeded last weekend to make the R2.9 version work with Seaside > 3.0. > At least: all demo tests seem to be working properly. > > I uploaded the changes to squeaksource a couple of minutes ago. > > Cheers, > Johan > > On 19 Jan 2010, at 20:52, Mariano Abel Coca wrote: > > > Hi everyone, > > > > I'm trying to develop using TDD with seaside 3.0, but honestly, I > couldn't find any framework or package that works fine with it. I've tried > Albatross and Seaside Testing, both of them work great with Seaside 2.8, but > fails to run or even to load in seaside 3.0. > > > > Any other suggestions? > > > > Thanks in advance. > > > > Mariano. > > _______________________________________________ > > seaside mailing list > > seaside(a)lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Jan. 20, 2010

Re: [Pharo-project] O2: tester wanted!

by Alexandre Bergel

> However, there are 6 undeclared classes referenced in the code. Very > likely when this code is run, O2 will fall over. Also 2 tests have > errors and one fails. That cannot be left like that. I will seat down with David asap... Alexandre > > > On Jan 19, 2010, at 23:11 , Mariano Martinez Peck wrote: > >> On Tue, Jan 19, 2010 at 11:03 PM, Alexandre Bergel < >> alexandre.bergel(a)inria.fr> wrote: >> >>> Dear All, >>> >>> For people who do not know, O2 is the browser David has >>> implemented in >>> the last few years. It replaces class-categories on the left-hand >>> side >>> pane with a list of packages. We are still away from having packages >>> as real first class entities, but this is a good step toward. Note >>> that some people find O2 a bit slower than other available code >>> browsers. >>> >>> David and I spent some time on fixing O2. O2 has now no dependencies >>> to OB anymore. >>> We would like that people try it and submit bug reports on the >>> google >>> bug tracker. In a fresh 10505, you can load O2 by evaluating: >>> >>> Gofer new squeaksource: 'MetacelloRepository'; package: >>> 'ConfigurationOfO2'; load. (Smalltalk at: #ConfigurationOfO2) >>> perform: >>> #loadDefault >>> >>> >> Yes, but be aware that that piece of code load only the core, as >> you can see >> here: >> >> group: 'default' with: #('Core' ); >> group: 'Core' with: #( 'OmniBrowser2' 'O2-Standard' 'O2- >> Morphic' >> 'O2-Enhancements' ); >> group: 'Dev' with: #( 'Core' 'O2-Refactory' 'OCForO2' ); >> >> >> As I remember, most of the problems of O2 were sometimes related to >> the >> integration to RB. So, if you really want to tests it, please, test >> it using >> the RB: >> >> ((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: >> 'Dev' >> >> >> As I already said to Alexandre and David in private, I will put O2 >> again in >> the next image. So, it would be cool if it is tested "completely". >> >> >> >>> O2 does not need OB whatsoever. O2 loads in a Core (I tried in a >>> 11165). Before and after loading O2, running OB tests give "548 run, >>> 547 passes, 1 failures" [*]. >>> >>> >> Yes, if someone can help with that failure would be cool, I have >> already >> reported it. >> >> >> >>> Cheers, >>> Alexandre >>> >>> [*] the test have been loaded using (ConfigurationOfOmniBrowser >>> project version: '1.1') load: 'Dev Tests' >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> 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 >>> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2010

Re: [Pharo-project] [Seaside] Seaside + TDD

by Johan Brichau

Hi Mariano, I'm currently also looking at using Seaside Testing with Seaside 3.0. I have succeeded last weekend to make the R2.9 version work with Seaside 3.0. At least: all demo tests seem to be working properly. I uploaded the changes to squeaksource a couple of minutes ago. Cheers, Johan On 19 Jan 2010, at 20:52, Mariano Abel Coca wrote: > Hi everyone, > > I'm trying to develop using TDD with seaside 3.0, but honestly, I couldn't find any framework or package that works fine with it. I've tried Albatross and Seaside Testing, both of them work great with Seaside 2.8, but fails to run or even to load in seaside 3.0. > > Any other suggestions? > > Thanks in advance. > > Mariano. > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

Jan. 20, 2010

Re: [Pharo-project] ocompletion bug fix

by Mariano Martinez Peck

Yes, please, when submit the issue tracker, said exactly which version and browser are you using and if you can say the OCompletion version, better On Wed, Jan 20, 2010 at 3:06 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > It is best to create an issue in our tracker and put Romain Robbes, the > maintainer of Ocompletion, in cc. Also post the issue URL to the mailing > list. > > This problem, though, sounds familiar to me. Which versions are you using? > You may find already closed reports of this problem in the tracker. > > Thanks, > Adrian > > On Jan 20, 2010, at 18:59 , Sean Allen wrote: > > > I just fixed a bug that has been driving me crazy for a while in the > > Ocompletion package. > > > > When you select an area of text and delete, if you are deleting all of > > it, it throws a subscript out of bounds error. > > > > What is the proper process for getting this change integrated? > > I'm not really sure who this small fix should be sent to. > > > > _______________________________________________ > > 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 >

Jan. 20, 2010

[Pharo-project] DecompilationTests failures [was: About DecompilerTests >> decompilerDiscrepancies]

by Eliot Miranda

On Wed, Jan 20, 2010 at 12:41 AM, Michael Roberts <mike(a)mjr104.co.uk> wrote: > IIRC this suite is fairly specialised as part of eliot's closure work. > I think we disabled it from running because we did not have time to > fix it. I don't have an image at the moment but it would be better to > leave it alone if you can until someone can study the decompiler in > depth. Unless Eliot can comment? > Actually I suspect decompilerDiscrepancies is equivalent to my 3.8-derived image's DecompilerTests>>decompilerFailures which exists to list methods that will cause decompilation tests to fail and predates my work with closures. My version reads decompilerFailures "here is the list of failures: DNU resulting in trying to decompile the following methods" ^ #((BalloonEngineSimulation circleCosTable "-0.3826834323650903 => -0.38268343236509 or -0.3826834323650902") (BalloonEngineSimulation circleSinTable "-0.3826834323650903 => -0.38268343236509 or -0.3826834323650902") (GeniePlugin primSameClassAbsoluteStrokeDistanceMyPoints:otherPoints:myVectors:otherVectors:mySquaredLengths:otherSquaredLengths:myAngles:otherAngles:maxSizeAndReferenceFlag:rowBase:rowInsertRemove:rowInsertRemoveCount: "Cannot compile -- stack including temps is too deep") (QPickable2D pick:) "foo ifTrue: [^bar] ifFalse: [^baz]. ^huh?" (QUsersPane userEntryCompare:to:) "foo ifTrue: [^bar] ifFalse: [^baz]. ^huh?" (TShaderProgram vertexStrings) "foo ifTrue: []. => foo. => ." (TShaderProgram fragmentStrings) "foo ifTrue: []. => foo. => ." (TWindow zoomWindow:) "foo ifTrue: [^bar] ifFalse: [^baz]. ^huh?" "(PNMReadWriter nextImage) (Collection #ifEmpty:ifNotEmpty:) (Collection #ifEmpty:) (Collection #ifNotEmpty:ifEmpty:) (Text #alignmentAt:ifAbsent:) (ObjectWithDocumentation propertyAt:ifAbsent:)") They all list methods whose compilation of their decompilation won't match what one started with either because of limitations in the decompiler or optimizations in the compiler. For example if one writes foo ifTrue: []. the compiler will emit that as foo, eliminating the branch around the empty block. So when that is decompiled it'll decompile as foo. and the compiler will then compile that as empty. So ... When you decompile the source code of the method containing foo ifTrue: [] it contains a parse node that prints as foo ifTrue: []. But the bytecode contains only the code for foo. so when you decompile that you get foo. and when you compile that you get no bytecode generated for foo. Other examples include cases where to:by:do: is decompiled as whileTrue:, where the precision of a written float exceeds the representation of underlying float objects, and so on. I don't see the point of fixing these things in either the compiler or the decompiler. They're legal Smalltalk, the optimizations the compiler performs is perfectly reasonable, and there seems no point in e.g. annotating the bytecode with information on the optimization so that the decompilation would be correct. Hence I think we have to live with the work-around which is filtering-out expected failures. Implementing the filter as a list is poor; better would be to have rules that match expected failures, but that's potentially a lot of tricky work for not much benefit. What would help is a) a simple tool to look at the discrepancies side-by-side (I have a workspace I can send you), and b) people who run the tests updating the filer-list with exceptions and documenting what causes each exception. HTH Eliot > Cheers mike > > On Tuesday, January 19, 2010, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: > > Hi folks: does someone know what is this method for ? > > > > In my case, it has included the message saveImageSegments which I > rename it to saveImageSegments: > > > > So...what should I do ? I put saveImageSegments: instead of > saveImageSegments or I just remove it from there? > > > > Thanks > > > > Mariano > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2010