July 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About deprecating UpdatingMenuMorph

by stepharo

We have some other users (9) addUpdating: action: On 25/7/14 21:55, stepharo wrote: > Hi guys > > I would like to simplify the Menu logic and I would like to remove the > UpdatingMenuItemMorph. > So far it is only use in Spec with autoRefresh. > I really think that if we want to give a chance to Morphic and its > future incarnation we should > rationalize what we have. > > Stef > >

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by kilon alios

Oh yes yes thank you, thank you both, this is exactly what I wanted. No need to send me your code ,I can parse this with regex I am already parsing pharo code with regex and it has been easy enough. It worked for messages like unary and keywords but I wanted to do more complex pharo syntax parsing to python. But if your code follows a better approach is more than welcomed. This is the first time I actually try to parse full syntax of a language. Basically what you gave me looks good enough to do what I want, I will also look at the classes themselves, I am surprised how small package AST is. I guess that the beauty of the smalltalk syntax. :) On Fri, Jul 25, 2014 at 10:51 PM, Thierry Goubier <thierry.goubier(a)gmail.com > wrote: > Le 25/07/2014 21:42, kilon alios a Ã©crit : > > ok we are getting somewhere, the problem is that if I do > > (SomeClass compiledMethodAt: #nameOfMethod it will look only in the > instance side for method, how I look also for class methods ? Also how I > can return source of class ? to be specific I need the names of instance > variables, class variables and class instance variables . > > For the class method: > > SomeClass class compiledMethodAt: #nameOfClassMethod > > For the instance variable, etc... SomeClass definition will give you that. > But it's a bit tricky to parse; for example, if you want a reification > (instance variable name is recognized as instance variable name in the > ast), I have some code which does: parse, rewrite and reparse on a class > definition (for the smart suggestion thing). > > > > Markus that beautiful nodesDo outputs the full syntax tree yeap > definetly what I need to do what I want. > > Does the ast method applies also to classes or only compiled methods ? > > Only source code. A class definition is not entirely code (see above). > > > > On Fri, Jul 25, 2014 at 9:59 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> >> >> as example how to query the AST see the method #accessesSlot: >> >> accessesSlot: aSlot >> self ast nodesDo: [ :node | >> node isVariable and: [ >> node isInstance and: [ >> (node binding slot == aSlot) >> ifTrue: [^true]]]]. >> ^false >> >> > Thanks Markus, this is a nice example. > > Thierry >

July 25, 2014

About deprecating UpdatingMenuMorph

by stepharo

Hi guys I would like to simplify the Menu logic and I would like to remove the UpdatingMenuItemMorph. So far it is only use in Spec with autoRefresh. I really think that if we want to give a chance to Morphic and its future incarnation we should rationalize what we have. Stef

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by Thierry Goubier

Le 25/07/2014 20:55, Marcus Denker a Ã©crit : > > On 25 Jul 2014, at 20:49, Thierry Goubier <thierry.goubier(a)gmail.com > <mailto:thierry.goubier@gmail.com>> wrote: > >> Ok, as above, it should be understood as: >> >> ast := RBParser parseMethod: (Object compiledMethodAt: #printString) >> onError: [ :msg :ps | ]. >> ast doSemanticAnalysisIn: self sourceClass. >> > > There is a method on CompiledMethod called #ast that called the > parser + semantic analysis: > > ( Object compiledMethodAt: #halt ) ast > > No need to know details about RBParser. > Marcus Cool. Thanks. But when you start to use the ast, you'd better have a look into the RBParser / RBAST stuff, no? Thierry

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by Thierry Goubier

Le 25/07/2014 21:42, kilon alios a Ã©crit : > ok we are getting somewhere, the problem is that if I do > > (SomeClass compiledMethodAt: #nameOfMethod it will look only in the > instance side for method, how I look also for class methods ? Also > how I can return source of class ? to be specific I need the names of > instance variables, class variables and class instance variables . For the class method: SomeClass class compiledMethodAt: #nameOfClassMethod For the instance variable, etc... SomeClass definition will give you that. But it's a bit tricky to parse; for example, if you want a reification (instance variable name is recognized as instance variable name in the ast), I have some code which does: parse, rewrite and reparse on a class definition (for the smart suggestion thing). > > Markus that beautiful nodesDo outputs the full syntax tree yeap > definetly what I need to do what I want. > > Does the ast method applies also to classes or only compiled methods ? Only source code. A class definition is not entirely code (see above). > > > On Fri, Jul 25, 2014 at 9:59 PM, Marcus Denker <marcus.denker(a)inria.fr > <mailto:marcus.denker@inria.fr>> wrote: > > > > as example how to query the AST see the method #accessesSlot: > > accessesSlot: aSlot > self ast nodesDo: [ :node | > node isVariable and: [ > node isInstance and: [ > (node binding slot == aSlot) > ifTrue: [^true]]]]. > ^false > > Thanks Markus, this is a nice example. Thierry

July 25, 2014

Re: [Pharo-dev] smalltalkhub should be working now

by Esteban Lorenzano

Iâm not sure. Probably a concurrency issue (undetected so far) made a duplicate version of Pharo team. Then because of the duplicate Pharo team, a second Pharo40Inbox was created. Then some people committed slices to the new (and empty) Pharo40Inbox. So, the solution was: - unify both projects (so all slices are in just one place) - detect and remove wrong Pharo40Inbox - detect and remove wrong Pharo team - review all structure so it has correct ids, etc. (viewed like this, looks easy, but it was a lot of tedious work :) ) On 25 Jul 2014, at 21:42, stepharo <stepharo(a)free.fr> wrote: > Thanks you both. > Could you explain a bit what was the problem? > Stef > > On 25/7/14 15:26, Esteban Lorenzano wrote: >> with the invaluable help of Nico, we managed to fixed it. >> (or at least we *think* we managed to fix it :D ) >> >> Esteban >> >> >> > >

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by kilon alios

ok we are getting somewhere, the problem is that if I do (SomeClass compiledMethodAt: #nameOfMethod it will look only in the instance side for method, how I look also for class methods ? Also how I can return source of class ? to be specific I need the names of instance variables, class variables and class instance variables . Markus that beautiful nodesDo outputs the full syntax tree yeap definetly what I need to do what I want. Does the ast method applies also to classes or only compiled methods ? On Fri, Jul 25, 2014 at 9:59 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Jul 2014, at 20:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 25 Jul 2014, at 20:49, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > Le 25/07/2014 20:37, kilon alios a Ã©crit : > > I don't understand how to use aClass definition from workspace nor I > understand your selector message. > > (aClass compiledMethodAt: self selector) sourceCode , self would imply > that i try to operate this from inside another class with self selector > being the method itself at the time executed ? > > No, just that you can write: > > (Object compiledMethodAt: #printString) sourceCode > > That's me not sanitizing my code samples (lifting it from the AltBrowser) > > > However because I try to parse pharo syntax to python code, the classes > that I am parsing are unrelated to the parser class itself so I don't see > how self selector would be relevant here. > > > I also don't understand > > ast := RBParser parseMethod: aTarget text asString onError: [ :msg > :pos | ^ self ]. > ast doSemanticAnalysisIn: self sourceClass > > what is aTarget ? > > > Ok, as above, it should be understood as: > > ast := RBParser parseMethod: (Object compiledMethodAt: #printString) > onError: [ :msg :ps | ]. > ast doSemanticAnalysisIn: self sourceClass. > > > There is a method on CompiledMethod called #ast that called the parser > + semantic analysis: > > ( Object compiledMethodAt: #halt ) ast > > No need to know details about RBParser. > > > as example how to query the AST see the method #accessesSlot: > > accessesSlot: aSlot > self ast nodesDo: [ :node | > node isVariable and: [ > node isInstance and: [ > (node binding slot == aSlot) > ifTrue: [^true]]]]. > ^false > >

July 25, 2014

Re: [Pharo-dev] smalltalkhub should be working now

by stepharo

Thanks you both. Could you explain a bit what was the problem? Stef On 25/7/14 15:26, Esteban Lorenzano wrote: > with the invaluable help of Nico, we managed to fixed it. > (or at least we *think* we managed to fix it :D ) > > Esteban > > >

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by Marcus Denker

On 25 Jul 2014, at 20:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Jul 2014, at 20:49, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > >> Le 25/07/2014 20:37, kilon alios a Ã©crit : >>> I don't understand how to use aClass definition from workspace nor I understand your selector message. >>> >>> (aClass compiledMethodAt: self selector) sourceCode , self would imply that i try to operate this from inside another class with self selector being the method itself at the time executed ? >> No, just that you can write: >> >> (Object compiledMethodAt: #printString) sourceCode >> >> That's me not sanitizing my code samples (lifting it from the AltBrowser) >> >>> >>> However because I try to parse pharo syntax to python code, the classes that I am parsing are unrelated to the parser class itself so I don't see how self selector would be relevant here. >>> >>> >>> I also don't understand >>> >>> ast := RBParser parseMethod: aTarget text asString onError: [ :msg :pos | ^ self ]. >>> ast doSemanticAnalysisIn: self sourceClass >>> >>> what is aTarget ? >> >> Ok, as above, it should be understood as: >> >> ast := RBParser parseMethod: (Object compiledMethodAt: #printString) onError: [ :msg :ps | ]. >> ast doSemanticAnalysisIn: self sourceClass. >> > > There is a method on CompiledMethod called #ast that called the parser + semantic analysis: > > ( Object compiledMethodAt: #halt ) ast > > No need to know details about RBParser. > as example how to query the AST see the method #accessesSlot: accessesSlot: aSlot self ast nodesDo: [ :node | node isVariable and: [ node isInstance and: [ (node binding slot == aSlot) ifTrue: [^true]]]]. ^false

July 25, 2014

Re: [Pharo-dev] Returning the source of a class as a string

by Marcus Denker

On 25 Jul 2014, at 20:49, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 25/07/2014 20:37, kilon alios a Ã©crit : >> I don't understand how to use aClass definition from workspace nor I understand your selector message. >> >> (aClass compiledMethodAt: self selector) sourceCode , self would imply that i try to operate this from inside another class with self selector being the method itself at the time executed ? > No, just that you can write: > > (Object compiledMethodAt: #printString) sourceCode > > That's me not sanitizing my code samples (lifting it from the AltBrowser) > >> >> However because I try to parse pharo syntax to python code, the classes that I am parsing are unrelated to the parser class itself so I don't see how self selector would be relevant here. >> >> >> I also don't understand >> >> ast := RBParser parseMethod: aTarget text asString onError: [ :msg :pos | ^ self ]. >> ast doSemanticAnalysisIn: self sourceClass >> >> what is aTarget ? > > Ok, as above, it should be understood as: > > ast := RBParser parseMethod: (Object compiledMethodAt: #printString) onError: [ :msg :ps | ]. > ast doSemanticAnalysisIn: self sourceClass. > There is a method on CompiledMethod called #ast that called the parser + semantic analysis: ( Object compiledMethodAt: #halt ) ast No need to know details about RBParser. Marcus

July 25, 2014