May 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Using Athens for real ...

by Tudor Girba

Indeed. This is so exciting! Doru On May 4, 2013, at 8:00 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > > On May 4, 2013, at 7:22 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 4 May 2013 12:31, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> Yes that view is very neat! Especially for debugging, maintaining the >>> Smalltalk immediate feedback principle :0 >>> >> >> and after i finish with path geometry calcucations, you can implement >> "clickable" things, >> no matter what their shape :) > > > arghhhhhh this is too cool :) > I want that ;D > The future will be massively fun :) > Stef > > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

May 4, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 2 regressions found. Tests.System.OSEnvironmentTest.testAtPut ToolsTest.Debugger.DebuggerTest.testBasic

May 4, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=ma… 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

May 4, 2013

[Pharo-project] [update 3.0] #30102

by Marcus Denker

30102 ----- 10514 temprarily remove BlockContext/BlockCloure code printing https://pharo.fogbugz.com/f/cases/10514/ 7376 Morph>>#fitInWorld https://pharo.fogbugz.com/f/cases/7376 10390 Failing on Build server: #testSystemAnnouncerIsUnique https://pharo.fogbugz.com/f/cases/10390 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.534.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Morphic-MarcusDenker.1413.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1425.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.436.diff

May 4, 2013

[Pharo-project] [regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=li… 1 regressions found. ToolsTest.Debugger.DebuggerTest.testBasic

May 4, 2013

Re: [Pharo-project] Pharo Logo SVG

by Igor Stasenko

On 4 May 2013 20:03, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > On Sat, May 4, 2013 at 7:49 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> And here how it looks in Athens.. >> yeah SVG importer needs more love, but my hands is too busy right now :( >> >> AthensSceneView new >> scene: (AthensSVGConverter fromFile: 'logo.svg'); >> openInWindow >> >> >> But this version of svg is much better, because old one contained >> bitmap data ... (brrr). > > > Really? I created the previous version of the logo and the main problem was > to remove bitmaps created during import from pdf and to be devoted to > original as much as possible. I supposed I removed all of them. > the one i tried had bitmap data inside. And i do not remember where i took it from (yes, from media files somewhere.. and i don't even know who made it and when).. > -- Pavel > -- Best regards, Igor Stasenko.

May 4, 2013

Re: [Pharo-project] How to Debug :D

by Igor Stasenko

On 4 May 2013 12:21, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 2013/5/4 stephane ducasse <stephane.ducasse(a)free.fr> >> >> >> On May 4, 2013, at 1:04 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> > Did i said already that i don't like how ASTInterpreter implemented? :) >> >> >> We will let perfection for later :) > > > It is not a question of perfection or so. > > Igor does not like that we interpret recursively the AST instead of with a > loop (ASTInterpreter>>interpret: calls itself again and again). He would > like to have a flatten-AST-interpreter, with a loop like: > > [currentASTNode hasNextNode] whileTrue: [ self interpret: currentASTNode > nextNode ]. more precisely , something like: | node | node := self initialASTNode. [node notNil ] whileTrue: [ node := self interpretSingleASTNode: node ]. > > But Camillo and I don't want that because it interprets a flatten AST, not > a tree. > Clement, it is not a question of "liking", it is question of how far you can go with it. With current implementation, if you try to interpret 10000 factorial, you will crash the image with stack overflow. And it is not about flattening a tree. Your input is always tree. The only difference is how you walk over it, and what (or how many) state you should keep while doing so. But please, do not take me wrong: having AST Interpreter even in current state is a big progress. -- Best regards, Igor Stasenko.

May 4, 2013

Re: [Pharo-project] Pharo Logo SVG

by Pavel Krivanek

On Sat, May 4, 2013 at 7:49 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > And here how it looks in Athens.. > yeah SVG importer needs more love, but my hands is too busy right now :( > > AthensSceneView new > scene: (AthensSVGConverter fromFile: 'logo.svg'); > openInWindow > > > But this version of svg is much better, because old one contained > bitmap data ... (brrr). > Really? I created the previous version of the logo and the main problem was to remove bitmaps created during import from pdf and to be devoted to original as much as possible. I supposed I removed all of them. -- Pavel > Thanks for taking care! > > -- > Best regards, > Igor Stasenko. >

May 4, 2013

Re: [Pharo-project] How to Debug :D

by stephane ducasse

Thanks. This is CSP passing style? I thought it was different. Now going to eat and after I will digest that. Thanks for the snippet. Stef > A trampoline looks like this: > > Foo >> trampoline: initialValue into: aUnaryBlock > | v | > v := [initialValue]. > [v isBlock] whileTrue: [v := aUnaryBlock value: v value]. > ^ v. > > and then used: > > | f factorial | > factorial := 1. > f := Foo new. > f trampoline: 10 into: [ :n | > n <= 0 > ifTrue: [factorial] > ifFalse: [factorial := factorial * n. [n - 1]]]. > > The important thing is that the block returns a value for the base > case/cases of the recursion, and a block that, when evaluated, will > yield the next value on which to recurse. (So the block replaces the > recursive call.) > > The trampoline thus turns the recursive algorithm into an iteration. > > frank > > On 4 May 2013 17:42, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> can you explain? >> Because I read something like that olong time ago and I forgot >> >> On May 4, 2013, at 5:41 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> >> So use a trampoline. Then you can define your recursion naturally, in >> constant stack space. >> >> frank >> >> On 04 May 2013, at 16:08, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >> I understand why he wants that :) >> no stack explosionâ¦ >> >> Stef >> >> On May 4, 2013, at 12:37 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> To be more precise, for the method : >> >> foo >> ^ 1 + 2 >> >> AST will be : >> ^ >> \ >> + >> / \ >> 1 2 >> >> AST Interpreter, to interpret ^, will do something like : >> start interpret ^ >> interpret subnode of ^ >> start interpret + >> interpret subnodes of + >> interpret 1 >> interpret 2 >> interpret + with subnodes interpretation result >> end interpret + >> interpret ^ with subnode interpretation result >> end interpret ^ >> >> Igor would like to have a flatten AST that would be in an array like : >> #( 1 2 + ^ ) >> Then you can interpret it with a loop >> [currentASTNode hasNextNode] whileTrue: [ self interpret: currentASTNode >> nextNode ]. >> And interpretation looks like : >> interpret 2 >> interpret 1 >> interpret + with two precedent results on stack >> interpret ^ with precedent result on stack >> >> 2013/5/4 ClÃ©ment Bera <bera.clement(a)gmail.com> >>> >>> 2013/5/4 stephane ducasse <stephane.ducasse(a)free.fr> >>>> >>>> >>>> On May 4, 2013, at 1:04 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>>> Did i said already that i don't like how ASTInterpreter implemented? :) >>>> >>>> >>>> We will let perfection for later :) >>> >>> >>> It is not a question of perfection or so. >>> >>> Igor does not like that we interpret recursively the AST instead of with a >>> loop (ASTInterpreter>>interpret: calls itself again and again). He would >>> like to have a flatten-AST-interpreter, with a loop like: >>> >>> [currentASTNode hasNextNode] whileTrue: [ self interpret: currentASTNode >>> nextNode ]. >>> >>> But Camillo and I don't want that because it interprets a flatten AST, >>> not a tree. >>> >>>> >>>>> >>>>> Nevertheless, it is useful.. and this case clearly demonstrates that. >>>>> >>>>> On 4 May 2013 00:14, Clara Allende <clari.allende(a)gmail.com> wrote: >>>>>> This is great news! Are you going to publish the code? it will come in >>>>>> handy >>>>>> for my summer of code :D >>>>>> >>>>> >>>>> Camillo has the image >>>>> >>>>>> >>>>>> On 3 May 2013 03:21, stephane ducasse <stephane.ducasse(a)free.fr> >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Begin forwarded message: >>>>>>> >>>>>>> From: Camillo Bruni <camillobruni(a)gmail.com> >>>>>>> Subject: [Lsehub-staff] How to Debug :D >>>>>>> Date: May 2, 2013 6:22:06 PM GMT+02:00 >>>>>>> To: RMoD private list <lsehub-staff(a)lists.gforge.inria.fr> >>>>>>> Reply-To: RMoD private list <lsehub-staff(a)lists.gforge.inria.fr> >>>>>>> >>>>>>> Igor: Camillo can you help me debugging this strange athens rendering >>>>>>> bug >>>>>>> Cami: sure >>>>>>> >>>>>>> Igor: where do you think the bug is? The green path jumps if I change >>>>>>> the >>>>>>> Y coordinate and it shouldn't... >>>>>>> Cami: no clue... >>>>>>> >>>>>>> Igor: Any clue how to get to the bug? >>>>>>> Cami: let's use the ASTInterpreter to interpret two methods with >>>>>>> different >>>>>>> transformation matrices and see when they diverge. >>>>>>> >>>>>>> Result: >>>>>>> ------- >>>>>>> - after 1h comparing AST Debugger is ready >>>>>>> - we run the two traces, they do NOT diverge => ???? >>>>>>> >>>>>>> Conclusion: >>>>>>> ----------- >>>>>>> Cairo, which was chosen as reference, did not properly draw the >>>>>>> path!!! >>>>>>> >>>>>>> So we should publish the code of the ComparingInterpreter a bit and >>>>>>> we >>>>>>> can use it for a few more tasks in Pharo ;) >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Best regards, >>>>> Igor Stasenko. >>>>> >>>> >>>> >>> >>> >> >> >> >> -- >> ClÃ©ment BÃ©ra >> Mate Virtual Machine Engineer >> BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq >> >> >> >

May 4, 2013

Re: [Pharo-project] Using Athens for real ...

by stephane ducasse

On May 4, 2013, at 7:22 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 4 May 2013 12:31, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> Yes that view is very neat! Especially for debugging, maintaining the >> Smalltalk immediate feedback principle :0 >> > > and after i finish with path geometry calcucations, you can implement > "clickable" things, > no matter what their shape :) arghhhhhh this is too cool :) I want that ;D The future will be massively fun :) Stef

May 4, 2013