- Pharo-users - lists.pharo.org

Re: [Pharo-users] why is asDictonary a class method

by Roelof Wobben

March 31, 2019

Re: [Pharo-users] why is asDictonary a class method

by Richard O'Keefe

Question 1. Should that be #asDictionary? Question 2. If not, what's a Dictonary? Question 3. I see you are using self-encapsulation, with a getter 'self robot' and a setter 'self robot: something'. Of course that means that outside code can freely smash your "robot" property, unless #robot: checks that its argument makes sense. Does it? Question 4. What kind of thing *is* "robot". Have you checked that 'Robot directionLooking: ...' returns an instance of Robot? If you accidentally omitted '^' it might return the Robot class itself. Question 5. Are you sure that 'self robot' returns what you think it does? Have you checked? Question 6. Does Robot have an #asDictionary method? Does Robot have an #asDictonary method? Question 7. Why is "aCollection" not used in this method? Question 8. Why are you using 'yourself'? Question 9. Why does the caller want a dictionary instead of a Robot? What should be in that dictionary? There are more questions but those will do to be going on with. If your #robot: method began like robot: aRobot (aRobot isKindOf: Robot) ifFalse: [aRobot error: 'not an instance of Robot']. you would have caught what I suspect is your problem. Check question 4. On Sun, 31 Mar 2019 at 07:19, Roelof Wobben <r.wobben(a)home.nl> wrote: > Hello, > > Im busy with a new challenge from exercism. > Where I have to keep track of a robot , where it facing and on that > coordinate the robot is. > > so I made this function what the test wanted > > createDirection: aString position: aCollection > self robot: (Robot directionLooking: aString) yourself. > ^ self robot asDictonary > > I can see that on the first part a new robot is made with the right data. > but the test wants the data back as a Dictonary > that is why I made the self robot asDictonary line > > but to my suprise the compiler wants it be a class method where I expect > it to be a instance method. > > Can someone explain to my why this is ? > > Roelof > > >

March 31, 2019

Re: [Pharo-users] How to generically find methods in class hierarchies? (Aka narrow spotter?)

by Ben Coman

On Sat, 30 Mar 2019 at 20:25, Tim Mackinnon <tim(a)testit.works> wrote: > You - know, this has made me realise that I donât understand the > difference between #messages and #implementors in Spotter? In my haste Iâve > always jumped on the latter (as its first in the spotter list) - and > implementors has much more methods. So thats a good tip. > > In realising this now, Iâm wondering how you easily jump down the sections > with the keyboard on OSX - help says cmd-shift-down but it appears to not > work (maybe a regression?). > Try... wrap #m but that is a bit insider knowledge and easy to miss. Perhaps showing this shortcut in the heading would help... "#Messages (#m) nnn/NNN" I took a poke at doing that, browsing senders of #spotterOrder: I found... CompiledMethod>>spotterForMessagesFor: aStep <spotterOrder: 12> aStep listProcessor title: 'Messages'; allCandidates: [ self messages asSortedCollection collect: [:each | GTSelector new name: each ] ]; filter: GTFilterSubstring But as a test changing the title to 'Messages x' is not reflected when I next open Spotter. Any clues where the "#Messages (#m) nnn/NNN" would be made? cheers -ben

March 31, 2019

Re: [Pharo-users] why is asDictonary a class method

by Dennis Schetinin

Didn't you forget to return (^) an instance from #directionLooking:? And why do you need to send #yourself? ÑÐ±, 30 Ð¼Ð°ÑÑÐ° 2019 Ð³. Ð² 21:19, Roelof Wobben <r.wobben(a)home.nl>: > Hello, > > Im busy with a new challenge from exercism. > Where I have to keep track of a robot , where it facing and on that > coordinate the robot is. > > so I made this function what the test wanted > > createDirection: aString position: aCollection > self robot: (Robot directionLooking: aString) yourself. > ^ self robot asDictonary > > I can see that on the first part a new robot is made with the right data. > but the test wants the data back as a Dictonary > that is why I made the self robot asDictonary line > > but to my suprise the compiler wants it be a class method where I expect > it to be a instance method. > > Can someone explain to my why this is ? > > Roelof > > > -- -- Best regards, Dennis Schetinin

March 30, 2019

why is asDictonary a class method

by Roelof Wobben

Hello, Im busy with a new challenge from exercism. Where I have to keep track of a robot , where it facing and on that coordinate the robot is. so I made this function what the test wanted createDirection: aString position: aCollection Â Â Â self robot: (Robot directionLooking: aString) yourself. Â Â Â ^ self robot asDictonary I can see that on the first part a new robot is made with the right data. but the test wants the data back as a Dictonary that is why I made the self robot asDictonary line but to my suprise the compiler wants it be a class method where I expect it to be a instance method. Can someone explain to my why this is ? Roelof

March 30, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Peter Kenny

Sven - Thanks for mentioning this - it's fascinating to see how it works. Even though it's only (!) 900+ selectors, it must have been a nightmare to construct - the layout of the source code suggests there was a lot of manual effort. Peter Sven Van Caekenberghe-2 wrote > Note that 'find by example' seems magical, but it isn't, really. The set > of discoverable selectors is limited. See MethodFinder > >> On 30 Mar 2019, at 13:26, Tim Mackinnon < > tim@ > > wrote: >> >> I actually keep meaning to try and plug this in to spotter so we get all >> of this stuff in one easy place (I think its pretty simple, just havenât >> had a chance to try it yet). >> >> Tim >> >>> On 30 Mar 2019, at 09:26, Peter Kenny < > peter@.co > > wrote: >>> >>> Ben >>> >>> Thanks for pointing this out - I was not aware of it. At first sight the >>> notation is completely opaque - I had no idea what the query in you post >>> meant until I read through the instructions in Finder. Now I have tried >>> it, >>> it looks quite handy. >>> >>> Minor nit-pick: The instructions say the components of a example are >>> separated by a period. This should read 'period plus space'; I put in >>> #(1 2 >>> 3 4).0.4 as an example and it said no such method. Granted the example > >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 30, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Sven Van Caekenberghe

Note that 'find by example' seems magical, but it isn't, really. The set of discoverable selectors is limited. See MethodFinder > On 30 Mar 2019, at 13:26, Tim Mackinnon <tim(a)testit.works> wrote: > > I actually keep meaning to try and plug this in to spotter so we get all of this stuff in one easy place (I think its pretty simple, just havenât had a chance to try it yet). > > Tim > >> On 30 Mar 2019, at 09:26, Peter Kenny <peter(a)pbkresearch.co.uk> wrote: >> >> Ben >> >> Thanks for pointing this out - I was not aware of it. At first sight the >> notation is completely opaque - I had no idea what the query in you post >> meant until I read through the instructions in Finder. Now I have tried it, >> it looks quite handy. >> >> Minor nit-pick: The instructions say the components of a example are >> separated by a period. This should read 'period plus space'; I put in #(1 2 >> 3 4).0.4 as an example and it said no such method. Granted the example >> quoted in the instructions has spaces, but a lazy so-and-so like me can be >> guaranteed to foul it up. >> >> Peter >> >> >> Ben Coman wrote >>> On Sat, 30 Mar 2019 at 01:09, Peter Kenny < >> >>> peter@.co >> >>> > wrote: >>> >>>> Tim >>>> >>>> Going back to your original question, the answer is there all the time >>>> but >>>> buried in the enormous method dictionaries of the Collection subclasses. >>> >>> >>> And we have Tools > Finder > Examples > #(10 20 30 40) . 5 . 10 >>> to help unbury such methods... >>> >>> >>> >>>> If >>>> you look at SequenceableCollection>>atWrap: you will see that it does >>>> exactly what you want. >>>> >>>> To get the item before the first, i.e. the zeroth: >>>> #(1 2 3 4) atWrap: 0 => 4 >>>> >>>> To get the item after the last: >>>> #(1 2 3 4) atWrap: 5 => 1 >>>> >>>> As seen here, the method is inherited by Array, so it should do all you >>>> want. >>>> >>>> HTH >>>> >>>> Peter >>>> >>>> >>> >>> --------------- >>> >>>> >>>> Marcus Denker-4 wrote >>>>>> On 29 Mar 2019, at 14:24, Ben Coman < >>>>>> I believe there have been some proposals to separate out the Process >>>>>> related LinkedList stuff, but I can't remember the exact arguments. >>>>> >>>>> Yes, we did thatâ¦ there is now ProcessList. >>>>> >>>>> We ran into that problem far too often âhey, LinkedList can be cleaned >>>> up >>>>> easily like this!â â> boom, everything broken. >>>>> >>>>> Now we have ProcessList where it matters if code is changed to >>>> introduce >>>> a >>>>> message send more and LinkedList where it does not. >>>> >>> >>> Cool !! >>> >>> cheers -ben >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

March 30, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Tim Mackinnon

I actually keep meaning to try and plug this in to spotter so we get all of this stuff in one easy place (I think its pretty simple, just havenât had a chance to try it yet). Tim > On 30 Mar 2019, at 09:26, Peter Kenny <peter(a)pbkresearch.co.uk> wrote: > > Ben > > Thanks for pointing this out - I was not aware of it. At first sight the > notation is completely opaque - I had no idea what the query in you post > meant until I read through the instructions in Finder. Now I have tried it, > it looks quite handy. > > Minor nit-pick: The instructions say the components of a example are > separated by a period. This should read 'period plus space'; I put in #(1 2 > 3 4).0.4 as an example and it said no such method. Granted the example > quoted in the instructions has spaces, but a lazy so-and-so like me can be > guaranteed to foul it up. > > Peter > > > Ben Coman wrote >> On Sat, 30 Mar 2019 at 01:09, Peter Kenny < > >> peter@.co > >> > wrote: >> >>> Tim >>> >>> Going back to your original question, the answer is there all the time >>> but >>> buried in the enormous method dictionaries of the Collection subclasses. >> >> >> And we have Tools > Finder > Examples > #(10 20 30 40) . 5 . 10 >> to help unbury such methods... >> >> >> >>> If >>> you look at SequenceableCollection>>atWrap: you will see that it does >>> exactly what you want. >>> >>> To get the item before the first, i.e. the zeroth: >>> #(1 2 3 4) atWrap: 0 => 4 >>> >>> To get the item after the last: >>> #(1 2 3 4) atWrap: 5 => 1 >>> >>> As seen here, the method is inherited by Array, so it should do all you >>> want. >>> >>> HTH >>> >>> Peter >>> >>> >> >> --------------- >> >>> >>> Marcus Denker-4 wrote >>>>> On 29 Mar 2019, at 14:24, Ben Coman < >>>>> I believe there have been some proposals to separate out the Process >>>>> related LinkedList stuff, but I can't remember the exact arguments. >>>> >>>> Yes, we did thatâ¦ there is now ProcessList. >>>> >>>> We ran into that problem far too often âhey, LinkedList can be cleaned >>> up >>>> easily like this!â â> boom, everything broken. >>>> >>>> Now we have ProcessList where it matters if code is changed to >>> introduce >>> a >>>> message send more and LinkedList where it does not. >>> >> >> Cool !! >> >> cheers -ben > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html>

March 30, 2019

Re: [Pharo-users] How to generically find methods in class hierarchies? (Aka narrow spotter?)

by Tim Mackinnon

You - know, this has made me realise that I donât understand the difference between #messages and #implementors in Spotter? In my haste Iâve always jumped on the latter (as its first in the spotter list) - and implementors has much more methods. So thats a good tip. In realising this now, Iâm wondering how you easily jump down the sections with the keyboard on OSX - help says cmd-shift-down but it appears to not work (maybe a regression?). Iâd also like to learn how to modify that list as Windows always comes first, and I rarely use spotter to switch windows, and prefer to type "Coll <enter>â and get a new browser on collection (and not a window that happens to mention collection). Anyway - learning lots from this, thanks. Tim > On 30 Mar 2019, at 09:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> On 30 Mar 2019, at 00:45, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> >> I had also used spotter - and to explain - if you type âwrapâ into spotter there are 400 methods that come up, and when you scroll down them, after about 100 the list starts to go blank (bug?). > > If I type 'wrap' I see this in Spotter: > > <Screenshot 2019-03-30 at 10.22.06.png> > So it is hit #2/#3 in Messages ... >

March 30, 2019

Re: [Pharo-users] Easiest way to wrap around the indexed value in a list (mod doesn't quite work)

by Peter Kenny

Ben Thanks for pointing this out - I was not aware of it. At first sight the notation is completely opaque - I had no idea what the query in you post meant until I read through the instructions in Finder. Now I have tried it, it looks quite handy. Minor nit-pick: The instructions say the components of a example are separated by a period. This should read 'period plus space'; I put in #(1 2 3 4).0.4 as an example and it said no such method. Granted the example quoted in the instructions has spaces, but a lazy so-and-so like me can be guaranteed to foul it up. Peter Ben Coman wrote > On Sat, 30 Mar 2019 at 01:09, Peter Kenny < > peter@.co > > wrote: > >> Tim >> >> Going back to your original question, the answer is there all the time >> but >> buried in the enormous method dictionaries of the Collection subclasses. > > > And we have Tools > Finder > Examples > #(10 20 30 40) . 5 . 10 > to help unbury such methods... > > > >> If >> you look at SequenceableCollection>>atWrap: you will see that it does >> exactly what you want. >> >> To get the item before the first, i.e. the zeroth: >> #(1 2 3 4) atWrap: 0 => 4 >> >> To get the item after the last: >> #(1 2 3 4) atWrap: 5 => 1 >> >> As seen here, the method is inherited by Array, so it should do all you >> want. >> >> HTH >> >> Peter >> >> > > --------------- > >> >> Marcus Denker-4 wrote >> >> On 29 Mar 2019, at 14:24, Ben Coman < >> >> I believe there have been some proposals to separate out the Process >> >> related LinkedList stuff, but I can't remember the exact arguments. >> > >> > Yes, we did thatâ¦ there is now ProcessList. >> > >> > We ran into that problem far too often âhey, LinkedList can be cleaned >> up >> > easily like this!â â> boom, everything broken. >> > >> > Now we have ProcessList where it matters if code is changed to >> introduce >> a >> > message send more and LinkedList where it does not. >> > > Cool !! > > cheers -ben -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 30, 2019