December 2019 - Pharo-users

[ANN] TechTalk TODAY âWorking with Spec2 and GTK" BUT TIME CHANGE TO 16h France
by Esteban Lorenzano Dec. 19, 2019

Dec. 19, 2019

Hi, I will give a techtalk today around the work with Spec2 and GTK. But because of personal reasons, I cannot give the talk 17-18h EU, instead, it will be one our earlier. So, this is the appointment: Pharo TechTalk 19 Dec 2019 4:00 PM - 5:00 PM (UTC+01:00) A regular chat about Pharo. Happens on Discord. The Tech talks are open to both members and non-members! Topic: âWorking with Spec2 and GTKâ Here is the event link: https://association.pharo.org/event-3419547 And here is the place where the transmission will be made: https://www.youtube.com/c/EstebanLorenzano/live Iâm sorry for the mess but fatherhood has this issues ;) See you there! Esteban

1 0

Question on MetaLink: access to the calling MessageNode from a MethodNode
by Mehrdad Abdi Dec. 18, 2019

Dec. 18, 2019

Hello For a specific method, I need to log some information when the method is called, like the state of the receiver, values of arguments, where the method is called, ... . Using following MetaLink, Iâm able to capture the receiver and arguments and context. link := MetaLink new metaObject: self; selector: #linkBeforeMethodArguments:receiver:selector:context:; control: #before; level: 0; arguments: #( arguments receiver selector context ). aMethod := MyClass methodNamed: #myMethodArg1:arg2. aMethod ast link: link For capturing the information related to where this method is called, It's possible to extract it from Context, but itâs a dirty way. Is there any way to access the MessageNode which called this MethodNode? Best regards, Mehrdad

2 1

Re: [pharo-project/pharo] Proposed improvement : performance of #atRandom: in class Bag (#5392)
by Benoit St-Jean Dec. 18, 2019

Dec. 18, 2019

While I'm at it, another improvement would be to buffer #newFrom: by reading large chunks of the argument <aCollection> via a ReadStream, adding the objects read to a <Bag> buffer and inserting into the receiver via #add:withOccurrences:.Â That way, if you read say 1000 object (of which lots are similar), you don't have to "add" 1000 items, you could reduce the number of adds by reducing the duplicates with this buffer bag.Â Wouldn't make much of a difference in the worst case scenario but one can assume that since you're using a bag, you normally expect a lot of dups!Â So we could gain a lot that way.Â Anyway, that's what I'm seeing with my experiments (millions of objects) and I'm still contemplating that improvement with more & more tests (such as adjusting the buffer size).Â So far, this is really promising! On 2019-12-18 06:32, Sven Van Caekenberghe wrote: > > OK, now I see. I was thrown off by the weird formatting ;-) > > The final expression is not needed, since you started with an emptyCheck. > > Reformatted then: > > |Bag>>#atRandom: aGenerator "Answer a random element of the receiver. > Uses aGenerator which should be kept by the user in a variable and > used every time. Use this instead of #atRandom for better uniformity > of random numbers because only you use the generator. Causes an error > if self has no elements." | rand index | self emptyCheck. rand := > aGenerator nextInt: self size. index := 0. self doWithOccurrences: [ > :key :count | index := index + count. rand <= index ifTrue: [ ^ key ] ] | > > Still, we need a PR as well. And maybe a specific test unless this is > already covered by other tests. > > â > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/pharo-project/pharo/issues/5392?email_source=notificatio…>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AEFVQ7ZNNUWBQZF7KKUDEBDQZ…>. > -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth GitHub: bstjean Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

1 0

Proposed improvement : performance of #atRandom: in class Bag
by Benoit St-Jean Dec. 18, 2019

Dec. 18, 2019

For those interested, I proposed a fix to *drastically* improve the performance of Bag>>#atRandom: ! See https://github.com/pharo-project/pharo/issues/5392 -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth GitHub: bstjean Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

1 0

Localization of Months and Day names
by Esteban Maringolo Dec. 18, 2019

Dec. 18, 2019

What is the "official way" (if any) to localize the printing of Date Month and Day names? I saw there is a Locale class, but neither the primLongDateFormat and primShortDateFormat have any senders, so if they're used, it's not through message sends. Regards! Esteban A. Maringolo

2 1

TaskIt
by Santiago Bragagnolo Dec. 17, 2019

Dec. 17, 2019

Hi everybody! We are starting to discuss with norbert about letting taskit to leave my incubator (my github account to go elsewhere). I have being thinking about it since long time, since i would like it to allow taskit to evolve into more than just my needs and wishes. The sidequestion i am bringing today it may seem (or even be) almost scholastic at this point, but i think it should have some space. The question is if to move it to pharo-contributions, or if to create a new pharo-processing. During the ESUG i came up with the idea/feeling/etc that it would be nice to have a group of people interested into processing (as hobby, duty, etc) for being able to push further this project and what-ever-other related project. During the conference i addressed norbert, tomohiro, mariano, matteo, guille, pablo, noury, (people for whom processing directly or indirectly is a primary concern) and i think there is even more people interested in this kind of general problematic, for what i sensed specially during my esug presentation. I think that to build a kind of team or group for discussing and working on this subject is a step in a direction that search to solve many modern daily problems that pushes us out of larger models of business and interaction (cloud and derivatives). Having this points in mind i think that the choice of this new github project could be a good point to start a to work on this goal (as a first place of gathering). Still, i would like to hear other's opinion, in order to be able to deal with this maybe before new year :). Thanks for your time and reading :) Santiago

5 5

Re: [Pharo-users] how can I this refractor this so its more smalltalk
by Ben Coman Dec. 17, 2019

Dec. 17, 2019

Apart from using streams, part of making code less ugly is splitting it up its separate aaspects. One way it to to do as little as possible within your loop. See how Todd only does one thing within his loop. Apart from looking nicer, doing so improves how you "think" about the problem. cheers -ben On Tue, 17 Dec 2019 at 23:00, Roelof Wobben via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hello, > > My solution to day2 part1 is right this : > > processData: instructions > | opcode index firstNumber secondNumber placeToPut firstNumberIndex > secondNumberIndex | > index := 1. > opcode := instructions at: index. > [ opcode ~= 99 ] > whileTrue: [ firstNumberIndex := instructions at: index + 1. > secondNumberIndex := instructions at: index + 2. > firstNumber := instructions at: firstNumberIndex + 1. > secondNumber := instructions at: secondNumberIndex + 1. > placeToPut := (instructions at: index + 3) + 1. > opcode == 1 > ifTrue: [ instructions at: placeToPut put: firstNumber > + secondNumber ]. > opcode == 2 > ifTrue: [ instructions at: placeToPut put: firstNumber > * secondNumber ]. > index := index + 4. > opcode := instructions at: index ]. > ^ instructions at: 1 > > so its ugly code > > is there a way I can this more the smalltalk way by using streams or > something else. > if so, is there someone who can tell me or can let me see how to make > this cleaner code > > Roelof > > >

1 0

Re: [Pharo-users] how can I this refractor this so its more smalltalk
by Todd Blanchard Dec. 17, 2019

Dec. 17, 2019

Well my main run method looks like this: run | op | ram := self input. in := ReadStream on: ram. [ (op := in next) = 99 ] whileFalse: [ self processOpcode: op ]. ^self at: 0. ram is the array of integers. in is a ReadStream on them which lets me process them in order. They are both instance variables. self input provides a clean copy of the program memory (the integer array). I just used an array literal. No file IO. The main dispatch method is processOpcode: op op = 1 ifTrue: [ ^self processAdd ]. op = 2 ifTrue: [ ^self processMultiply ]. and for illustration processAdd | a b c | a := self at: in next. b := self at: in next. self at: in next put: a+b There are custom versions of at: and at:put: that compensate for zero based vs one based array indexing. at: idx ^ram at: idx + 1 I hope this helps you out. > On Dec 17, 2019, at 6:59 AM, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Roelof Wobben <r.wobben(a)home.nl> > Subject: how can I this refractor this so its more smalltalk > Date: December 17, 2019 at 6:59:28 AM PST > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hello, > > My solution to day2 part1 is right this : > > processData: instructions > | opcode index firstNumber secondNumber placeToPut firstNumberIndex secondNumberIndex | > index := 1. > opcode := instructions at: index. > [ opcode ~= 99 ] > whileTrue: [ firstNumberIndex := instructions at: index + 1. > secondNumberIndex := instructions at: index + 2. > firstNumber := instructions at: firstNumberIndex + 1. > secondNumber := instructions at: secondNumberIndex + 1. > placeToPut := (instructions at: index + 3) + 1. > opcode == 1 > ifTrue: [ instructions at: placeToPut put: firstNumber + secondNumber ]. > opcode == 2 > ifTrue: [ instructions at: placeToPut put: firstNumber * secondNumber ]. > index := index + 4. > opcode := instructions at: index ]. > ^ instructions at: 1 > > so its ugly code > > is there a way I can this more the smalltalk way by using streams or something else. > if so, is there someone who can tell me or can let me see how to make this cleaner code > > Roelof > > > >

1 0

Re: [Pharo-users] how can I this refractor this so its more smalltalk
by Kasper Osterbye Dec. 17, 2019

Dec. 17, 2019

Hi Roelof I saw your posts earlier, and will try to take a look. I am not into the advent of code myself, but love a good puzzle. Would it be possible to provide a link to the puzzle you are trying to solve?

2 1

how can I this refractor this so its more smalltalk
by Roelof Wobben Dec. 17, 2019

Dec. 17, 2019

Hello, My solution to day2 part1 is right this : processData: instructions Â Â Â | opcode index firstNumber secondNumber placeToPut firstNumberIndex secondNumberIndex | Â Â Â index := 1. Â Â Â opcode := instructions at: index. Â Â Â [ opcode ~= 99 ] Â Â Â Â Â Â whileTrue: [ firstNumberIndex := instructions at: index + 1. Â Â Â Â Â Â Â Â Â secondNumberIndex := instructions at: index + 2. Â Â Â Â Â Â Â Â Â firstNumber := instructions at: firstNumberIndex + 1. Â Â Â Â Â Â Â Â Â secondNumber := instructions at: secondNumberIndex + 1. Â Â Â Â Â Â Â Â Â placeToPut := (instructions at: index + 3) + 1. Â Â Â Â Â Â Â Â Â opcode == 1 Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ instructions at: placeToPut put: firstNumber + secondNumber ]. Â Â Â Â Â Â Â Â Â opcode == 2 Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ instructions at: placeToPut put: firstNumber * secondNumber ]. Â Â Â Â Â Â Â Â Â index := index + 4. Â Â Â Â Â Â Â Â Â opcode := instructions at: index ]. Â Â Â ^ instructions at: 1 so its ugly code is there a wayÂ I can this more the smalltalk way by using streams or something else. if so, is there someone who can tell me or can let me see how to make this cleaner code Roelof

1 0