December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] What are MethodDictionary faults?

by StÃ©phane Ducasse

> What's MW ? MethodWrapper. But you cannot wrap the complete system like do: (if I remember correctly). > Yes, I noticed that too. Is very probable that messages very general that are used a lot will bring the class again. Yes the problem is to identify them. We tried a bit not too much with mathieu but was not obvious > That's the idea of the tracer. WIth this tracer you *should* be able to see the messages chain that makes you bring the class (why it was used). But I don't know if this stuff is working, as you said. which tracer? What I suggest: - create a new category in the class and move all the methods that could be removed. Tag them as deprecated. - in imageSegments just clean :) Stef

Dec. 24, 2009

Re: [Pharo-project] New pharo images

by Alain Plantec

StÃ©phane Ducasse a Ã©crit : >> 2009/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>> Damien in 1.1 may be we should put the nice little font of Cuis on :) >>> >> Tell me what I should do. >> > > We should check the code of settings to see how the preferences is done > when we press the launch button on the side of the install bitmap DejaVu fonts > I've checked, we have "bitmap dejavu sans" with sizes 7, 9 and 12. Alain

Dec. 24, 2009

Re: [Pharo-project] What are MethodDictionary faults?

by Mariano Martinez Peck

Adrian: Thanks, indeed cannotInterpret: was what I was looking for :) On Wed, Dec 23, 2009 at 5:19 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Ok this is in the image I did not remember (getting old) :) but the vm pay > attention > not to crash totally when you put nil in a methodDict. > > ok > Now what I know is that a while back when we activate > Smalltalk at: #MDFaultDict put: Dictionary new. > We kind of either crashed or got all the classes of the system in. > > I have the impression that this is just a hack and I would remove it from > the system > because we can do with MW or reflectivity (even if we probably cannot trace > the tracing code). > What's MW ? Now...the question is, suppose I remove all the methods like discoverUnusedCLasses, activeClasses, and so on, can I remove also the methods induceMDFault, recoverFromMDFault, etc ??? Or there are other users? As I understood, there aren't. In addition, I don't see the relation between cannotInterpret: and those methods, because cannotInerpret: does not call this methods to recover. > Also the granularity is really the class so as soon as one method is > invoked you get all the class back. > Yes, I noticed that too. Is very probable that messages very general that are used a lot will bring the class again. > So with mathieu we simply something could not understand why all the > classes would be touched > may be browser was scanning all the image. No idea. but at the end it was > not useful. > That's the idea of the tracer. WIth this tracer you *should* be able to see the messages chain that makes you bring the class (why it was used). But I don't know if this stuff is working, as you said. > > Stef > > On Dec 23, 2009, at 4:51 PM, Adrian Kuhn wrote: > > > Mariano Martinez Peck <marianopeck@...> writes: > > > >> So, it seems to HACK (it forces a fault) this MD fault recover to > discover > >> inactive classes and other things. Ok, forget that hack for a moment. > >> > >> What questions is, what are these faults? Why a method dictionary can > be in > >> nil ? How is this produced ? And how is it fixed? > >> > >> I saw for example this: > >> > >> Behaviour>>methodDict > >> methodDict == nil ifTrue: [self recoverFromMDFaultWithTrace]. > >> ^ methodDict > >> > >> But again...how can that be nil ??? > > > > I guess your missing link is > > > > ProtoObject >> #cannotInterpret: > > > > which is executed by the VM whenever you try to send a message to an > object > > whose class does not have a method dictionary. Further methods that you > should > > look at are > > > > ClassDescription >> #induceMDFault > > ClassDescription >> #recoverFromMDFault > > ClassDescription >> #recoverFromMDFaultWithTrace > > > > and their senders. Except for the call to #cannotInterpret by the VM, all > the > > rest is done in the image (stef got that wrong) and you can go and read > the > > code. All in all, it is a highly sophisticated (read *ugly*) hack and I'd > say > > an evil use of superpowers. > > > > --AA > > > > > > > > > > > > > > _______________________________________________ > > 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 >

Dec. 24, 2009

Re: [Pharo-project] SUnit forked, gofer it

by Mariano Martinez Peck

hahahah did I convinced you ? Thank you very much. This was my little christmas gift. I put the issue as closed. Cheers Mariano On Thu, Dec 24, 2009 at 10:56 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > Changed in > > Name: OB-SUnitIntegration-lr.16 > Author: lr > Time: 24 December 2009, 10:54:56 am > UUID: 661b0ef3-03df-4193-84ed-e482c9baaec6 > Ancestors: OB-SUnitIntegration-AdrianKuhn.15 > > - run tests depending on selection > > 2009/12/24 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > > > > On Thu, Dec 24, 2009 at 9:52 AM, Lukas Renggli <renggli(a)gmail.com> > wrote: > >> > >> Indeed, it aways runs all tests of a class. Should that be changed? I > > > > Yes!!!! If you have selected a particular method, the idea is to run > THAT > > method, not all. Why you need to select then ? > > If you want all methods go to the class or even to the tests runner. > > > >> > >> found it more useful to run them all, instead of just one. > >> > >> Lukas > >> > >> 2009/12/24 Adrian Kuhn <akuhn(a)iam.unibe.ch>: > >> > Tudor Girba <tudor.girba@...> writes: > >> > > >> >> It should work if your mouse is over the methods pane. > >> > > >> > Not true in OB. > >> > > >> > > >> > -- > >> > 4th Workshop on Dynamic Languages and Applications > >> > Submit papers by March 31, 2010. http://bit.ly/dyla2010 > >> > > >> > > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > >> > >> > >> > >> -- > >> Lukas Renggli > >> http://www.lukas-renggli.ch > >> > >> _______________________________________________ > >> 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 > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 24, 2009

Re: [Pharo-project] SUnit forked, gofer it

by Lukas Renggli

Changed in Name: OB-SUnitIntegration-lr.16 Author: lr Time: 24 December 2009, 10:54:56 am UUID: 661b0ef3-03df-4193-84ed-e482c9baaec6 Ancestors: OB-SUnitIntegration-AdrianKuhn.15 - run tests depending on selection 2009/12/24 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > On Thu, Dec 24, 2009 at 9:52 AM, Lukas Renggli <renggli(a)gmail.com> wrote: >> >> Indeed, it aways runs all tests of a class. Should that be changed? I > > Yes!!!!Â Â If you have selected a particular method, the idea is to run THAT > method, not all. Why you need to select then ? > If you want all methods go to the class or even to the tests runner. > >> >> found it more useful to run them all, instead of just one. >> >> Lukas >> >> 2009/12/24 Adrian Kuhn <akuhn(a)iam.unibe.ch>: >> > Tudor Girba <tudor.girba@...> writes: >> > >> >> It should work if your mouse is over the methods pane. >> > >> > Not true in OB. >> > >> > >> > -- >> > 4th Workshop on Dynamic Languages and Applications >> > Submit papers by March 31, 2010. http://bit.ly/dyla2010 >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> >> >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 24, 2009

Re: [Pharo-project] SUnit forked, gofer it

by Mariano Martinez Peck

On Thu, Dec 24, 2009 at 9:52 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > Indeed, it aways runs all tests of a class. Should that be changed? I > Yes!!!! If you have selected a particular method, the idea is to run THAT method, not all. Why you need to select then ? If you want all methods go to the class or even to the tests runner. > found it more useful to run them all, instead of just one. > > Lukas > > 2009/12/24 Adrian Kuhn <akuhn(a)iam.unibe.ch>: > > Tudor Girba <tudor.girba@...> writes: > > > >> It should work if your mouse is over the methods pane. > > > > Not true in OB. > > > > > > -- > > 4th Workshop on Dynamic Languages and Applications > > Submit papers by March 31, 2010. http://bit.ly/dyla2010 > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 24, 2009

Re: [Pharo-project] Fwd: sort: and sortBlock:

by StÃ©phane Ducasse

> > sorted is bad name Now given the situation and the result of the discussion we could have it in addition to sort sorted -> always a copy sort -> inplace when possible on SortedCollection, OrderedCollection and others. Stef

Dec. 24, 2009

Re: [Pharo-project] SUnit forked, gofer it

by StÃ©phane Ducasse

Normally it works to click on the class or package to run all the test of the packages now may be the binding does not do it but pressing on the icon was working like that On Dec 24, 2009, at 10:16 AM, Adrian Kuhn wrote: > Lukas Renggli <renggli@...> writes: > >> Indeed, it always runs all tests of a class. Should that be changed? I >> found it more useful to run them all, instead of just one. > > Fixed it in my image (and attached on google). > > Its awesome when you work on one test in particular.It is somehow annoying > when you browse a package ... click click click ... dive into one method > and want to run the whole test case. But one might get used to it quickly. > > Maybe different action for Cmd+T in the source editor and the method list? > (or is that too confusing?) > > --AA > > PS: also broken was that when you ran one method the history of all other > methods was lost. Fixed in akuhn/SUnit now. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 24, 2009

Re: [Pharo-project] #sorted/#sorted:

by StÃ©phane Ducasse

On Dec 24, 2009, at 10:12 AM, Julian Fitzell wrote: > On Thu, Dec 24, 2009 at 12:19 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >>> #sorted, #sorted: -- VW already has this. VA is adding it. >>>> >>>> What is sorted? a boolean predicate method? >>>> What a bad name. Did they forgot Kent? >>> >>> An example of my previous message -- this name is confusing and should >>> probably not be used. >> >> Yes I agree > > I'm not interested in waging a battle over naming with hundreds of > people on a mailing list. why? We are discussing and getting a consensus. > I can give a few examples of why I think > it's clear, but in the end, my usage (being pragmatic and concerned > primarily with compatibility) is going to go with the majority of > platforms. We are pragmatic too. We try to avoid that people always do the same mistakes and get polymorphic classes - which is too me really important. We got burnt by that with VW. You know the asSortedCollection everywhere or not wanted a copy > Adjective method selectors seem to normally be side-effect free and > return a copy of the object modified in some way, e.g.: #capitalized, > #shuffled, #padded:to:with:, #withBlanksTrimmed. I can't think of any > method selectors that are adjectives and don't return a modified copy > of the object (though I'm sure someone will come up with some > examples). > > Methods selectors that cause the object to do something or to change > itself in some way are pretty much all imperative verbs: #grow, > #clear, #close (there are, of course, plenty of verbal selectors that > *do* return a copy). > > And for what it's worth, nouns tend to be accessors (#name, #size) and > predicates (#isEmpty, #canUnderstand:) tend to be test methods. There > are plenty of other grammar-based patterns. > > I can see an argument for #copySorted, but personally I don't think it > makes things much clearer and by that logic you need to have > #copyShuffled, #copyWithBlanksTrimmed, etc. Since adjectives always > seem to return a copy anyway, the "copy" verb seems redundant. > > Anyway, that's all I have to say about it. You guys carry on and name > the method anything you like - I was just letting you know what the > other platforms have. :) This is important but now you can also say to VA people that copying VW is not always the best choice. > > Julian > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 24, 2009

Re: [Pharo-project] New pharo images

by StÃ©phane Ducasse

> 2009/12/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Damien in 1.1 may be we should put the nice little font of Cuis on :) > > Tell me what I should do. We should check the code of settings to see how the preferences is done when we press the launch button on the side of the install bitmap DejaVu fonts I should work on project proposal now so no fun. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 24, 2009