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

[Pharo-project] [update 1.4] #14243
by Marcus Denker Dec. 3, 2011

Dec. 3, 2011

14243 ----- Issue 5052: #subclassResponsibility should not print the object but the class name http://code.google.com/p/pharo/issues/detail?id=5052 Issue 5050: restart UIProcess in next postscript http://code.google.com/p/pharo/issues/detail?id=5050 Issue 5049: Remove TestNewParagraphFix http://code.google.com/p/pharo/issues/detail?id=5049 Issue 5051: [ENH]: Clean up Mail code http://code.google.com/p/pharo/issues/detail?id=5051 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [COTDC] 89 - NullStream
by sean＠clipperadams.com Dec. 3, 2011

Dec. 3, 2011

Continuing in Collections... Today: NullStream Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

1 0

[Pharo-project] Consortium memberships brainstorming and ideas
by StÃ©phane Ducasse Dec. 3, 2011

Dec. 3, 2011

HI We would like to get your point of view about the following (we discussed with INRIA lawyer and others. Goal: Remember we want to be able to pay an engineer (cost 55K). Constraints: We do not want a special license for people participating to the consortium and the others. It means that members may not have immediate advantages like 10% reduction :). But it also means that the system is clean, simple, â¦. Proposals: Individual Member: - Free membership Institutional Member: (like Lab, Universityâ¦.) - 1000 Euros Company - First level support: 2000-3000 Euros - Extended Support: 5000-6000 Euros Then finally we want to have a donation for >500 Euros Now with these numbers: we can do it. It may be tight but this would be a huge success! we need 20 first level support 2000 Euros * 20 = 40000 two extended 5000 Euros * 2 = 12000 5 institutionals 5* 1000 = 5000 Gift: 500 * 10 = 5000 So let us know what do you think? Stef

1 0

[Pharo-project] TestNewParagraphFix
by Sean P. DeNigris Dec. 3, 2011

Dec. 3, 2011

NewParagraph is deprecated in 1.4. TestNewParagraphFix doesn't actually mention NewParagraph directly. The class comment says "This class tests the same things as its superclass, but for NewParagraph which is used in the Morphic environment." but its superclass is TestCase. Is TestNewParagraphFix still relevant? What was the original motivation i.e. why is it called XxxFix? Sean -- View this message in context: http://forum.world.st/TestNewParagraphFix-tp4147219p4147219.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

Re: [Pharo-project] [squeak-dev] Re: Prune stack serialization
by Mariano Martinez Peck Dec. 3, 2011

Dec. 3, 2011

Thank you very much Eliot and Juan for this nice discussion. I have just commit this new functionality and it seems to work fine. I ended up using Eliot's #abstractBytecodes since the one from Juan didn't work out of the box in Pharo. On Fri, Dec 2, 2011 at 10:38 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > Hi Juan, > > On Fri, Dec 2, 2011 at 11:59 AM, Juan Vuletich <juan(a)jvuletich.org> wrote: > >> Mariano Martinez Peck wrote: >> >>> >>> >>> On Fri, Dec 2, 2011 at 9:46 PM, Eliot Miranda <eliot.miranda(a)gmail.com<mailto: >>> eliot.miranda(a)gmail.**com <eliot.miranda(a)gmail.com>>> wrote: >>> >>> >>> >>> On Fri, Dec 2, 2011 at 12:40 PM, Mariano Martinez Peck >>> <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>**> wrote: >>> >>> >>> >>> On Fri, Dec 2, 2011 at 8:30 PM, Juan Vuletich >>> <juan(a)jvuletich.org <mailto:juan@jvuletich.org>> wrote: >>> >>> Eliot Miranda wrote: >>> >>> >>> >>> On Fri, Dec 2, 2011 at 10:55 AM, Mariano Martinez Peck >>> <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com> >>> <mailto:marianopeck@gmail.com >>> >>> <mailto:marianopeck@gmail.com>**>> wrote: >>> >>> Thanks both. I am right to assume that if the block >>> refers to temp >>> vars, parameters, or whatever in another scope, >>> then such solution >>> won't work. I mean, if I have this example for example: >>> >>> | bytes result blah | >>> blah := 42. >>> bytes := FLSerializer serializeToByteArray: >>> (SortedCollection >>> sortBlock: [:a :b | (a + blah) > b ]). >>> >>> Then the 'blah' is in a different context. So the >>> mentioned >>> solution works for "clean" closures, which are >>> "self contained". >>> In the other cases (such as this example), we >>> should serialize the >>> whole stack. Is this correct? >>> >>> >>> No. The closure implementation arranges that any and >>> all temporary variables accessed by the closure are >>> directly accessible from the closure without accessing >>> the outer contexts. >>> ... >>> >>> >>> WRT clean closures, check what I did in Cuis to serialize >>> SortedCollections. See implementors and senders of #isClean. >>> >>> >>> Nice. Thanks Juan. I was checking your code, and that's >>> exactly why I asked Eliot. In your method you say: >>> >>> isClean >>> "A clean closure is one that doesn't really need the home >>> context because: >>> - It doesn't send messages to self or super >>> - It doesn't access any instance variable >>> - It doesn't access any outer temp >>> - It doesn't do ^ return" >>> ..... >>> >>> So... my question is, WHAT do I need to serialize if I want to >>> be able to serialize also "non clean". >>> >>> >>> IMO, dy default, everything reachable from the closure, including >>> the outerContext chain and their senders. But that's only a >>> default. What makes sense in any given context is up to the >>> application, e.g. see Seaside. One size won't fit all. You >>> should handle the common cases (e.g. clean blocks and everything >>> else) and leave it up to the user to figure out what they need to >>> do in complex situations, making sure you provide them with the >>> hooks they'll need, such as the ability to substitute objects when >>> serializing etc, and perhaps some useful examples. >>> >>> >>> +1 Then we will do the following: we will check whether the closure is >>> clean. If it is, then we serialize just the closure plus its outerContext >>> but only with receiver and method. If it is not clean, then we serialize >>> the whole stack. That's all by default. If then someone needs something >>> different, then to use the hooks :) >>> So the final question is whether what Juan is using in Cuis is up to >>> date. If it is, then I have all I need :) >>> Thank you guys. >>> >> >> I can say that it does indeed work. But I'd be really grateful if Eliot >> took a good look at that code! >> > > There is a much better way, using > InstructionStream>>interpreetNextInstructionFor: which abstracts away from > the bytecode encoding and allows one to simply use messages. e.g. look at > > BlockClosure methods for private > abstractBytecodes > "Answer an OrderedCollection of the abstract bytecodes sent in the > receiver." > | scanner blockCreationMessage end abstractBytecodes | > scanner := InstructionStream new. > "find the creation message to find the extent of the block." > scanner method: self method pc: self method initialPC. > [scanner pc < startpc] whileTrue: > [[scanner interpretNextInstructionFor: nil] > on: MessageNotUnderstood > do: [:ex| blockCreationMessage := ex message]]. > end := blockCreationMessage arguments last + startpc - 1. > "now collect all the bytecode messages in the block." > abstractBytecodes := OrderedCollection new. > scanner method: self method pc: startpc. > [scanner pc < end] whileTrue: > [[scanner interpretNextInstructionFor: nil] > on: MessageNotUnderstood > do: [:ex| abstractBytecodes add: ex message selector]]. > ^abstractBytecodes > > and (SortedCollection sortBlock: [:a :b| a compare: b caseSensitive: > false]) sortBlock abstractBytecodes evaluates to > > an OrderedCollection(#pushTemporaryVariable: #pushTemporaryVariable: > #pushConstant: #send:super:numArgs:) > > So a check for clean blocks would check for a block's abstractBytecodes > not including some particular set of banned messages (which I *think* is > pushReceiver pushReceiverVariable: popIntoReceiverVariable: > storeIntoReceiverVariable: methodReturnConstant: methodReturnReceiver > methodReturnTop). > > e.g. > > isClean > ^(self abstractBytecodes intersection: #(pushReceiver > pushReceiverVariable: popIntoReceiverVariable: storeIntoReceiverVariable: > methodReturnConstant: methodReturnReceiver methodReturnTop)) isEmpty > > >> Cheers, >> Juan Vuletich >> >> >>> >>> >>> I mean, for each item on that list, what do I need apart from >>> the closure instance and the receiver and method from the >>> outerContext ? the whole stack of contexts ? >>> >>> >>> Thanks a lot in advance! >>> >>> >>> >>> -- Mariano >>> http://marianopeck.wordpress.**com<http://marianopeck.wordpress.com> >>> >>> >>> >>> >>> >>> >>> >>> -- best, >>> Eliot >>> >>> >>> >>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >>> >>> ------------------------------**------------------------------** >>> ------------ >>> >>> >>> >>> ------------------------------**------------------------------** >>> ------------ >>> >>> No virus found in this message. >>> Checked by AVG - www.avg.com <http://www.avg.com> >>> Version: 10.0.1411 / Virus Database: 2102/4052 - Release Date: 12/02/11 >>> >>> >> >> > > > -- > best, > Eliot > > > > > -- Mariano http://marianopeck.wordpress.com

1 0

[Pharo-project] SubscriptOutOfBounds while Debugging
by Sean P. DeNigris Dec. 2, 2011

Dec. 2, 2011

In Pharo1.4a Latest update: #14238, I keep getting the error while stepping through code. Also, the tools (Browser, Implementors, etc.) take *forever* to appear. Is anyone else experiencing either? Sean -- View this message in context: http://forum.world.st/SubscriptOutOfBounds-while-Debugging-tp4148106p414810… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

3 3

Re: [Pharo-project] [squeak-dev] Re: Prune stack serialization
by Mariano Martinez Peck Dec. 2, 2011

Dec. 2, 2011

> WRT clean closures, check what I did in Cuis to serialize >> SortedCollections. See implementors and senders of #isClean. >> >> >> Nice. Thanks Juan. I was checking your code, and that's exactly why I >> asked Eliot. In your method you say: >> >> isClean >> "A clean closure is one that doesn't really need the home context >> because: >> - It doesn't send messages to self or super >> - It doesn't access any instance variable >> - It doesn't access any outer temp >> - It doesn't do ^ return" >> ..... >> >> So... my question is, WHAT do I need to serialize if I want to be able to >> serialize also "non clean". I mean, for each item on that list, what do I >> need apart from the closure instance and the receiver and method from the >> outerContext ? the whole stack of contexts ? >> >> > I think it is needed to know why you need to serialize a non-clean > closure. If it is just to be able to evaluate it, well, some people may just need that, but there are cases where I need it completely. I mean, I need to serialize the whole possible graph of objects. This is an example for what I am doing in my PhD. We are also experiment with remote messages and things like that and sometimes we pass a whole stack. In that case I thin it also make sense. But again, these are particular cases. I agree that most of the times the closure will be "clean" > maybe you don't need the stack at all. My trick could be augmented by > serializing any referenced objects, but not the stack. > > Yes, maybe I was not clear. When I refer to "stack" I refer all instances of ContextPart (well, subclasses) and all the objects reachable from there. > Cheers, > Juan Vuletich > > > >> Thanks a lot in advance! >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.**com <http://marianopeck.wordpress.com> >> > > > -- Mariano http://marianopeck.wordpress.com

1 0

Re: [Pharo-project] [squeak-dev] Re: Prune stack serialization
by Mariano Martinez Peck Dec. 2, 2011

Dec. 2, 2011

On Fri, Dec 2, 2011 at 8:30 PM, Juan Vuletich <juan(a)jvuletich.org> wrote: > Eliot Miranda wrote: > >> >> >> On Fri, Dec 2, 2011 at 10:55 AM, Mariano Martinez Peck < >> marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>**> wrote: >> >> Thanks both. I am right to assume that if the block refers to temp >> vars, parameters, or whatever in another scope, then such solution >> won't work. I mean, if I have this example for example: >> >> | bytes result blah | >> blah := 42. >> bytes := FLSerializer serializeToByteArray: (SortedCollection >> sortBlock: [:a :b | (a + blah) > b ]). >> >> Then the 'blah' is in a different context. So the mentioned >> solution works for "clean" closures, which are "self contained". >> In the other cases (such as this example), we should serialize the >> whole stack. Is this correct? >> >> >> No. The closure implementation arranges that any and all temporary >> variables accessed by the closure are directly accessible from the closure >> without accessing the outer contexts. >> ... >> > > WRT clean closures, check what I did in Cuis to serialize > SortedCollections. See implementors and senders of #isClean. > > Nice. Thanks Juan. I was checking your code, and that's exactly why I asked Eliot. In your method you say: isClean "A clean closure is one that doesn't really need the home context because: - It doesn't send messages to self or super - It doesn't access any instance variable - It doesn't access any outer temp - It doesn't do ^ return" ..... So... my question is, WHAT do I need to serialize if I want to be able to serialize also "non clean". I mean, for each item on that list, what do I need apart from the closure instance and the receiver and method from the outerContext ? the whole stack of contexts ? Thanks a lot in advance! -- Mariano http://marianopeck.wordpress.com

1 1

[Pharo-project] VM page in pharo book is outdated
by Esteban Lorenzano Dec. 2, 2011

Dec. 2, 2011

Hi, Checking the pharo colaboractive book, I found that the VM building is old and it is not compatible anymore with our current process. Maybe "someone" (cough, cough, Mariano, cough, cough) could update it with better information? Cheers, Esteban pd: also... I'm a little worried about nobody noticing this before. That means people does not use pharo book? I think is a great way to share information, but maybe there is not much people aware of it... I know, there is a link in "external links" in main page and is top in "documentation"... I don't know if we can do it more visible or clear? ppd: I'd rearrange "pharo tools" section by adding subsections like: "Persistence", "Web", etc., today looks a little bit confusing, IMHO. pppd: yeah... today is my "stupid questions" day... :P

8 14

[Pharo-project] latest VM sources
by Pavel Krivanek Dec. 2, 2011

Dec. 2, 2011

Hi, a guy from Red Hat owes me a favor so he promised me to create official Fedora packages for latest Pharo/Squeak related projects (virtual machines and images). But he wants some information like where to find latests virtual machines source codes, what are the dependencies etc. Looking at squeakvm.org, there is only a link to 3.11-3.2135 svn repository. Can you please summarize me the links to latest StackVM and CogVM sources? I guess he will not want to fight to VMMaker - at least at start ;-). Cheers, -- Pavel

5 6