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

Re: [Pharo-project] merging latest polymorph

by Adrian Lienhard

Stef, I had the same problem and in addition I got a debugger each time I klicked into a text pane after merging Polimorph-Widgets. I added a note in http://code.google.com/p/pharo/issues/detail?id=1003. Gary replied: "Always best to merge the new versions since some differences between Squeak and Pharo ;-)". I reopened issue 1003. Adrian On Aug 5, 2009, at 12:22 , StÃ©phane Ducasse wrote: > Ok I will try > > What I did was to click on all the use incoming version and at the end > (at 5 left items) > it just looped for ever. I had the redo the use incoming version but > the number of conflicts > stayed the same for ever 5. > So far I could merge Polymorph-Widgets-gvc.70 but not Polymorph- > Widgets-gvc.71 > > Stef > > On Aug 5, 2009, at 12:08 PM, Damien Cassou wrote: > >> On Wed, Aug 5, 2009 at 11:18 AM, StÃ©phane >> Ducasse<stephane.ducasse(a)inria.fr> wrote: >>> Hi adrian >>> >>> I got some problems when merging the latest polymorph (_ fixes). >>> I got conflicts when there should be none. I simply got revision >>> changed. >>> Did you already experience that? >> >> You may want to try _loading_ again the version from the Pharo >> repository and then _merging_ with the other repository. >> >> -- >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 6, 2009

[Pharo-project] updating a list morph

by Tudor Girba

Hi, I have a Morphic newbie question. I have a list morph: PluggableListMorph on: listModel list: #displayedItems selected: #selection changeSelected: #selection: I now would like it to update when the items change. Could anyone tell me how I accomplish that? Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

Aug. 5, 2009

Re: [Pharo-project] can anyone justify the following comment behaviour?

by Gabriel Cotelli

+1 to changing this... On Wed, Aug 5, 2009 at 4:59 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > Date: 2009-08-05 03:55:59 GMT (4 hours and 2 minutes ago) > Hi All, > > > in ParseNode>>printCommentOn: there is the most perplexing > destructive modification of a comment on printing: > > printCommentOn: aStream indent: indent > | thisComment | > self comment == nil ifTrue: [^ self]. > 1 to: self comment size > do: [:index | > index > 1 ifTrue: [aStream crtab: indent]. > aStream nextPut: $". > thisComment := self comment at: index. > self printSingleComment: thisComment > on: aStream > indent: indent. > aStream nextPut: $"]. > !! self comment: nil > > The result is that a parse tree can only be printed once before it > prints without comments. Can anyone justify this? I would like to > remove it; it makes no sense to me. > > best > Eliot > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 5, 2009

Re: [Pharo-project] Please update Linux VM

by Marcus Denker

On 05.08.2009, at 14:54, Mariano Martinez Peck wrote: > Hi folks. PLEASE a good soul of you update the linux VM from webpage? > http://gforge.inria.fr/frs/download.php/22421/pharo-vm-0.15.1b-linux.zip > > Every single day there are folks asking in Pharo IRC channel how to > use it. It is not intuitive and they are lost. No matter what you > say, the reality is that they are lost and confused. We must put a > readme.txt in pharo-vm-0.15.1b-linux.zip. The readme.txt can be > something as easy as: > > " > To run SqueakVm just do these steps: > 1) uncompress this zip. > 2) give execution permissons to the file "squeak" > 3) run squeak like this: ./squeak /home/you/your.image > " > > Thanks, Can you add a report at http://code.google.com/p/pharo/issues/list (We should have a bot for that ;-) Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Aug. 5, 2009

Re: [Pharo-project] [BUG] MethodContext allInstances size

by Marcus Denker

On 05.08.2009, at 13:18, Igor Stasenko wrote: >> >> Yes, and the real solution of course is to change the VM to allocate >> less >> contexts and use the C-stack instead... >> > hmm, doesn't that breaks the smalltalk introspection capabilities, > since then you can't see all the > context objects which is used by interpreter for running your code? > I want to point, that the way how VM allocating contexts is > implementation details , and if it done correctly > then you're still should be able to access all context objects. the magic is to create these objects as soon as you look at them. e.g, a description for visualworks: http://pages.cs.wisc.edu/~cymen/misc/interests/oopsla99-contexts.pdf Of course, even though as soon as I look at a thisContext, there is an object, I will not see all possible contexts with #allInstances, but only those that where created because they are needed. In that way, the implementation level optimization is not completely hidden. And of course, #allInstances works even for MethodContext, as no MethodContexts are created in a normal execution of a method like aInstancesDo:. Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Aug. 5, 2009

Re: [Pharo-project] [BUG] MethodContext allInstances size

by StÃ©phane Ducasse

allInstancesDo: aBlock "Evaluate the argument, aBlock, for each of the current instances of the receiver. Because aBlock might change the class of inst (for example, using become:), it is essential to compute next before aBlock value: inst." self == UndefinedObject ifTrue: [^ aBlock value: nil]. self allInstances do: [:each | aBlock value: each. ] Works On Aug 5, 2009, at 8:58 PM, StÃ©phane Ducasse wrote: > the problem now is that > > allInstancesDo: aBlock > "Evaluate the argument, aBlock, for each of the current instances of > the > receiver. > > Because aBlock might change the class of inst (for example, using > become:), > it is essential to compute next before aBlock value: inst." > | inst next | > self == UndefinedObject ifTrue: [^ aBlock value: nil]. > inst := self someInstance. > [inst == nil] > whileFalse: > [ > next := inst nextInstance. > aBlock value: inst. > inst := next] > > is looping too. > > Stef > > On Aug 5, 2009, at 7:01 PM, Marcus Denker wrote: > >> >> On 05.08.2009, at 12:42, Marcus Denker wrote: >>>>> >>>> Hmm, if that so, then we would expect to see an interpreter speed >>>> degradation. But its not. :) >>> >>> Yes, see the other mail. The reason is that the allocation of >>> contexts >>> in case of blocks happens now at #value, whereas it used to be just >>> done >>> at the definiton point (#blockCopy). >>> >>> So nothing to worry about. >> >> >> Eliot says: >> >> | So you can either >> | - wait for the stack VM or >> | - inline allInstancesDo: into allInstances or >> | - implement allInstacesDo: specially in ContextPart or >> | - implement a pair of primitives to answer allInstances and >> allObject atomically. >> | >> | This latter approach allows much more flexibility in implementing >> the garbage collector subsequently; for >> | example segmenting the heap and adding and freeing segments as >> required, which complicates the simple object >> | ordering provided by the single heap but has much better memory >> usage. >> >> >> I vote for inling for now... this fixes the problem. >> >> allInstances >> "Answer a collection of all current instances of the receiver." >> >> | all inst next | >> all := OrderedCollection new. >> inst := self someInstance. >> [inst == nil] >> whileFalse: [ >> next := inst nextInstance. >> inst == all ifFalse: [all add: inst]. >> inst := next]. >> ^ all asArray >> >> >> Marcus >> >> >> -- >> Marcus Denker - http://marcusdenker.de >> PLEIAD Lab - Computer Science Department (DCC) - University of Chile >> >> >> _______________________________________________ >> 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

Aug. 5, 2009

Re: [Pharo-project] Please update Linux VM

by Schwab,Wilhelm K

Don't forget the bit about renaming the UUID plugin _directory_ - that's a crash waiting to happen, unless it's been fixed?? Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Wednesday, August 05, 2009 1:54 PM To: Pharo Development Subject: [Pharo-project] Please update Linux VM Hi folks. PLEASE a good soul of you update the linux VM from webpage? http://gforge.inria.fr/frs/download.php/22421/pharo-vm-0.15.1b-linux.zip Every single day there are folks asking in Pharo IRC channel how to use it. It is not intuitive and they are lost. No matter what you say, the reality is that they are lost and confused. We must put a readme.txt in pharo-vm-0.15.1b-linux.zip. The readme.txt can be something as easy as: " To run SqueakVm just do these steps: 1) uncompress this zip. 2) give execution permissons to the file "squeak" 3) run squeak like this: ./squeak /home/you/your.image " Thanks, Mariano

Aug. 5, 2009

Re: [Pharo-project] [BUG] MethodContext allInstances size

by StÃ©phane Ducasse

the problem now is that allInstancesDo: aBlock "Evaluate the argument, aBlock, for each of the current instances of the receiver. Because aBlock might change the class of inst (for example, using become:), it is essential to compute next before aBlock value: inst." | inst next | self == UndefinedObject ifTrue: [^ aBlock value: nil]. inst := self someInstance. [inst == nil] whileFalse: [ next := inst nextInstance. aBlock value: inst. inst := next] is looping too. Stef On Aug 5, 2009, at 7:01 PM, Marcus Denker wrote: > > On 05.08.2009, at 12:42, Marcus Denker wrote: >>>> >>> Hmm, if that so, then we would expect to see an interpreter speed >>> degradation. But its not. :) >> >> Yes, see the other mail. The reason is that the allocation of >> contexts >> in case of blocks happens now at #value, whereas it used to be just >> done >> at the definiton point (#blockCopy). >> >> So nothing to worry about. > > > Eliot says: > > | So you can either > | - wait for the stack VM or > | - inline allInstancesDo: into allInstances or > | - implement allInstacesDo: specially in ContextPart or > | - implement a pair of primitives to answer allInstances and > allObject atomically. > | > | This latter approach allows much more flexibility in implementing > the garbage collector subsequently; for > | example segmenting the heap and adding and freeing segments as > required, which complicates the simple object > | ordering provided by the single heap but has much better memory > usage. > > > I vote for inling for now... this fixes the problem. > > allInstances > "Answer a collection of all current instances of the receiver." > > | all inst next | > all := OrderedCollection new. > inst := self someInstance. > [inst == nil] > whileFalse: [ > next := inst nextInstance. > inst == all ifFalse: [all add: inst]. > inst := next]. > ^ all asArray > > > Marcus > > > -- > Marcus Denker - http://marcusdenker.de > PLEIAD Lab - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 5, 2009

[Pharo-project] Please update Linux VM

by Mariano Martinez Peck

Hi folks. PLEASE a good soul of you update the linux VM from webpage? http://gforge.inria.fr/frs/download.php/22421/pharo-vm-0.15.1b-linux.zip Every single day there are folks asking in Pharo IRC channel how to use it. It is not intuitive and they are lost. No matter what you say, the reality is that they are lost and confused. We must put a readme.txt in pharo-vm-0.15.1b-linux.zip. The readme.txt can be something as easy as: " To run SqueakVm just do these steps: 1) uncompress this zip. 2) give execution permissons to the file "squeak" 3) run squeak like this: ./squeak /home/you/your.image " Thanks, Mariano

Aug. 5, 2009

Re: [Pharo-project] Wrong values of variables showed in execution context when doing self break?

by Dale Henrichs

Aug. 5, 2009