October 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12198

by StÃ©phane Ducasse

12198 ----- initialize LongTestCase correctly

Oct. 19, 2010

[Pharo-project] [update 1.2] #12197

by StÃ©phane Ducasse

12197 ----- - Issue 3127: Missing Close in About Dialog. Thanks Alain Plantec. - Issue 3125: SharedQueue/Monitor cleans. Thanks levente. :)

Oct. 19, 2010

Re: [Pharo-project] Little change for Objects As Methods

by Mariano Martinez Peck

On Tue, Oct 19, 2010 at 1:25 PM, Fernando olivero <fernando.olivero(a)usi.ch>wrote: > Just by curiosity, why does MethodDictionary>>at:put: has to send > #flushCache at all? > I am not sure, but I guess that cleaning. The method comment of CompiledMethod >> flushChache says: "Tell the interpreter to remove all references to this method from its method lookup cache, if it has one. This primitive must be called whenever a method is defined or removed" So...when you do a aClass methodDict at: #xxx put: aNewCompiledMethod nobody else "would" (Sometimes I think there are MCMethodDefinition instances pointing to methods that were even replaced by another ones) point to the original compiled method, at least no here. Thus....the vm cleans the cache for the method lookup. cheers mariano > > Fernando > > On Oct 19, 2010, at 1:14 PM, StÃ©phane Ducasse wrote: > > > Hi mariano > > > > I do not really like your solution. Implementing flushCache is not that > bad in your class. It is not a bad compromise. > > May be it should be better documented. > > > > Stef > > > > > >> When you are using Objects as methods, MethodWrappers, or whatever with > run:with:in, you have to implement not only that method, but also > flushCache doing nothing because it is used in: > >> > >> MethodDictionary >> at: put: > >> > >> at: key put: value > >> "Set the value at key to be value." > >> | index | > >> index := self findElementOrNil: key. > >> (self basicAt: index) == nil > >> ifTrue: > >> [tally := tally + 1. > >> self basicAt: index put: key] > >> ifFalse: > >> [(array at: index) flushCache]. > >> array at: index put: value. > >> self fullCheck. > >> ^ value > >> > >> > >> Ok, I can implement that in my classes, and in MethodWrappers, but I > think it would be nicer and cleanly if you only have to implement > run:with:in: since flushChache doesn't make sense for normal objects. > >> > >> So, I would like to change that code to > >> > >> at: key put: value > >> "Set the value at key to be value." > >> | index | > >> index := self findElementOrNil: key. > >> (self basicAt: index) == nil > >> ifTrue: > >> [tally := tally + 1. > >> self basicAt: index put: key] > >> ifFalse: > >> [(array at: index) isCompiledMethod ifTrue: [flushCache]]. > >> array at: index put: value. > >> self fullCheck. > >> ^ value > >> > >> > >> Yes, yes, I know the if is ugly, but it gives us a cleaner way to define > objects as methods. > >> The other option is to implement flushCache in Object doing nothing but > I like it less than this. > >> > >> opinions? > >> > >> thanks > >> > >> mariano > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 19, 2010

[Pharo-project] Fwd: [squeak-dev] SqueakSource are down

by StÃ©phane Ducasse

> > > > > On Oct 19, 2010, at 12:50 AM, Igor Stasenko wrote: > >> Hello, >> >> :( >> >> Guys, are there a reason , why we can't address this problem once and for all? > > time and money - ESUG is planning to support a rewrite of squeaksource. > I imagine. > INRIA told me that they will set up and maintain a webdav server that we could use for squeak and pharo. > Now we will not have the nice features of squeaksource. > I'm just waiting for it. > > Stef > > >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > > >

Oct. 19, 2010

Re: [Pharo-project] [squeak-dev] SharedQueue does scale (was: Re: SharedQueue doesn't scale)

by StÃ©phane Ducasse

On Oct 18, 2010, at 10:03 PM, Levente Uzonyi wrote: > On Mon, 18 Oct 2010, StÃ©phane Ducasse wrote: > >>> >>> This benchmark is the real concurrent stress test. 100 processes are adding 10,000 elements to the queue while another 100 are reading from it. It clearly shows that Igor's queues are an order of magnitude faster. Also 200 concurrent processes cause much less slowdown compared to the sequential tests for them. >>> >>> So, even though SharedQueue is now faster than SharedQueue2, both will have to go IMHO. :) >> >> Hi Levente >> >> Naively why? > > Did you see the benchmarks? > >> and replace by what? > > By Igor's new collections. Though the name should be kept for compatibility reasons. Ok I was confused... too many emails and threads. So yes! Stef

Oct. 19, 2010

Re: [Pharo-project] Little change for Objects As Methods

by Fernando olivero

Just by curiosity, why does MethodDictionary>>at:put: has to send #flushCache at all? Fernando On Oct 19, 2010, at 1:14 PM, StÃ©phane Ducasse wrote: > Hi mariano > > I do not really like your solution. Implementing flushCache is not that bad in your class. It is not a bad compromise. > May be it should be better documented. > > Stef > > >> When you are using Objects as methods, MethodWrappers, or whatever with run:with:in, you have to implement not only that method, but also flushCache doing nothing because it is used in: >> >> MethodDictionary >> at: put: >> >> at: key put: value >> "Set the value at key to be value." >> | index | >> index := self findElementOrNil: key. >> (self basicAt: index) == nil >> ifTrue: >> [tally := tally + 1. >> self basicAt: index put: key] >> ifFalse: >> [(array at: index) flushCache]. >> array at: index put: value. >> self fullCheck. >> ^ value >> >> >> Ok, I can implement that in my classes, and in MethodWrappers, but I think it would be nicer and cleanly if you only have to implement run:with:in: since flushChache doesn't make sense for normal objects. >> >> So, I would like to change that code to >> >> at: key put: value >> "Set the value at key to be value." >> | index | >> index := self findElementOrNil: key. >> (self basicAt: index) == nil >> ifTrue: >> [tally := tally + 1. >> self basicAt: index put: key] >> ifFalse: >> [(array at: index) isCompiledMethod ifTrue: [flushCache]]. >> array at: index put: value. >> self fullCheck. >> ^ value >> >> >> Yes, yes, I know the if is ugly, but it gives us a cleaner way to define objects as methods. >> The other option is to implement flushCache in Object doing nothing but I like it less than this. >> >> opinions? >> >> thanks >> >> mariano >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2010

Re: [Pharo-project] Speeding up Pharo 1.1

by StÃ©phane Ducasse

Thanks I added that to our agenda! December and january will be busy. We will have fun! Stef On Oct 19, 2010, at 9:24 AM, Henrik Sperre Johansen wrote: > On 19.10.2010 09:17, StÃ©phane Ducasse wrote: >> How can we make progress on this issue? >> >> Stef > As far as I can tell (again, I haven't actually experienced this slowdown), any of: > - Port Levente's WeakKeyDictionary, which is much faster. > - Wait for new VM's supporting Igors finalization scheme, which should be much faster (haven't tested it personally) > - Rewrite the MC package caching to not use weak collections/ be smarter about what it keeps. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2010

Re: [Pharo-project] Stack should be reimplemented with Array

by StÃ©phane Ducasse

On Oct 19, 2010, at 1:23 AM, Igor Stasenko wrote: > On 19 October 2010 00:25, Levente Uzonyi <leves(a)elte.hu> wrote: >> On Mon, 18 Oct 2010, Igor Stasenko wrote: >> >>> Stephane, i could say more: >>> - i don't like how LinkedList implemented. >>> >>> I don't see why it should mimic things like #at: #at:put: at all.. >> >> It's not mimicing those methods. A list usually support things like this, >> but the user should know the consequences. >> > > The consequences of such approach is much more far-reaching: leads to > bad design practices, crappy application performance, > and then tons of bugs and workarounds. > >>> IMO this protocol should be pruned from it, to not provoke uses which >>> completely do not fit for given data structure. >> >> I'm not sure if it's okay to remove features, because users lacking really >> basic CS knowledge may use them the wrong way. >> > > Imo, we should prohibit this from the beginning. Standard, core > classes should not contain an API, which could lead to > careless, abusive programming techniques. Yes and we should have comments comments comments and comments. > IMO, a kernel APIs should serve not only as an implementation of basic > system funcionality, it also must serve as guide, > how to best use these facilities, so people will learn what is the > right way to use it. > > We should teach users to use right tools for things they need. > > >>> >>> Removing/inserting into the middle of list is quite ineffective >>> operation (O(n)), >> >> As long as you don't give away the link objects, it's O(n), otherwise it can >> be O(1). > > giving away link objects... oh, that's the worst thing, which could > possibly happen :) > >> >>> while inserting at the begginning/end of list is O(1). >>> >>> Lists are sequenceable.. but sequenceable ~~ indexable. Period. >> >> Sequenceable is indexable, but good performance is not guaranteed. >> > Unless you representing an infinite collection(s). > Streams are good example of sequenceable, however non-indexable containers. > > >> >> Levente >> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2010

Re: [Pharo-project] Stack should be reimplemented with Array

by StÃ©phane Ducasse

one point at a time :) I'm talking about stack :) On Oct 18, 2010, at 10:49 PM, Igor Stasenko wrote: > Stephane, i could say more: > - i don't like how LinkedList implemented. > > I don't see why it should mimic things like #at: #at:put: at all.. > IMO this protocol should be pruned from it, to not provoke uses which > completely do not fit for given data structure. > > Removing/inserting into the middle of list is quite ineffective > operation (O(n)), > while inserting at the begginning/end of list is O(1). > > Lists are sequenceable.. but sequenceable ~~ indexable. Period. > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 19, 2010

Re: [Pharo-project] bad bracket autocompletion in Pharo Core 1.2

by StÃ©phane Ducasse

>> >> > > Maybe Pharo runs some hidden AI process, which refactors and changes > things under the hood? :) If we could educate it to autofix it this would be a clear win-win situation :) Seriously guillermo how this code arrived in since it is not in CUIS? Stef

Oct. 19, 2010