November 2018 - Pharo-users

Re: [Pharo-users] ToManyRelationSlot variant with an ordered collection?

by Marcus Denker

> On 10 Nov 2018, at 22:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > The current implementation of ToManyRelationSlot is based on a RelationSet which holds the items in a Set. > > Is there an implementation that holds the items in an ordered collection? Not that I know, but it would be interesting to experiment with this! Marcus

Nov. 12, 2018

ToManyRelationSlot variant with an ordered collection?

by Tudor Girba

Hi, The current implementation of ToManyRelationSlot is based on a RelationSet which holds the items in a Set. Is there an implementation that holds the items in an ordered collection? Cheers, Doru -- www.feenk.com "Some battles are better lost than fought."

Nov. 10, 2018

Re: [Pharo-users] what must be instead of the ??

by Richard O'Keefe

We are talking to a beginner here. One of the important things for a beginner to understand is the idea of hiding stuff and thinking in terms of asking objects to do things for you. For example, in Java you historically did final int n = aString.length(); for (int i = 0; i < n; i++) { final char c = aString.charAt(i); ... } Here all the loop control is *outside* the string, and if you wanted to use some other data structure you would have to change the code. But in Smalltalk, you ask the *object* to manage the iteration. For collections in general, we have aCollection do: [:anElement | ... ] For sequences we also have aSequence withIndexDo: [:anElement :itsIndex | ...] where the sequence need not be a stored sequence and need not be efficiently indexable. (And indeed, in Java these days, Strings *aren't* efficiently indexable, thanks to using UTF-16 internally.) Using enumeration methods (a) makes your code easier to read (b) makes your code easier to write (as there is lots of fiddly detail you don't write at all, it's there once and for all in the class) (c) makes your code more adaptable (the object needs to support #withIndexDo: and that is *all* you demand of it). indexWhereBasementFirstReached: input "The input is a sequence in which the character ( means to go up a floor and the character ) means to go down a floor. Answer the index of the character where the floor below the initial floor is first reached. If that floor is not reached, e.g., if the input is empty, answer 0. This is the same convention as #indexOf:." |floor| floor := 0. input withIndexDo: [:char :index | char = $( ifTrue: [floor := floor + 1]. char = $) ifTrue: [floor := floor - 1]. floor = -1 ifTrue: [^index]]. ^0 For example, we could add the #withIndexDo: method to Stream, which already has #do: withIndexDo: elementAndIndexBlock "Iterate over the 'future values' remaining in this stream, passing each in turn to the block argument, together with an index starting at 1 for the first value passed to the block." |index| index := 0. self do: [:each | elementAndIndexBlock value: each value: (index := index + 1)]. Now the #indexWhereBasementFirstReached: method will work on input streams as well as strings, so it could, for example, handle a terabyte long sequence held in a file. On Sat, 10 Nov 2018 at 06:17, Roelof Wobben <r.wobben(a)home.nl> wrote: > hmm. > > When I try this on P7 > > |input stepChanges floor| > input := '((('. > floor := 0. > stepChanges := input collect: [ :c | > floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). > floor > ]. > > stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input > yo' ]. > > then I see this error message : Improper store to indexable object. > > Roelof > > > Op 9-11-2018 om 17:39 schreef Roelof Wobben: > > stepChanges := input collect: [ :c | > floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). > floor > ]. > > stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input > yo' ]. > > >

Nov. 10, 2018

Re: [Pharo-users] what must be instead of the ??

by Roelof Wobben

Given up for today I have this : calculateFloors | stepChanges floor| floor := 0. stepChanges := input asArray collect: [ :c | floor := floor+ (c = $( ifTrue: [ 1 ] ifFalse: [ -1 ]). ]. floors addFloor: floor. but now I see this error message : temp values not written or read. floors and input are instance variables where input is the input the user wants to use and floors is a Collection new. Roelof Op 9-11-2018 om 20:07 schreef Roelof Wobben: > hmm, got a idea > > I could use this part : > > |input floor stepChanges| > input := '))((((('. > floor := 0. > stepChanges := input asArray collect: [ :c | > floor := floor + (c = $( ifTrue: [ 1 ] ifFalse: [ -1 ]). > Â ]. > > > two times if the outcome would be a collection. > The challenge is 2 parts. > > 1) find out where santa stops. that would be the last number in the > collection.. > 2) find out when santa enters the basement. That could be the function > that is mentioned here. > > Time to experiment with this idea. > > Roelof > > > Op 9-11-2018 om 19:13 schreef Alistair Grant: >> Hi Peter, >> >> On Fri, 9 Nov 2018 at 19:00, Alistair Grant <akgrant0710(a)gmail.com> >> wrote: >>> Hi Peter, >>> >>> On Fri, 9 Nov 2018 at 18:51, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>>>> but how do I find now the answer do I have to do something likeÂ Â >>>>> puzzle1Â stepChanges detectIndex ? >>>> >>>> How do you mean? It would be the same >>>> >>>> santaFloorOnBasement >>>> Â Â Â Â "calculates which step take Santa to the basement" >>>> >>>> Â Â Â Â stepChanges := input collect: [ :c | >>>> floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). >>>> floor >>>> Â Â Â Â ]. >>>> >>>> Â Â Â Â stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ >>>> 'invalid input yo' ]. >>>> >>>>> then I see this error message : Improper store to indexable object. >>>> >>>> Because earlier you were comparing strings and not characters, I >>>> assumed your input was an array of strings like #('(' '(' '('). but >>>> you can fix that by changing `input collect:` -> `input asArray >>>> collect:` and `c = '('` -> `c = $(`. >>> Using '(' instead of $( is indeed an error, but it isn't the cause of >>> the Improper store error. >> I was too quick to respond here, I didn't look at the #asArray. Sorry! >> >> But still suggest Roelof looks at the debugger... >> >>> Roelof, I really suggest you trigger this error again, start the >>> debugger and then take a look in the call stack (I'm assuming you're >>> familiar with at least one other programming language, so should be >>> able to figure out the debugger). >> Cheers, >> Alistair >> >> > > >

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Roelof Wobben

hmm, got a idea I could use this part : |input floor stepChanges| input := '))((((('. floor := 0. stepChanges := input asArray collect: [ :c | floor := floor + (c = $( ifTrue: [ 1 ] ifFalse: [ -1 ]). Â ]. two times if the outcome would be a collection. The challenge is 2 parts. 1) find out where santa stops. that would be the last number in the collection.. 2) find out when santa enters the basement. That could be the function that is mentioned here. Time to experiment with this idea. Roelof Op 9-11-2018 om 19:13 schreef Alistair Grant: > Hi Peter, > > On Fri, 9 Nov 2018 at 19:00, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Peter, >> >> On Fri, 9 Nov 2018 at 18:51, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >>>> but how do I find now the answer do I have to do something like puzzle1 stepChanges detectIndex ? >>> >>> How do you mean? It would be the same >>> >>> santaFloorOnBasement >>> "calculates which step take Santa to the basement" >>> >>> stepChanges := input collect: [ :c | >>> floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). >>> floor >>> ]. >>> >>> stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input yo' ]. >>> >>>> then I see this error message : Improper store to indexable object. >>> >>> Because earlier you were comparing strings and not characters, I assumed your input was an array of strings like #('(' '(' '('). but you can fix that by changing `input collect:` -> `input asArray collect:` and `c = '('` -> `c = $(`. >> Using '(' instead of $( is indeed an error, but it isn't the cause of >> the Improper store error. > I was too quick to respond here, I didn't look at the #asArray. Sorry! > > But still suggest Roelof looks at the debugger... > >> Roelof, I really suggest you trigger this error again, start the >> debugger and then take a look in the call stack (I'm assuming you're >> familiar with at least one other programming language, so should be >> able to figure out the debugger). > Cheers, > Alistair > >

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Roelof Wobben

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Alistair Grant

Hi Peter, On Fri, 9 Nov 2018 at 19:00, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Peter, > > On Fri, 9 Nov 2018 at 18:51, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > >> > >> but how do I find now the answer do I have to do something like puzzle1 stepChanges detectIndex ? > > > > > > How do you mean? It would be the same > > > > santaFloorOnBasement > > "calculates which step take Santa to the basement" > > > > stepChanges := input collect: [ :c | > > floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). > > floor > > ]. > > > > stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input yo' ]. > > > >> then I see this error message : Improper store to indexable object. > > > > > > Because earlier you were comparing strings and not characters, I assumed your input was an array of strings like #('(' '(' '('). but you can fix that by changing `input collect:` -> `input asArray collect:` and `c = '('` -> `c = $(`. > > Using '(' instead of $( is indeed an error, but it isn't the cause of > the Improper store error. I was too quick to respond here, I didn't look at the #asArray. Sorry! But still suggest Roelof looks at the debugger... > Roelof, I really suggest you trigger this error again, start the > debugger and then take a look in the call stack (I'm assuming you're > familiar with at least one other programming language, so should be > able to figure out the debugger). Cheers, Alistair

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Alistair Grant

Hi Peter, On Fri, 9 Nov 2018 at 18:51, Peter Uhnak <i.uhnak(a)gmail.com> wrote: >> >> but how do I find now the answer do I have to do something like puzzle1 stepChanges detectIndex ? > > > How do you mean? It would be the same > > santaFloorOnBasement > "calculates which step take Santa to the basement" > > stepChanges := input collect: [ :c | > floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). > floor > ]. > > stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input yo' ]. > >> then I see this error message : Improper store to indexable object. > > > Because earlier you were comparing strings and not characters, I assumed your input was an array of strings like #('(' '(' '('). but you can fix that by changing `input collect:` -> `input asArray collect:` and `c = '('` -> `c = $(`. Using '(' instead of $( is indeed an error, but it isn't the cause of the Improper store error. Roelof, I really suggest you trigger this error again, start the debugger and then take a look in the call stack (I'm assuming you're familiar with at least one other programming language, so should be able to figure out the debugger). Cheers, Alistair

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Peter Uhnak

> > but how do I find now the answer do I have to do something like puzzle1 > stepChanges detectIndex ? How do you mean? It would be the same santaFloorOnBasement "calculates which step take Santa to the basement" stepChanges := input collect: [ :c | floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). floor ]. stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input yo' ]. then I see this error message : Improper store to indexable object. Because earlier you were comparing strings and not characters, I assumed your input was an array of strings like #('(' '(' '('). but you can fix that by changing `input collect:` -> `input asArray collect:` and `c = '('` -> `c = $(`. I have thought of something but I found it wierd that you do steps when you > have already the answer. That is indeed true, personally I would decide based on how often the method is called and how large the input is. Because this cumulative change makes it much easier to debug any issues... and usually I prefer debuggability over performance (unless it is an actual bottleneck). Peter On Fri, Nov 9, 2018 at 6:38 PM Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > It's bug in the collect: implementation used in String. I've opened > https://pharo.fogbugz.com/f/cases/22652/collect-over-Strings-is-broken > > On Fri, Nov 9, 2018 at 2:17 PM Roelof Wobben <r.wobben(a)home.nl> wrote: > >> hmm. >> >> When I try this on P7 >> >> |input stepChanges floor| >> input := '((('. >> floor := 0. >> stepChanges := input collect: [ :c | >> floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). >> floor >> ]. >> >> stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input >> yo' ]. >> >> then I see this error message : Improper store to indexable object. >> >> Roelof >> >> >> Op 9-11-2018 om 17:39 schreef Roelof Wobben: >> >> stepChanges := input collect: [ :c | >> floor := floor + (c = '(' ifTrue: [ 1 ] ifFalse: [ -1 ]). >> floor >> ]. >> >> stepChanges detectIndex: [ :each | each = -1 ] ifNone: [ 'invalid input >> yo' ]. >> >> >>

Nov. 9, 2018

Re: [Pharo-users] what must be instead of the ??

by Alistair Grant

On Fri, 9 Nov 2018 at 18:38, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > It's bug in the collect: implementation used in String. I've opened https://pharo.fogbugz.com/f/cases/22652/collect-over-Strings-is-broken Strings store characters, not integers, so change your example to: 'aa' collect: [ :a | $1 ] and you'll see that (I think) it is working as expected. You could do: 'aa' collect: [ :a | 1 ] as: Array. Roelof, revisit your example, taking the above in to account :-) HTH, Alistair

Nov. 9, 2018