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

Problem with streamsocket receiving

by kilon alios

so I have no issues sending data from pharo to python but I have a problem recieving data from python here is my method sendMessage: aString |stream errString isDataAvailable | stream := SocketStream openConnectionToHostNamed: '127.0.0.1' port: 4000 . stream sendCommand: aString. isDataAvailable := stream isDataAvailable . isDataAvailable inspect. isDataAvailable ifTrue: [ errString := stream nextLineCrLf . errString inspect. errString = '' ifFalse: [self error: errString.]] . stream close. I have used telnet to test the connection , telnet can receive the data fine and it displays it fine. I have encode the data as bytestring from python with ascii encoding and added both a carriage return and a line feed in the end ? whats wrong ? I tried most method in socket stream even upToEnd message and none gives back any data. What am I doing wrong ?

July 25, 2014

Re: [Pharo-dev] Metarepo Pharo 4.0 access

by Maximiliano Taborda

Thanks! El viernes, 25 de julio de 2014, Esteban Lorenzano <estebanlm(a)gmail.com> escribiÃ³: > I marked it as public access. > you should be able to commit. > > Esteban > > On 25 Jul 2014, at 20:04, Maximiliano Taborda <mtaborda(a)gmail.com > <javascript:_e(%7B%7D,'cvml','mtaborda(a)gmail.com');>> wrote: > > Hi. > I need access too. Could you give it to me? > My username is: maxi. Thanks. > > Regards. > Maxi > > > 2014-07-25 12:30 GMT-03:00 Marcus Denker <marcus.denker(a)inria.fr > <javascript:_e(%7B%7D,'cvml','marcus.denker(a)inria.fr');>>: > >> >> On 25 Jul 2014, at 17:06, Serge Stinckwich <serge.stinckwich(a)gmail.com >> <javascript:_e(%7B%7D,'cvml','serge.stinckwich(a)gmail.com');>> wrote: >> >> > Can someone give me access to the metarepo for Pharo 4.0 ? >> >> done >> >> >> > >

July 25, 2014

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

by Thierry Goubier

Le 25/07/2014 23:46, Marcus Denker a Ã©crit : > On 25 Jul 2014, at 23:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 25 Jul 2014, at 23:28, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >>> Le 25/07/2014 23:15, Marcus Denker a Ã©crit : >>>> On 25 Jul 2014, at 21:51, 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). >>>>> >>>> Yes, we need thatâ¦ >>>> there is code on the issue tracker, too: >>>> >>>> https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… >>> 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â I'd be tempted not to write an adhoc mini-language inside the instanceVariables array. Why not just something like: TestCase subclass: #RBProgramNodeTest instanceVariables :{#ivar1. #ivar2 . BooleanSlot named: #boolean } classVariables: {#MyGlobal} category: 'AST-Tests-Coreâ Maybe, with packages: TestCase subclass: #RBProgramNodeTest instanceVariables :{#ivar1. #ivar2 . BooleanSlot named: #boolean } classVariables: {#MyGlobal} package: #'AST-Tests-Coreâ Not much more: we can allways drag and drop to the right place if needed, query if no package is given, cut and paste for keyboard use. If you want the grand show, I'll make you a wizard for creating classes with at least 10 steps ;) >> >> Ah, and we need to think about âcategoryââ¦ as we now have packages. >> > But for the âwe need some kind of AST like structureâ it changes nothing: this is still a message send, > but we need to reason about a class definition if we want to have suggestions (and with them e.g. BreakPoints > on variables) working. > > Marcus > I have that working without a real "ClassDefinition node" at the moment. Really very convenient to have the refactorings on instance variables working straight out of the class description text pane by just selecting the instance variable name in the string. Class definitions are either normal messages (for example in code creating a class by hand) or descriptions visible in browsers (interactive use). In the first case, you should not interpret them as class definitions since the class may/probably does not exist at that point. It is then just a message. In the second case, the GUI can ask for interpretation of the message into a class definition. I think this is how Gisela solution works, no? Thierry

July 25, 2014

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

by Marcus Denker

On 25 Jul 2014, at 23:44, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 25 Jul 2014, at 23:28, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > >> Le 25/07/2014 23:15, Marcus Denker a Ã©crit : >>> On 25 Jul 2014, at 21:51, 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). >>>> >>> Yes, we need thatâ¦ >>> there is code on the issue tracker, too: >>> >>> https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… >> 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. > But for the âwe need some kind of AST like structureâ it changes nothing: this is still a message send, but we need to reason about a class definition if we want to have suggestions (and with them e.g. BreakPoints on variables) working. Marcus

July 25, 2014

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

by Marcus Denker

On 25 Jul 2014, at 23:28, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 25/07/2014 23:15, Marcus Denker a Ã©crit : >> On 25 Jul 2014, at 21:51, 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). >>> >> Yes, we need thatâ¦ >> there is code on the issue tracker, too: >> >> https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… > 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

July 25, 2014

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

by Thierry Goubier

Le 25/07/2014 23:15, Marcus Denker a Ã©crit : > On 25 Jul 2014, at 21:51, 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). >> > Yes, we need thatâ¦ > there is code on the issue tracker, too: > > https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… Yes. What about the class definition format change described by Camillo? Thierry

July 25, 2014

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

by Marcus Denker

On 25 Jul 2014, at 21:51, 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). > Yes, we need thatâ¦ there is code on the issue tracker, too: https://pharo.fogbugz.com/f/cases/10983/Represent-a-class-definition-with-A… Marcus

July 25, 2014

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

by Marcus Denker

On 25 Jul 2014, at 21:52, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 25/07/2014 20:55, Marcus Denker a Ã©crit : >> >> On 25 Jul 2014, at 20:49, Thierry Goubier <thierry.goubier(a)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? > yes! Marcus

July 25, 2014

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

by Marcus Denker

On 25 Jul 2014, at 21:59, kilon alios <kilon.alios(a)gmail.com> wrote: > 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. :) > Yes, Smalltalk syntax is very simple compared to most other languages, see http://code.uko.tymchuk.me/2013/02/grammars-complexity-comparison.html

July 25, 2014

Other MenuMorph facts

by stepharo

(MenuMorph selectors select: [ :each | 'add*' match: each ]) size 42 number of isKindOf: 11 for a single class I imagine that this is the top. Stef

July 25, 2014