June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Opal ?

by Marcus Denker

On Jun 21, 2012, at 3:36 PM, Goubier Thierry wrote: >> >> It seem the final objective is to send something to Esug ? > > If I make it in time, yes. Ok, it seems I shouldn't try the RecompileTests then? No, I don't use them right now... > So far, I have only the IRDecompilerTests which are failing. That is the one that depends on PetitParser (experiment, not needed will be done after the rest works). State of things: 1) Backend. BC->IR->BC seem ok. - IRComparer new compareImage shows 16 differences, mostly pop-combining and unused code after return skipped, seems good. (this compares #abstractSymbolic on the bytecode level) - IRComparer new compareImageFrameSize 10 methods have smaller framesize , 2 a larger one. This needs to be checked. 2) AST to IR AST-IR-BC - OCRecompiler new inspect; recompileImage shows 10 problems. 2 are undeclareds, one is related to primitive errors (which is not yet supported). Rest are wrong stack depth on jump targets in the backend. - CompilerComparer new compare: Morph (this compares #abstractSymbolic on the bytecode level) ==> 39 differences, need to be analyzed (same for the whole image). 3) Missing: IR->AST, mapping BC to text offset needs to be checked, and then integration into the system. Error handling, things like that. On the good side, OCRecompiler new doInstallMethods; recompileImage seems to work. (did not yet run too many tests, first the rest of the problems need to be fixed). Marcus -- Marcus Denker -- http://marcusdenker.de

June 21, 2012

Re: [Pharo-project] Worskpace question

by Guillermo Polito

On Thu, Jun 21, 2012 at 3:44 PM, Stefan Marr <smalltalk(a)stefan-marr.de>wrote: > > On 21 Jun 2012, at 15:11, Hilaire Fernandes wrote: > > > I want to see the animation of the growing morph. > > Instead I get nothing. > > > > To get the animation, you have to enclose the loop in a forked process, > > but it is inelegant: > > Isn't the doIt evaluated in the UI processes? > > It is! > I bet there is a Morphic API that allows you to process the next drawing > request. > Hmm, that sounds like forcing the framework... I think that having a second process is the right way... > If the doIt is not evaluated in the UI process, just to a `Processor > yield` after every step you want to see. > Sometimes, when processing in different process, the correct way is to send updates to the UI process through World addDeferredUIMessage: [ ... ] Cheers, Guille > > Best regards > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > >

June 21, 2012

Re: [Pharo-project] Worskpace question

by Stefan Marr

On 21 Jun 2012, at 15:11, Hilaire Fernandes wrote: > I want to see the animation of the growing morph. > Instead I get nothing. > > To get the animation, you have to enclose the loop in a forked process, > but it is inelegant: Isn't the doIt evaluated in the UI processes? I bet there is a Morphic API that allows you to process the next drawing request. If the doIt is not evaluated in the UI process, just to a `Processor yield` after every step you want to see. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

June 21, 2012

Re: [Pharo-project] Opal ?

by Goubier Thierry

Le 21/06/2012 15:30, Jean Baptiste Arnaud a Ã©crit : > > On Jun 21, 2012, at 3:22 PM, Goubier Thierry wrote: > >> Le 21/06/2012 15:16, Jean Baptiste Arnaud a Ã©crit : >>> >>> I understand but the logic itself will not change. The design is done. >>> The used case too. But it is not perfect but you put a lot of energy >>> on it. >>> M. Goubier want to to port its code, i think it should try, and if some >>> problem happen raise the issue. Instead to try and spend week on the old >>> compiler. >>> The experiment match perfectly with the opal Spirit. And we have someone >>> motivated to perform a experiment on Opal, don't say no. >> >> And you need to be motivated. > > It seem the final objective is to send something to Esug ? If I make it in time, yes. Ok, it seems I shouldn't try the RecompileTests then? So far, I have only the IRDecompilerTests which are failing. Thierry >> Opal depends on Petit Parser, which depends on RB, where it should >> stop (I hope). >> >> Thierry >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > Best Regards > Jean Baptiste Arnaud > jbaptiste.arnaud(a)gmail.com <mailto:jbaptiste.arnaud@gmail.com> > > > > > > > -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 21, 2012

Re: [Pharo-project] Opal ?

by Goubier Thierry

Le 21/06/2012 15:28, Frank Shearar a Ã©crit : > On 21 June 2012 14:22, Goubier Thierry<thierry.goubier(a)cea.fr> wrote: >> Le 21/06/2012 15:16, Jean Baptiste Arnaud a Ã©crit : >>> >>> >>> I understand but the logic itself will not change. The design is done. >>> The used case too. But it is not perfect but you put a lot of energy on >>> it. >>> M. Goubier want to to port its code, i think it should try, and if some >>> problem happen raise the issue. Instead to try and spend week on the old >>> compiler. >>> The experiment match perfectly with the opal Spirit. And we have someone >>> motivated to perform a experiment on Opal, don't say no. >> >> >> And you need to be motivated. >> >> Opal depends on Petit Parser, which depends on RB, where it should stop (I >> hope). > > PetitParser does not depend on RB. It depends on AST-Core and > AST-Compiler, which are (small) _parts_ of RB. Thanks. It's hard to guess which subsets of RB are needed when you encounter an error with some RB prefixed classes when loading a package. Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

June 21, 2012

Re: [Pharo-project] Opal ?

by Marcus Denker

On Jun 21, 2012, at 3:30 PM, Jean Baptiste Arnaud wrote: > > On Jun 21, 2012, at 3:22 PM, Goubier Thierry wrote: > >> Le 21/06/2012 15:16, Jean Baptiste Arnaud a Ã©crit : >>> >>> I understand but the logic itself will not change. The design is done. >>> The used case too. But it is not perfect but you put a lot of energy on it. >>> M. Goubier want to to port its code, i think it should try, and if some >>> problem happen raise the issue. Instead to try and spend week on the old >>> compiler. >>> The experiment match perfectly with the opal Spirit. And we have someone >>> motivated to perform a experiment on Opal, don't say no. >> >> And you need to be motivated. > > It seem the final objective is to send something to Esug ? > No, the final objective is to finish. Marcus -- Marcus Denker -- http://marcusdenker.de

June 21, 2012

Re: [Pharo-project] Array size in inspector

by Damien Cassou

On Thu, Jun 21, 2012 at 2:50 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > It doens't need to be StackOverflow necessary. We also have: > "A friendly place where any question about pharo is welcome" > <pharo-users(a)lists.gforge.inria.fr>, you are right. I've just update the Pharo website to give more emphasis to this user mailing list and to stackoverflow. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

June 21, 2012

[Pharo-project] [update 2.0] #20149

by Esteban Lorenzano

20149 ----- Issue 6097: Bad source and changes path for one click on Windows (Jenkins?) http://code.google.com/p/pharo/issues/detail?id=6097 Issue 6096: WindowsResolver sends "self default" but no method #default is implemented http://code.google.com/p/pharo/issues/detail?id=6096 (windows should be working now)

June 21, 2012

Re: [Pharo-project] Opal ?

by Jean Baptiste Arnaud

On Jun 21, 2012, at 3:22 PM, Goubier Thierry wrote: > Le 21/06/2012 15:16, Jean Baptiste Arnaud a Ã©crit : >> >> I understand but the logic itself will not change. The design is done. >> The used case too. But it is not perfect but you put a lot of energy on it. >> M. Goubier want to to port its code, i think it should try, and if some >> problem happen raise the issue. Instead to try and spend week on the old >> compiler. >> The experiment match perfectly with the opal Spirit. And we have someone >> motivated to perform a experiment on Opal, don't say no. > > And you need to be motivated. It seem the final objective is to send something to Esug ? > Opal depends on Petit Parser, which depends on RB, where it should stop (I hope). > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > Best Regards Jean Baptiste Arnaud jbaptiste.arnaud(a)gmail.com

June 21, 2012

Re: [Pharo-project] Opal ?

by Marcus Denker

On Jun 21, 2012, at 3:25 PM, Jean Baptiste Arnaud wrote: >>> >>> For now, I've just discovered there is a dependency on petit parser. I'll break my 1.4 image soon :-) > The dependency is not just for Decompiling ? > yes, just an experiment... -- Marcus Denker -- http://marcusdenker.de

June 21, 2012