- Pharo-dev - lists.pharo.org

[Pharo-project] Pharo Kernel Reload Tests-Unix - Build # 67 - Unstable!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

April 18, 2012

Re: [Pharo-project] I need Pharo 1.4 for PowerPC

by Hilaire Fernandes

Le 17/04/2012 23:56, Edgar J. De Cleene a Ã©crit : > Found, install and try. > Unluck with all images > When COGDroid starts it asks for the image to use. If the image is in /mnt/sdcard it will propose you to start with it. I think there are instructions in the CogDroid wiki. Also there are two COgDroid, x86 and Arm Hilaire

April 18, 2012

[Pharo-project] [update 1.4] #14434

by Marcus Denker

14434 ----- Issue 5622: PluggableListMorph: you can use an accessor to retrieve directly an item from the list http://code.google.com/p/pharo/issues/detail?id=5622 Issue 5623: Failing tests related to Condensing Changes http://code.google.com/p/pharo/issues/detail?id=5623 -- Marcus Denker -- http://marcusdenker.de

April 18, 2012

Re: [Pharo-project] Block with ^ examples ...

by Eliot Miranda

James, ^-return in a block attempts to return from the enclosing method activation (the home context), as if a return from the method has occurred. But errors and exceptions can occur. a) if the method has already been returned from the enclosing method context (the home context) will be specially marked (it will have a nil sender and a nil pc) and a cannotReturn: error should be invoked by sending cannotRetuern: with the result as its argument to the activation of the block which is trying to return. b) if the enclosing home context is not on the sender chain of the block activation (i.e. because the block is being evaluated in a different process, a so-called "sideways return") the implementation may choose (and IMO /should choose) to invoke a cannotReturn: error. c) if an unwind-protect is found between the block activation and the sender of the home context then a message invoking unwind-protect processing (implementation-dependent; in Squeak this is #aboutToReturn:through:) should be sent to the block activation, with at least the result as an argument, but typically with the result and the first unwind-protect activation as arguments. Further, if the return can occur without error, all activations must be marked as returned-from (so that other attempts to return from intervening acrtivations provoke cannotReturn: errors). In Squeak the following methods implement this in the simulation, but N.B. fail to prevent side-ways returns: MethodContext methods for accessing methodReturnContext "Answer the context from which an ^-return should return from." closureOrNil == nil ifTrue: [^self]. ^closureOrNil outerContext methodReturnContext ContextPart methods for instruction decoding methodReturnTop "Simulate the action of a 'return top of stack' bytecode. This corresponds to source expressions like '^something'." ^self return: self pop from: self methodReturnContext return: value from: aSender "For simulation. Roll back self to aSender and return value from it. Execute any unwind blocks on the way. ASSUMES aSender is a sender of self" | newTop ctxt | aSender isDead ifTrue: [ ^ self send: #cannotReturn: to: self with: {value} super: false]. newTop := aSender sender. ctxt := self findNextUnwindContextUpTo: newTop. ctxt ifNotNil: [ ^ self send: #aboutToReturn:through: to: self with: {value. ctxt} super: false]. self releaseTo: newTop. newTop ifNotNil: [newTop push: value]. ^ newTop To prevent side-ways returns return: value from: aSender needs to be modified to something like return: value from: aSender "For simulation. Roll back self to aSender and return value from it. Execute any unwind blocks on the way." | newTop | ((self hasSender: aSender) and: [aSender isDead not]) ifFalse: [^self send: #cannotReturn: to: self with: {value} super: false]. newTop := aSender sender. (self findNextUnwindContextUpTo: newTop) ifNotNil: [:ctxt| ^self send: #aboutToReturn:through: to: self with: {value. ctxt} super: false]. self releaseTo: newTop. newTop ifNotNil: [newTop push: value]. ^newTop HTH Eliot On Tue, Apr 17, 2012 at 3:56 PM, James Ladd <james_ladd(a)hotmail.com> wrote: > > If I understand what I have read from the blue book the following is > how a block with a return is handled: > > 1 - sampleMethod > 2 self doIt: [ ^ true ]. > 3 Transcript show: 'here'; cr. > > Line 1 defines the instance method 'sampleMethod' - using Redline syntax > of course. > Line 2 sends the keyword message doIt: to receiver with a block that > contains a '^' (return). > Line 3 outputs a message using the Transcript. > > When Line 2 is executed and the passed block is sent the message 'value' > then the > value true is returned from the method 'sampleMethod', and line 3 of > sampleMethod is > never executed. > > Correct? > > Rgs, James. > -- best, Eliot

April 18, 2012

Re: [Pharo-project] Block with ^ examples ...

by James Ladd

If I understand what I have read from the blue book the following is how a block with a return is handled: 1 - sampleMethod 2 self doIt: [ ^ true ].3 Transcript show: 'here'; cr. Line 1 defines the instance method 'sampleMethod' - using Redline syntax of course. Line 2 sends the keyword message doIt: to receiver with a block that contains a '^' (return). Line 3 outputs a message using the Transcript. When Line 2 is executed and the passed block is sent the message 'value' then the value true is returned from the method 'sampleMethod', and line 3 of sampleMethod is never executed. Correct? Rgs, James.

April 17, 2012

Re: [Pharo-project] I need Pharo 1.4 for PowerPC

by Edgar J. De Cleene

On 4/17/12 4:32 PM, "Hilaire Fernandes" <hilaire.fernandes(a)edu.ge.ch> wrote: > Le 17/04/2012 11:42, Edgar J. De Cleene a Ã©crit : >> Any ARM VM which I could try? >> Have a 7Â² Android named Â³LittleAsimovÂ² now and canÂ¹t wait to have Pharo >> into. > > > Try CogDoid > > Hilaire > > > -- > Dr. Geo -- http://www.drgeo.eu Found, install and try. Unluck with all images Edgar

April 17, 2012

[Pharo-project] Why Every Ruby Developer Should Learn Smalltalk | Level Up! Victor Savkin's Blog About Programming

by Sven Van Caekenberghe

As currently on http://news.ycombinator.com (those who can, vote up please) http://victorsavkin.com/post/16375110741/why-smalltalk Yes! Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

April 17, 2012

Re: [Pharo-project] I need Pharo 1.4 for PowerPC

by edgar de cleene Android

very thanks Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: >Le 17/04/2012 11:42, Edgar J. De Cleene a Ã©crit : >> Any ARM VM which I could try? >> Have a 7â Android named âLittleAsimovâ now and canât wait to have Pharo >> into. > > >Try CogDoid > >Hilaire > > >-- >Dr. Geo -- http://www.drgeo.eu > >

April 17, 2012

Re: [Pharo-project] How to globals that are NOT classes or traits?

by Frank Shearar

On 17 April 2012 18:52, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Tue, Apr 17, 2012 at 10:11 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> I think that we missing a way to determine to which package some >> global belongs to. >> When you loading a package it can declare new global, but there is no >> reflective mechanisms in system to tell, to which package it belongs. >> If we could have that, then clearly, if you serialize the package, you >> would want to serialize its globals as well, >> and if not, you can just leave a reference to it, which will be >> rewired at materialization. > > > +1. Â Some construct that defines a module, analogous to a class definition? +1. I haven't had a chance to look yet, but it's possible Michael van der Gulik's SecureSqueak does this already, or has taken steps towards doing it: * http://securesqueak.blogspot.co.uk/2011/05/now-where-was-i.html * http://gulik.pbworks.com/ * http://gulik.pbworks.com/SecureSqueak Michael's said he'd need to cut a new release if I (we) wanted to make use of it. frank >> On 17 April 2012 18:20, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: >> > >> > >> > On Tue, Apr 17, 2012 at 3:50 AM, Mariano Martinez Peck >> > <marianopeck(a)gmail.com> wrote: >> >> >> >> Hi guys. In Fuel, we need to identity which globals present in >> >> Smalltalk >> >> globals are NOT classes or traits, because we need to manage them as >> >> globals. So far we have a hardcoded list: >> >> >> >> defaultGlobalSymbols >> >> >> >> Â Â Â ^ #(#Smalltalk #SourceFiles #Transcript #Undeclared #Display >> >> #TextConstants #ActiveWorld #ActiveHand #ActiveEvent #Sensor #Processor >> >> #ImageImports #SystemOrganization #World) >> >> >> >> So...as every hardcoded stuff, this is not nice because as soon as >> >> globals >> >> change, we need to fix this. So it would be nice if the system (pharo) >> >> can >> >> provide us this information. >> >> >> >> What do you think? >> > >> > >> > What I think is that the set of globals depends on usage. Â Some time I >> > might >> > actually want to serialize the SourceFiles Array, sometimes I might not >> > want >> > to. Â So this should be configurable, with a sensible default. Â Just as >> > when >> > one serializes a set of classes, references to classes outside the set >> > are >> > not serialized, serializing some subset of global objects in Smalltalk >> > should serialize those objects, not references. Â So design some >> > convenient >> > API that allows one to specify which objects are not globals, and have >> > the >> > default be e.g. all global objects in Smalltalk. >> > >> >> >> >> >> >> >> >> -- >> >> Mariano >> >> http://marianopeck.wordpress.com >> >> >> > >> > >> > >> > -- >> > best, >> > Eliot >> > >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > best, > Eliot >

April 17, 2012

Re: [Pharo-project] I need Pharo 1.4 for PowerPC

by Hilaire Fernandes

Le 17/04/2012 11:42, Edgar J. De Cleene a Ã©crit : > Any ARM VM which I could try? > Have a 7â Android named âLittleAsimovâ now and canât wait to have Pharo > into. Try CogDoid Hilaire -- Dr. Geo -- http://www.drgeo.eu

April 17, 2012