February 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Smart Suggestions based on text selection such as extract method seems to be broken.

by Thierry Goubier

Stef, Look if smart suggestion isn't affected by the token / ast change. Thierry Le 28 fÃ©vr. 2015 18:55, "stepharo" <stepharo(a)free.fr> a Ã©crit : > Hi > > Smart Suggestions based on text selection such as extract method seems to > be broken. > if I press command-T on a node, when I select extract method, the complete > or part of the method > is selected. I thought that it was working. > > Stef > >

Feb. 28, 2015

Re: [Pharo-dev] [Reflectivity] Compiler AST transformation Plugins

by Thierry Goubier

Cool. Per class customizable code rewriting. Great for extendable frameworks. Thierry Le 28 fÃ©vr. 2015 16:18, "Marcus Denker" <marcus.denker(a)inria.fr> a Ã©crit : > A simple AST-transformer plugin architecture for Opal... > > -> subclass OCCompilerASTPlugin > -> implement #transform e.g. > > transform > | rule | > rule := RBParseTreeRewriter replaceLiteral: 42 with: 'meaning of life'. > rule executeTree: ast. > ^ast > > The plugin can be activated *per class hierarchy* by overriding #compiler > > compiler > "the example plugin is active for this class" > ^super compiler addPlugin: ASTPluginMeaningOfLife. > > or of course for a single compilation: > > (Smalltalk compiler addPlugin: ASTPluginMeaningOfLife) evaluate: '42' > > For review here: > > https://pharo.fogbugz.com/f/cases/15019/Compiler-AST-transformation-Plugins > > Marcus >

Feb. 28, 2015

[Reflectivity] Trello Board

by Marcus Denker

Hi, I added a board for this one, too https://trello.com/b/m5cxaAxB/reflectivity <https://trello.com/b/m5cxaAxB/reflectivity> Marcus

Feb. 28, 2015

[Pharo4][Slots] Trello Board

by Marcus Denker

Hi, I want to try to keep the TODO in a Trello board, this should make it easier for people that want to help to pick something todoâ¦ I will post some simple actions, too. (for example tests that need to be written). https://trello.com/b/d59lgZFB/slots <https://trello.com/b/d59lgZFB/slots> Marcus

Feb. 28, 2015

[Reflectivity] Compiler AST transformation Plugins

by Marcus Denker

A simple AST-transformer plugin architecture for Opal... -> subclass OCCompilerASTPlugin -> implement #transform e.g. transform | rule | rule := RBParseTreeRewriter replaceLiteral: 42 with: 'meaning of life'. rule executeTree: ast. ^ast The plugin can be activated *per class hierarchy* by overriding #compiler compiler "the example plugin is active for this class" ^super compiler addPlugin: ASTPluginMeaningOfLife. or of course for a single compilation: (Smalltalk compiler addPlugin: ASTPluginMeaningOfLife) evaluate: â42â For review here: https://pharo.fogbugz.com/f/cases/15019/Compiler-AST-transformation-Plugins Marcus

Feb. 28, 2015

Zn using String>>#substrings:

by Sven Van Caekenberghe

Hi, Zinc HTTP Components' latest stable version 2.6.2 which was integrated in Pharo 4.0 is using String>>#substrings: instead of String>>#subStrings: For Pharo 4 this is of course OK. String>>#substrings: was also added to Pharo 3.0. For Pharo 2.0 Zinc will load a 'forward compatibility' package to add the missing method. If you are working in/with an older/existing Pharo 3.0 things will not be solved automatically. Either add the method yourself, or load 'Zinc-pharo2-forward-compatibility' manually. It might even be possible to update the image, but I haven't tried that. HTH, Sven

Feb. 28, 2015

Re: [Pharo-dev] Unkownselector Warning: removed for now

by Marcus Denker

> On 28 Feb 2015, at 09:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > With the AST changes, we now create the RBMessageNode with a selector. Before it was an array of parts, > which means that the Symbol was not created in the Parser. > > This means, we used to check in the Semantic Analysis when visiting the RBMessageNode if the selector already > is in the Symboltable and raise a warning else. > > After discussing with Pablo, we decided to not implement this functionality on the level of the Parser (where the symbol > is now created). > > - this is purely a âlintâ like warning. It has nothing to do with Syntax (nor with semantics). > - it should be implemented on the tool level > - it should not raise the annoying dialog, but instead put a red line under the symbol > - The non existing selector is coloured red by the syntax highlighting already now (until you acceptâ¦) > > Thus: We will for now remove the warning, it will come back as part of the IDE later. There we will be able to do > a *much* better job, too. (e.g. not check against existing symbols, but existing method selectors). > e.g. Symbol allSymbols size "59965". (CompiledMethod allInstances collect: #selector) asSet size â42260" Marcus

Feb. 28, 2015

Unkownselector Warning: removed for now

by Marcus Denker

Hi, With the AST changes, we now create the RBMessageNode with a selector. Before it was an array of parts, which means that the Symbol was not created in the Parser. This means, we used to check in the Semantic Analysis when visiting the RBMessageNode if the selector already is in the Symboltable and raise a warning else. After discussing with Pablo, we decided to not implement this functionality on the level of the Parser (where the symbol is now created). - this is purely a âlintâ like warning. It has nothing to do with Syntax (nor with semantics). - it should be implemented on the tool level - it should not raise the annoying dialog, but instead put a red line under the symbol - The non existing selector is coloured red by the syntax highlighting already now (until you acceptâ¦) Thus: We will for now remove the warning, it will come back as part of the IDE later. There we will be able to do a *much* better job, too. (e.g. not check against existing symbols, but existing method selectors). Marcus

Feb. 28, 2015

Re: [Pharo-dev] The evil twin in 40516

by Marcus Denker

> On 27 Feb 2015, at 23:11, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 27/02/2015 20:26, Marcus Denker a Ã©crit : >> >>> On 27 Feb 2015, at 19:48, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> Hi Markus, >>> >>> if I understand correctly some of the possibilities: >>> >>> - I can use RBParseTreeSearcher / RBParseTreeRewriter on the twin AST. >>> >>> (any example how to install / invalidate the twin AST after an effective RBParseTreeRewriter operation?) >>> >> Yes, but I would do it on a copyâ¦ that is, do the change in run:with:in: on a copy, generate code from that, >> keep the original. >> An AST that follows the text is kind of nice for e.g. navigation. >> >>> - Any change to the Twin AST is reflected in the method bytecode (as long as one does invalidate). >>> >> yes. >> >>> This would mean being able to put tracing code with RB patterns, no? And without having to do a recompilation of the traced method? >>> >> >> Yes. At first I want to have something simple: a MOP based on the MetaLinks. But one could do the same with RB transformations: >> put them as annotation on the method, then on recompile take them into account. > > Maybe I'm not understanding everything, so would that be correct: > > - If I inject additional behavior with meta-links, then they just annotate the AST and do not really change it. > > Now, since writing dedicated ast visitors takes quite some code, what could work is to have a RBParseTreeMetaWriter: use a RB pattern to find the right ast node, and add whatever meta-link there. > Yes. The experiment right now does not use the rewriter, but we should have a look. Marcus

Feb. 28, 2015

Re: [Pharo-dev] About slots and syntax

by Marcus Denker

> On 27 Feb 2015, at 20:47, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > On 27 February 2015 at 16:13, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Are we sure that we want to use that => > I thought about = but this is not an assignement this is a declaration and normally we use | for declaration. > So what would be other alternatives before the world use => > Yes, everything is not yet fixedâ¦ > But | for local variables is syntax, and it's used as a bracket. It's also the logical or operatorâ¦ > > I'd propose :: because it recalls the :x for block arguments, or -- because it looks like a typographic em-dash: > > slots: { > #local -- ProcessLocalSlot. > #foo -- SomeOtherKindOfSlot. > interesting! > By the way, using an operator in this way is a little strange: what you read does not match the usual precedence rules (#default: is not a factory method of ProcessLocalSlot, it's an accessor on the result of #local => ProcessLocalSlot) > Oh, true.. that needs to be well documented. (having the method in addition on the class side makes sense, I guess). > > Then I still do not understand why we have empty classVariables: to me it does not make sense. I do not get why we like to have empty collections for the sake of having empty collections. We are trapped in some strange ways of thinking. > > Are there strong arguments against a cascade ? Good question. What is clear is that changing methods like subclass:instanceVariableNames:classVariableNames:category: and adding all variants is annoying. E.g. the âwe do not show the empty poolâ (and the slot definiton) is still just done âon the surfaceâ in Natutilus (#definitionForNautilus) as changing #definition is actually tricky to get all the tests green (esp Monticello). https://pharo.fogbugz.com/f/cases/14063/clean-up-definitionForNautilus <https://pharo.fogbugz.com/f/cases/14063/clean-up-definitionForNautilus> Marcus

Feb. 28, 2015