- Pharo-users - lists.pharo.org

Re: [Pharo-users] Seeing all the methods that is used in a method

by ClÃ©ment Bera

2014-08-07 10:47 GMT+02:00 aria2end <aria2end(a)gmail.com>: > Yes Exactly. I want to see all the potential methods called from from this > method which is the second case. but I receive error using that script. > > MessageNotUnderstood: ByteSymbol>>implementors > > Ok this method is implemented in the image I use (Pharo-40151). The code is Symbol>>implementors ^SystemNavigation new allImplementorsOf: self Sorry I didn't know this code was not in Pharo 3. > > > > > -- > View this message in context: > http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by Henrik Johansen

On 07 Aug 2014, at 10:41 , kilon alios <kilon.alios(a)gmail.com> wrote: > cant you also use the ast to find out how exactly Pharo which object and which method it executes ? No. Consider: #do: aBlock aBlock value Finding the methods actually executed by this is a hard problem. Youâd at least need inferred types (to find the values of block that are actually sent to THIS #do: implementation) to even attempt to make a somewhat accurate prediction. Cheers, Henry

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by Tudor Girba

Hi, I would suggest that you take a look at the support from GTInspector to understand the AST. For that, you can just download the latest moose image ( https://ci.inria.fr/moose/job/moose-5.0/lastSuccessfulBuild/artifact/moose-…) and inspect your method. You will get multiple views on that method including the AST and a preview of the sources. See the picture from the attachment. Cheers, Doru [image: Inline image 2] On Thu, Aug 7, 2014 at 10:39 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Marcus has shown me previously ast with nodesDo: for example this code > show me the full ast for my class method blenderOpen of my class Ephestos. > > (Ephestos class compiledMethodAt: #blenderOpen ) ast nodesDo: [ :node| > node inspect] > > and it opens one inspector per node > > messages that are "method calls" are nodes of RBMessageNode class. I see a > instance variable "selector" which returns the name of the selector and an > instance variable "receiver" returns the name of the receiver. Instance > variable "parent" describes the container of the message . For example in > my case the only RBMessageNode is contained inside a variable assignment. > > So I think its a good start for finding "method calls" messages. > > > On Thu, Aug 7, 2014 at 11:18 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >> >> >> >> 2014-08-07 5:11 GMT+02:00 aria2end <aria2end(a)gmail.com>: >> >> Hi, I know that I can see senders and implementers of a method but is >>> there >>> any way to see all methods that are used in a method ? >>> >> >> This is impossible. The method called for each message send can only been >> known at runtime, because it depends on the receiver class. The only thing >> you could see is the list of selectors (name of methods) called from this >> method. This is possible by sending #messages to the compiledMethod. >> >> Example: >> >> you have a method named #foo:bar: implemented in MyClass: >> MyClass>>foo: arg1 bar: arg2 >> ^ self baz: arg1 + arg2 >> >> You can open a workspace, and run: >> (MyClass >>#foo:bar:) messages >> >> which answers: >> a Set(#baz: #+) >> >> but you cannot see the methods called, because depending on the class of >> arg1, the method called for #+ may be any of these methods: >> AJMem>>#+ Collection>>#+ Color>>#+ DateAndTime>>#+ Duration>>#+ Float>>#+ >> FloatArray>>#+ Fraction>>#+ Integer>>#+ Interval>>#+ KMComposedModifier>>#+ >> KMKeyCombinationSequence>>#+ KMModifier>>#+ KMNoShortcut>>#+ >> LargeInteger>>#+ Number>>#+ Point>>#+ ROAbstractComponent>>#+ ROShape>>#+ >> ROShape class>>#+ ScaledDecimal>>#+ SmallInteger>>#+ String>>#+ >> Timespan>>#+ TraitComposition>>#+ TraitDescription>>#+ >> TraitTransformation>>#+ WordArray>>#+ TComposingDescription>>#+ >> >> Or perhaps you want to see all the potential methods called. Then you can >> open a workspace and run this script: >> >> | methods mb | >> methods := ((CompiledMethod>>#foo:bar:) messages collect: [ :selector | >> selector implementors ]) flattened. >> mb := MethodBrowser new. >> mb openWithSpec. >> mb methods: methods >> >> >> >>> or any way to see >>> all the send messages to other methods limited to scope of a method ? >>> >> >> all the send messages to other methods ? >> >> Well for that you'll need type inference to find out which variables are >> actually methods, and then see what messages are sent to those variables. >> But why would one want to do that ? >> >>> >>> Thanks, >>> Aria >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >> > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by aria2end

Yes Exactly. I want to see all the potential methods called from from this method which is the second case. but I receive error using that script. MessageNotUnderstood: ByteSymbol>>implementors -- View this message in context: http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by kilon alios

cant you also use the ast to find out how exactly Pharo which object and which method it executes ? On Thu, Aug 7, 2014 at 11:39 AM, kilon alios <kilon.alios(a)gmail.com> wrote: > Marcus has shown me previously ast with nodesDo: for example this code > show me the full ast for my class method blenderOpen of my class Ephestos. > > (Ephestos class compiledMethodAt: #blenderOpen ) ast nodesDo: [ :node| > node inspect] > > and it opens one inspector per node > > messages that are "method calls" are nodes of RBMessageNode class. I see a > instance variable "selector" which returns the name of the selector and an > instance variable "receiver" returns the name of the receiver. Instance > variable "parent" describes the container of the message . For example in > my case the only RBMessageNode is contained inside a variable assignment. > > So I think its a good start for finding "method calls" messages. > > > On Thu, Aug 7, 2014 at 11:18 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> > wrote: > >> >> >> >> 2014-08-07 5:11 GMT+02:00 aria2end <aria2end(a)gmail.com>: >> >> Hi, I know that I can see senders and implementers of a method but is >>> there >>> any way to see all methods that are used in a method ? >>> >> >> This is impossible. The method called for each message send can only been >> known at runtime, because it depends on the receiver class. The only thing >> you could see is the list of selectors (name of methods) called from this >> method. This is possible by sending #messages to the compiledMethod. >> >> Example: >> >> you have a method named #foo:bar: implemented in MyClass: >> MyClass>>foo: arg1 bar: arg2 >> ^ self baz: arg1 + arg2 >> >> You can open a workspace, and run: >> (MyClass >>#foo:bar:) messages >> >> which answers: >> a Set(#baz: #+) >> >> but you cannot see the methods called, because depending on the class of >> arg1, the method called for #+ may be any of these methods: >> AJMem>>#+ Collection>>#+ Color>>#+ DateAndTime>>#+ Duration>>#+ Float>>#+ >> FloatArray>>#+ Fraction>>#+ Integer>>#+ Interval>>#+ KMComposedModifier>>#+ >> KMKeyCombinationSequence>>#+ KMModifier>>#+ KMNoShortcut>>#+ >> LargeInteger>>#+ Number>>#+ Point>>#+ ROAbstractComponent>>#+ ROShape>>#+ >> ROShape class>>#+ ScaledDecimal>>#+ SmallInteger>>#+ String>>#+ >> Timespan>>#+ TraitComposition>>#+ TraitDescription>>#+ >> TraitTransformation>>#+ WordArray>>#+ TComposingDescription>>#+ >> >> Or perhaps you want to see all the potential methods called. Then you can >> open a workspace and run this script: >> >> | methods mb | >> methods := ((CompiledMethod>>#foo:bar:) messages collect: [ :selector | >> selector implementors ]) flattened. >> mb := MethodBrowser new. >> mb openWithSpec. >> mb methods: methods >> >> >> >>> or any way to see >>> all the send messages to other methods limited to scope of a method ? >>> >> >> all the send messages to other methods ? >> >> Well for that you'll need type inference to find out which variables are >> actually methods, and then see what messages are sent to those variables. >> But why would one want to do that ? >> >>> >>> Thanks, >>> Aria >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >> >

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by kilon alios

Marcus has shown me previously ast with nodesDo: for example this code show me the full ast for my class method blenderOpen of my class Ephestos. (Ephestos class compiledMethodAt: #blenderOpen ) ast nodesDo: [ :node| node inspect] and it opens one inspector per node messages that are "method calls" are nodes of RBMessageNode class. I see a instance variable "selector" which returns the name of the selector and an instance variable "receiver" returns the name of the receiver. Instance variable "parent" describes the container of the message . For example in my case the only RBMessageNode is contained inside a variable assignment. So I think its a good start for finding "method calls" messages. On Thu, Aug 7, 2014 at 11:18 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > > > 2014-08-07 5:11 GMT+02:00 aria2end <aria2end(a)gmail.com>: > > Hi, I know that I can see senders and implementers of a method but is there >> any way to see all methods that are used in a method ? >> > > This is impossible. The method called for each message send can only been > known at runtime, because it depends on the receiver class. The only thing > you could see is the list of selectors (name of methods) called from this > method. This is possible by sending #messages to the compiledMethod. > > Example: > > you have a method named #foo:bar: implemented in MyClass: > MyClass>>foo: arg1 bar: arg2 > ^ self baz: arg1 + arg2 > > You can open a workspace, and run: > (MyClass >>#foo:bar:) messages > > which answers: > a Set(#baz: #+) > > but you cannot see the methods called, because depending on the class of > arg1, the method called for #+ may be any of these methods: > AJMem>>#+ Collection>>#+ Color>>#+ DateAndTime>>#+ Duration>>#+ Float>>#+ > FloatArray>>#+ Fraction>>#+ Integer>>#+ Interval>>#+ KMComposedModifier>>#+ > KMKeyCombinationSequence>>#+ KMModifier>>#+ KMNoShortcut>>#+ > LargeInteger>>#+ Number>>#+ Point>>#+ ROAbstractComponent>>#+ ROShape>>#+ > ROShape class>>#+ ScaledDecimal>>#+ SmallInteger>>#+ String>>#+ > Timespan>>#+ TraitComposition>>#+ TraitDescription>>#+ > TraitTransformation>>#+ WordArray>>#+ TComposingDescription>>#+ > > Or perhaps you want to see all the potential methods called. Then you can > open a workspace and run this script: > > | methods mb | > methods := ((CompiledMethod>>#foo:bar:) messages collect: [ :selector | > selector implementors ]) flattened. > mb := MethodBrowser new. > mb openWithSpec. > mb methods: methods > > > >> or any way to see >> all the send messages to other methods limited to scope of a method ? >> > > all the send messages to other methods ? > > Well for that you'll need type inference to find out which variables are > actually methods, and then see what messages are sent to those variables. > But why would one want to do that ? > >> >> Thanks, >> Aria >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

Aug. 7, 2014

Re: [Pharo-users] Seeing all the methods that is used in a method

by ClÃ©ment Bera

2014-08-07 5:11 GMT+02:00 aria2end <aria2end(a)gmail.com>: > Hi, I know that I can see senders and implementers of a method but is there > any way to see all methods that are used in a method ? > This is impossible. The method called for each message send can only been known at runtime, because it depends on the receiver class. The only thing you could see is the list of selectors (name of methods) called from this method. This is possible by sending #messages to the compiledMethod. Example: you have a method named #foo:bar: implemented in MyClass: MyClass>>foo: arg1 bar: arg2 ^ self baz: arg1 + arg2 You can open a workspace, and run: (MyClass >>#foo:bar:) messages which answers: a Set(#baz: #+) but you cannot see the methods called, because depending on the class of arg1, the method called for #+ may be any of these methods: AJMem>>#+ Collection>>#+ Color>>#+ DateAndTime>>#+ Duration>>#+ Float>>#+ FloatArray>>#+ Fraction>>#+ Integer>>#+ Interval>>#+ KMComposedModifier>>#+ KMKeyCombinationSequence>>#+ KMModifier>>#+ KMNoShortcut>>#+ LargeInteger>>#+ Number>>#+ Point>>#+ ROAbstractComponent>>#+ ROShape>>#+ ROShape class>>#+ ScaledDecimal>>#+ SmallInteger>>#+ String>>#+ Timespan>>#+ TraitComposition>>#+ TraitDescription>>#+ TraitTransformation>>#+ WordArray>>#+ TComposingDescription>>#+ Or perhaps you want to see all the potential methods called. Then you can open a workspace and run this script: | methods mb | methods := ((CompiledMethod>>#foo:bar:) messages collect: [ :selector | selector implementors ]) flattened. mb := MethodBrowser new. mb openWithSpec. mb methods: methods > or any way to see > all the send messages to other methods limited to scope of a method ? > all the send messages to other methods ? Well for that you'll need type inference to find out which variables are actually methods, and then see what messages are sent to those variables. But why would one want to do that ? > > Thanks, > Aria > > > > > > -- > View this message in context: > http://forum.world.st/Seeing-all-the-methods-that-is-used-in-a-method-tp477… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014

Re: [Pharo-users] I need some explaination about arguements assignment

by ClÃ©ment Bera

2014-08-07 6:38 GMT+02:00 aria2end <aria2end(a)gmail.com>: > Hi james, > > Your post not only resolved the issue but also introduced me a new approach > which I was looking for it. > Thank you > > do you know the reason why assigning to a passed-in argument is illegal by > any chance ? > > This is illegal because then you may lose the original argument value and the debugger does not work well any more. Assigning to an argument should raise an error, but the new compiler does not raise it (it is a known bug). > > > -- > View this message in context: > http://forum.world.st/I-need-some-explaination-about-arguements-assignment-… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014

Re: [Pharo-users] I need some explaination about arguements assignment

by S Krish

See enclosed screen shot.. On Thu, Aug 7, 2014 at 11:59 AM, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > > ok something your post does bring up intrinsically not ok with Pharo, but > not threatening a bug, as in normal code practice: > > a) We should never assign values into the arguments.. > > On compiling .. > > As I see it, the Pharo compiler makes "aText" now a temp variable of the > block ( actually the while loop is not relevant .. ) > The argument "aNumb" actually takes on the value of the first argument > viz: of the passed aText.. > > It would be nicer if the compiler refuses to accept assignment to an > argument of the method.. > > As for suggestion that you liked, I would suggest simply run through Pharo > By Example first thoroughly... and then take up as much of test runs > through existing applications to understand some of the concepts of how to > code.. > > >

Aug. 7, 2014

Re: [Pharo-users] I need some explaination about arguements assignment

by S Krish

ok something your post does bring up intrinsically not ok with Pharo, but not threatening a bug, as in normal code practice: a) We should never assign values into the arguments.. On compiling .. As I see it, the Pharo compiler makes "aText" now a temp variable of the block ( actually the while loop is not relevant .. ) The argument "aNumb" actually takes on the value of the first argument viz: of the passed aText.. It would be nicer if the compiler refuses to accept assignment to an argument of the method.. As for suggestion that you liked, I would suggest simply run through Pharo By Example first thoroughly... and then take up as much of test runs through existing applications to understand some of the concepts of how to code.. On Thu, Aug 7, 2014 at 10:08 AM, aria2end <aria2end(a)gmail.com> wrote: > Hi james, > > Your post not only resolved the issue but also introduced me a new approach > which I was looking for it. > Thank you > > do you know the reason why assigning to a passed-in argument is illegal by > any chance ? > > > > -- > View this message in context: > http://forum.world.st/I-need-some-explaination-about-arguements-assignment-… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Aug. 7, 2014