On 25 Jul 2014, at 23:28, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Le 25/07/2014 23:15, Marcus Denker a écrit :
On 25 Jul 2014, at 21:51, Thierry Goubier <thierry.goubier@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).
Yes, we need that⦠there is code on the issue tracker, too:
https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-AS... Yes. What about the class definition format change described by Camillo?
Slowly working on it⦠very early (and right now broken) stage is in the image. And it is not yet decided how it will look like exactly⦠the only thing clear is that we need to use {#ivar1. #ivar2 . #boolean => BooleanSlot } instead of the strings⦠both for ivars and class vars⦠I want to finish and debug the machinery around and then start to play with it. I am a bit tempted to go the âbackward compatibleâ way and not use the term Slot but something like this: TestCase subclass: #RBProgramNodeTest instanceVariables :{#ivar1. #ivar2 . #boolean => BooleanSlot } classVariables: {#MyGlobal} category: 'AST-Tests-Coreâ Ah, and we need to think about âcategoryâ⦠as we now have packages. Marcus