September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] MethodWrappers

by Frank Shearar

On 21 September 2011 12:26, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Sep 21, 2011, at 12:59 PM, Frank Shearar wrote: > >> On 21 September 2011 11:48, Torsten Bergmann <astares(a)gmx.de> wrote: >>> Hi Eliot, >>> >>> at [1] you mentioned a port of MethodWrappers to Squeak 4.2. >>> Is there also a port for Pharo available or do you plan to >>> port it? >>> >>> For those who dont know about MethodWrappers: look at [2] >> >> And if you're wondering why on Earth you'd want them, take a look at >> SUnit's TestCoverage class for a use case. >> > But that is working in Pharo already, isn't it? > > Using the MethodWrapper version that is based on Object-As-Methods, > as far as I know. Indeed - I didn't mean to suggest that TestCoverage uses MethodWrappers the library, just that it uses the concept of method wrappers. (What it does is replace the existing CompiledMethods in a class' method dictionary with a TestCoverage instance proxying the CompiledMethod. When you run that method, you set a flag in the TestCoverage instance. After you've calculated the package tests' coverage, it uninstalls itself by replacing itself with the original CompiledMethod in the class' method dictionary.) frank > Â Â Â Â Marcus > > > > -- > Marcus Denker -- http://marcusdenker.de > > >

Sept. 21, 2011

Re: [Pharo-project] MethodWrappers

by Marcus Denker

On Sep 21, 2011, at 12:59 PM, Frank Shearar wrote: > On 21 September 2011 11:48, Torsten Bergmann <astares(a)gmx.de> wrote: >> Hi Eliot, >> >> at [1] you mentioned a port of MethodWrappers to Squeak 4.2. >> Is there also a port for Pharo available or do you plan to >> port it? >> >> For those who dont know about MethodWrappers: look at [2] > > And if you're wondering why on Earth you'd want them, take a look at > SUnit's TestCoverage class for a use case. > But that is working in Pharo already, isn't it? Using the MethodWrapper version that is based on Object-As-Methods, as far as I know. Marcus -- Marcus Denker -- http://marcusdenker.de

Sept. 21, 2011

[Pharo-project] [update 1.4] #14159

by Marcus Denker

14159 ----- Issue 3527: Generator http://code.google.com/p/pharo/issues/detail?id=3527 Issue 4791: Add a class to have a better holding of IconicList items http://code.google.com/p/pharo/issues/detail?id=4791 Issue 4841: can't forbid the styling of a text view with #styled: + need for commented examples http://code.google.com/p/pharo/issues/detail?id=4841 -- Marcus Denker -- http://marcusdenker.de

Sept. 21, 2011

Re: [Pharo-project] MethodWrappers

by Frank Shearar

On 21 September 2011 11:48, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Eliot, > > at [1] you mentioned a port of MethodWrappers to Squeak 4.2. > Is there also a port for Pharo available or do you plan to > port it? > > For those who dont know about MethodWrappers: look at [2] And if you're wondering why on Earth you'd want them, take a look at SUnit's TestCoverage class for a use case. frank > Thanks > Torsten > > > [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-September/16156… > [2] http://www.refactory.com/Software/MethodWrappers/ > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > >

Sept. 21, 2011

[Pharo-project] MethodWrappers

by Torsten Bergmann

Hi Eliot, at [1] you mentioned a port of MethodWrappers to Squeak 4.2. Is there also a port for Pharo available or do you plan to port it? For those who dont know about MethodWrappers: look at [2] Thanks Torsten [1] http://lists.squeakfoundation.org/pipermail/squeak-dev/2011-September/16156… [2] http://www.refactory.com/Software/MethodWrappers/ -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

Sept. 21, 2011

Re: [Pharo-project] Interesting expression...

by Stephan Eggermont

> ((para isKindOf: MultiNewParagraph) or: [para text string isByteString > or: [para text string isWideString]]) If you want to be able to handle large texts with nice (LaTeX-like) line breaking we'll probably need some different String implementations. I don't know how far MultiNewParagraph scales. Stephan

Sept. 21, 2011

Re: [Pharo-project] Fix for Explorer->Browse full

by Dennis Schetinin

Oh, thanks :) 2011/9/21 Marcus Denker <marcus.denker(a)inria.fr> > > On Sep 21, 2011, at 10:41 AM, Dennis Schetinin wrote: > > > That's great, but how can I update my existing images to fix it? > > > > You can run: > > UpdateStreamer new updateFromServer > > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Dennis Schetinin

Sept. 21, 2011

Re: [Pharo-project] Fix for Explorer->Browse full

by Marcus Denker

On Sep 21, 2011, at 10:41 AM, Dennis Schetinin wrote: > That's great, but how can I update my existing images to fix it? > You can run: UpdateStreamer new updateFromServer -- Marcus Denker -- http://marcusdenker.de

Sept. 21, 2011

Re: [Pharo-project] Should a serializer do something in particular with weak references?

by Igor Stasenko

On 21 September 2011 07:39, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi >> if you look at the problem in wider perspective, then right question >> to ask, is how to deal >> with objects which are register themselves in global facilities, like >> weak finalization, >> startup/shutdown lists etc. > Fuel can handle globals... but I don't understand how can weak objects be > accessed as global. Could you give a snippetÂ exemplifying, please? it depends who will use fuel and for what. for that reason, i think it is up to user(s) of fuel to determine what they want to serialize by having the logic which separating an objects which they want to store, and rest of the world. While in fuel itself, i don't see a possibility to make it so, that it will work for every possible use case, this is simply unrealistic. > Martin > On Tue, Sep 20, 2011 at 11:03 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 21 September 2011 03:15, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> >> wrote: >> > But how does Fuel "know" that the objects are not otherwise referenced? >> > Â The idea of ignoring weak collections sounds a lot like a compiler >> > optimization that sounds efficient and harmless - sometimes they cause huge >> > problems. Â Think of it this way, if the objects are not otherwise >> > referenced, sure they will be gc's soon - why are are they still around??? >> >> the main problem i think is to make fuel to know which objects are >> belong to your model, and which is not. >> because in Levente's suggestion, this makes a difference between >> either serializing a pointer or just replacing it with nil. >> >> But then, once you introduce "this object belongs to my model" logic, >> a new question immediately arises: what if some object strongly >> referencing an object outside your model? >> So, the problem is more general than just do it selectively only for >> weak containers. Either you doing it uniformly (providing facilities >> to deal with everything which outside your domain/model somehow), >> or you just walk the graph and storing everything (treating all object >> found as ones , who belong to your model). And there is nothing >> special to do with weak containers. >> >> > The comments re globally registered objects are well taken too. >> > Â Dolphin's proxies are a great way to handle such things: some objects >> > delegate their serialization to a proxy that contains logic to do global >> > registration, etc. >> > >> > Bill >> > >> > >> > ________________________________________ >> > From: pharo-project-bounces(a)lists.gforge.inria.fr >> > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Nicolas Cellier >> > [nicolas.cellier.aka.nice(a)gmail.com] >> > Sent: Tuesday, September 20, 2011 6:08 PM >> > To: Pharo-project(a)lists.gforge.inria.fr >> > Subject: Re: [Pharo-project] Should a serializer do something in >> > particular with weak references? >> > >> > 2011/9/21 Levente Uzonyi <leves(a)elte.hu>: >> >> On Tue, 20 Sep 2011, Mariano Martinez Peck wrote: >> >> >> >>> Hi guys. Martin and I were discussing whether we should do something >> >>> in >> >>> particular in Fuel with Weak references, such as WeakArray. Should we >> >>> serialize it the same way we serialize all objects, or should we do >> >>> something special? Â what could be the impact of materializing such >> >>> weak >> >>> references in a new image for example? >> >> >> >> You should ignore (serialize nil instead of them) the elements of a >> >> weak >> >> object (#weakSubclass:...) which aren't referenced strongly from other >> >> serialized objects. >> >> >> >> >> >> Levente >> >> >> > >> > Ach, you commited shorter and quicker ;) >> > >> > Nicolas >> > >> >>> >> >>> Thanks your sharing your thoughts. >> >>> >> >>> -- >> >>> Mariano >> >>> http://marianopeck.wordpress.com >> >>> >> >> >> >> >> > >> > >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

Sept. 21, 2011

Re: [Pharo-project] Fix for Explorer->Browse full

by Dennis Schetinin

That's great, but how can I update my existing images to fix it? 2011/9/21 Marcus Denker <marcus.denker(a)inria.fr> > > On Sep 21, 2011, at 10:29 AM, Dennis Schetinin wrote: > > > I have that issue in my 1.3 images (including the PharoOneClick1.3 > #13299, for instance). > > > It was fixed in an update after 13299. The current version is 13307 > > Marcus > > > > 2011/9/21 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > it is integrated in 1.3 and 1,4 so this is fixed no? > > > > Stef > > On Sep 21, 2011, at 4:17 AM, Dennis Schetinin wrote: > > > > > Yea, that irritates me, thanks for the fixâ¦ but the links look broken > for me. > > > > > > 2011/9/13 Sean P. DeNigris <sean(a)clipperadams.com> > > > You may have noticed the very annoying bug in 1.3 and 1.4, where when > you try > > > to browse the class, the browser always takes you to ByteString, no > matter > > > what's selected. This has been fixed in both 1.3 and 1.4 > > > (http://code.google.com/p/pharo/issues/detail?id=4548) > > > > > > If you have a version of 1.3 dev without the fix, you can file > > > http://forum.world.st/file/n3810137/Inspector-browseMethodFull.st > > > Inspector-browseMethodFull.st in. > > > > > > Cheers, > > > Sean > > > > > > -- > > > View this message in context: > http://forum.world.st/Fix-for-Explorer-Browse-full-tp3810137p3810137.html > > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > > > > > > > > > > > -- > > > Dennis Schetinin > > > > > > > > > > > > -- > > Dennis Schetinin > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Dennis Schetinin

Sept. 21, 2011