- Pharo-dev - lists.pharo.org

[Pharo-project] Pharo VMs should be more Pharo-like
by Esteban Lorenzano Dec. 4, 2011

Dec. 4, 2011

Hi, Currently, we are linking official VMs for pharo taking directly from Jenkins a version and packaging for download (or for Pharo One-Click). I think this is a temporal solution, we need something better: 1) Pharo VMs should have Pharo Icons. 2) Pharo VMs should be named "pharo" or "pharovm" (better the fist), not "CogVM", which is an internal name. 3) We should include a PLUGINS.txt file with information about present plugins (internal and external) 4) We should include a LICENCE.txt file with all licence information. ... I think that's all :) I know... this is very dumb and clearly not mandatory, but it says a lot about the maturity of our Pharo :) All agree? Should I create a ticket? Cheers, Esteban pd: I'm the only one who does not likes One-Click versions? I would prefer a different package for each platform (Is ugly to have a directory named Pharo.app in linux or windows. Also, no need to have all those duplicated-but-for-different-platform files)

10 13

[Pharo-project] VM freezes sending #basicNew to Stream subclass
by Larry White Dec. 3, 2011

Dec. 3, 2011

Hi, Throwing this out there because it may be a bug. I'm running the Seaside one-click install on OS X Lion. Pharo1.3 Latest update: #13302 I can reliably cause my VM to freeze up and need to Force-Quit it from the OS. I'm implementing (copying) the probability logic from the blue book. When I tried to create an instance of the Binomial class, the system hung. I can replicate the problem by sending the message #basicNew to ProbabilityDistribution. ProbabilityDistribution is a direct subclass of Stream and I haven't overridden or modified #basicNew. What's happening is that it fails in the BlockClosure [anObject doit], but only when I instantiate a member of this particular class hierarchy. In the probability classes, a #doIt in a Workspace hits the line "self suspend" in the #terminate method of Process and the VM hangs there. I believe they had ProbabilityDistribution subclass from Stream because sampling from a distribution is like reading from a Stream, but I don't think any there's any actual shared code, so I switched the superclass of ProbabilityDistribution to Object and the code works fine now. Thanks. Larry

4 13

Re: [Pharo-project] [Pharo-users] [COTDC] 89 - NullStream
by StÃ©phane Ducasse Dec. 3, 2011

Dec. 3, 2011

I'm a stream doing nothing (NullObject pattern). I can be handy when a stream is needed and that we need to do nothing (for example a logging in off mode). Stef On Dec 3, 2011, at 11:29 AM, sean(a)clipperadams.com wrote: > 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] Monticello enhancing
by Tobias Pape Dec. 3, 2011

Dec. 3, 2011

Dear all, afte Fuel being available for both Squeak and Pharo, I experimented a little bit. So, I put a new snapshot.fuel beside the snapshot.bin in the mcz zips (same for patch.* in mcd). But to make it easier in the future to experiment with things, I included a small facility to extend serializers/materializers or similar things more easily. How is it done? Example: new serializer in MCZ files: After my patch, include MCMczWriter class>>serializerMine ^ [:writer :snapshot | writer writeSnapshotAsMyFormat: snapshot] and MCMczWriter>>writeSnapshotAsMyFormat: snapshot self addString: (self doSomeConversion: aSnapshot) at: 'snapshot.myformat'. as Extension methods in MCMczWriter, and execute MCMczWriter populateSerializers. Now, a new file member is added to every new mcz file. As an example, I have done such thing for Fuel. Don't worry, it just uses the default behavior if Fuel is not present in either the image or the mcz-file. Best, -Tobias PS: for Squeak, see Inbox Monticello-topa.491, And I also have an MCD attached that should help using the code elsewhere.

3 6

[Pharo-project] A commercial question
by GermÃ¡n Arduino Dec. 3, 2011

Dec. 3, 2011

Hi: I'm only starting in the Apple software market and would like to ask the viability of sell desktop software developed with Pharo (I mean commercial sort of trialware software). I know my question is very general, but is focused mainly in the look and feel (I'm pretty sure that can develop any functionality I want) but not sure about the look and feel. The average Apple user could accept the look and feel of a morphic pharo application? (Very different than the osx l&f). Other options? Experiences, suggestions, are more than welcome. I know that the Apple store don't accept Pharo apps, but still if they have sales possibilities, I could try by my own. What do you think? Thanks. -- ============================================ GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com Promoter http://www.arsol.biz ============================================

6 9

[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

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