- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bag enhancements

by StÃ©phane Ducasse

On Aug 12, 2013, at 1:49 AM, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > Why not #doWithOccurrences: ?? > > Eg: > bag doWithOccurrences: [:element :count | "do something"] I did not see it in fact. it was probably not in the right place. > I dont'like the keysAndValuesDo: idea, is just an implementation detail. I agree (kind of) but this is polymorphic with hashtable so this is also nice. In fact I was not thinking about implementation when I wrote it. > > > On Sun, Aug 11, 2013 at 4:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > I was surprised to see the API of bag for iteration. > > I propose to add > > keysAndValuesDo: aBlock > "Iterate over the receiver and apply a two argument block on the element and its occurrences." > > contents associationsDo: [:assoc | aBlock value: assoc key value: assoc value ] > > and > > elementsAndOccurrencesDo: aTwoArgBlock > "Iterate over the receiver and apply a two argument block on the element and its occurrences." > > contents associationsDo: [:assoc | aTwoArgBlock value: assoc key value: assoc value ] > > Once we agree I will add a bug entry. > > Stef >

Aug. 12, 2013

Re: [Pharo-dev] bug with new inspector?

by ClÃ©ment Bera

yeah it tries to do 'bag at: 1' which fails. How would look like a nice bag inspector ? 2013/8/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > (Bag new add: 3 ; add: 3 ; add: 3 ; add: 2 ;yourself) inspect > > we got an error when trying to see the second element. > > > Stef > >

Aug. 12, 2013

Re: [Pharo-dev] Understanding Versionner repository selection

by HernÃ¡n Morales Durand

El 11/08/2013 4:00, StÃ©phane Ducasse escribiÃ³: > > On Aug 11, 2013, at 6:04 AM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com <mailto:hernan.morales@gmail.com>> wrote: > >> El 10/08/2013 14:55, HernÃ¡n Morales Durand escribiÃ³: >>> Hi folks, >>> I have a *very* simple package with no dependencies whatsoever. Now I'm >>> trying to understand Versionner, these are the steps: >>> >>> 1. I set the ConfigurationOf name >>> 2. I choose I don't want to use squeaksource.com >>> <http://squeaksource.com> >>> <http://squeaksource.com>, ok >>> 3. Select a repository... >>> >>> Now that is not clear for me. Which repository are you talking about? >>> the repository where I store MY code, or the repository where I would >>> like to publish the configuration so is displayed in the Configuration >>> Browser (like the MetaRepoForPharo)? >>> >> >> Ok, I choose the MetaRepoForPharo. The ConfigurationOf class is >> generated with its methods. I consider myself this package as stable, >> but there is no generated method for #'stable'. Do I need to create it >> by hand and then Commit to repository? > > normally not but I do not know the status of Versioner and christophe is > on vacation. > Thanks Stef. I get it now, it is just a matter of right click the in the right pane in Versionner, the #developement item, and then select the item "release dev" from the popup menu. Pretty easy. Now I will take a loot to SnapshotCello because I don't get what's the difference eith Versionner. >> >> This is another doubt. Where I should add meta information about my >> package? I just want to put a little description of what it does. > > > Hi all, > > I wish I could release a first beta of Versionner before my holidays but > I'am a bit short. > Nevertheless, you will find an archive on this page > http://chercheurs.lille.inria.fr/~demarey/Tech/Versionner containing the > current status of Versionner. > If you want, you can play a bit with it and give me feedback. > There are a lot of missing features but tit will come time after time. > > From now you can create a new config, release a dev version, update > dependencies. > > See you in 3 weeks, > Christophe.

Aug. 12, 2013

Re: [Pharo-dev] Bag enhancements

by Gabriel Cotelli

Why not #doWithOccurrences: ?? Eg: bag doWithOccurrences: [:element :count | "do something"] I dont'like the keysAndValuesDo: idea, is just an implementation detail. On Sun, Aug 11, 2013 at 4:52 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > I was surprised to see the API of bag for iteration. > > I propose to add > > keysAndValuesDo: aBlock > "Iterate over the receiver and apply a two argument block on the > element and its occurrences." > > contents associationsDo: [:assoc | aBlock value: assoc key value: > assoc value ] > > and > > elementsAndOccurrencesDo: aTwoArgBlock > "Iterate over the receiver and apply a two argument block on the > element and its occurrences." > > contents associationsDo: [:assoc | aTwoArgBlock value: assoc key > value: assoc value ] > > Once we agree I will add a bug entry. > > Stef >

Aug. 11, 2013

Re: [Pharo-dev] Fix in Athens-Cairo

by Alexandre Bergel

Yes, you're right. The Morphic version of drawing arc does not complain, however it did with Athens. Thanks for fixing this Alexandre On Aug 7, 2013, at 9:00 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Just to make it clear: > > when you get zero-divide error, where you think the bug is , in #/ method, > or maybe in code which passed zero as divisor? > > by analogy, when you want to draw an arc with zero length, which makes > it non-arc, > where you think the bug is, in code which implements drawing an arc or > in code which provides wrong input? > > because this change actually hiding the mistakes, so instead of > getting error and fixing it, > user now will have hard times figuring out, why it not draws things as > intended and where his mistake is. > > -- > Best regards, > Igor Stasenko. -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 11, 2013

Bag enhancements

by StÃ©phane Ducasse

Hi guys I was surprised to see the API of bag for iteration. I propose to add keysAndValuesDo: aBlock "Iterate over the receiver and apply a two argument block on the element and its occurrences." contents associationsDo: [:assoc | aBlock value: assoc key value: assoc value ] and elementsAndOccurrencesDo: aTwoArgBlock "Iterate over the receiver and apply a two argument block on the element and its occurrences." contents associationsDo: [:assoc | aTwoArgBlock value: assoc key value: assoc value ] Once we agree I will add a bug entry. Stef

Aug. 11, 2013

bug with new inspector?

by StÃ©phane Ducasse

(Bag new add: 3 ; add: 3 ; add: 3 ; add: 2 ;yourself) inspect we got an error when trying to see the second element. Stef

Aug. 11, 2013

Re: [Pharo-dev] adding temporary adds them outside the temp declaration?

by StÃ©phane Ducasse

Thanks clement. Stef On Aug 11, 2013, at 8:26 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > This is in Pharo 3, isn't it ? > > There are currently bugs with Opal's exception handing in Pharo 3.0. It was fixed then some other changes broke it again. So yeah it is known. You might have bug with: > OCShadowVariableWarning. > OCUndeclaredVariableWarning. > OCUninitializedVariableWarning. > OCUnusedVariableWarning. > OCUnknownSelectorWarning. > > > 2013/8/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > Is it a know bug? > > | selector superClasses | > selector := aMethodDefinition selector. > superClasses := aMethodDefinition realClass allSuperclasses. > result := OrderedCollection new. > (superClasses select: [ :eachClass | eachClass hasProtocolFor: selector]) > do: [ :eachClass | (eachClass includesSelector: selector) > ifTrue: [ result add: (self whichCategoryIncludesSelector: selector)]]. > ^ result asBag > > adds result > > result | selector superClasses | > selector := aMethodDefinition selector. > superClasses := aMethodDefinition realClass allSuperclasses. > result := OrderedCollection new. > (superClasses select: [ :eachClass | eachClass hasProtocolFor: selector]) > do: [ :eachClass | (eachClass includesSelector: selector) > ifTrue: [ result add: (self whichCategoryIncludesSelector: selector)]]. > ^ result asBag > > stef >

Aug. 11, 2013

Re: [Pharo-dev] adding temporary adds them outside the temp declaration?

by ClÃ©ment Bera

This is in Pharo 3, isn't it ? There are currently bugs with Opal's exception handing in Pharo 3.0. It was fixed then some other changes broke it again. So yeah it is known. You might have bug with: OCShadowVariableWarning. OCUndeclaredVariableWarning. OCUninitializedVariableWarning. OCUnusedVariableWarning. OCUnknownSelectorWarning. 2013/8/11 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Hi guys > > Is it a know bug? > > | selector superClasses | > selector := aMethodDefinition selector. > superClasses := aMethodDefinition realClass allSuperclasses. > result := OrderedCollection new. > (superClasses select: [ :eachClass | eachClass hasProtocolFor: > selector]) > do: [ :eachClass | (eachClass includesSelector: selector) > ifTrue: [ > result add: (self whichCategoryIncludesSelector: selector)]]. > ^ result asBag > > adds result > > result | selector superClasses | > selector := aMethodDefinition selector. > superClasses := aMethodDefinition realClass allSuperclasses. > result := OrderedCollection new. > (superClasses select: [ :eachClass | eachClass hasProtocolFor: > selector]) > do: [ :eachClass | (eachClass includesSelector: selector) > ifTrue: [ > result add: (self whichCategoryIncludesSelector: selector)]]. > ^ result asBag > > stef >

Aug. 11, 2013

adding temporary adds them outside the temp declaration?

by StÃ©phane Ducasse

Hi guys Is it a know bug? | selector superClasses | selector := aMethodDefinition selector. superClasses := aMethodDefinition realClass allSuperclasses. result := OrderedCollection new. (superClasses select: [ :eachClass | eachClass hasProtocolFor: selector]) do: [ :eachClass | (eachClass includesSelector: selector) ifTrue: [ result add: (self whichCategoryIncludesSelector: selector)]]. ^ result asBag adds result result | selector superClasses | selector := aMethodDefinition selector. superClasses := aMethodDefinition realClass allSuperclasses. result := OrderedCollection new. (superClasses select: [ :eachClass | eachClass hasProtocolFor: selector]) do: [ :eachClass | (eachClass includesSelector: selector) ifTrue: [ result add: (self whichCategoryIncludesSelector: selector)]]. ^ result asBag stef

Aug. 11, 2013