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

Re: [Pharo-project] Alien bug fix

by StÃ©phane Ducasse

Thanks eliot BTW what is the future of alien compared to FFI. I'm still confused. Stef (finished to paint house - well nearly finished before running to ESUG). On Aug 18, 2011, at 7:37 PM, Eliot Miranda wrote: > Hi All, > > I've just published Alien-eem.14 to http://www.squeaksource.com/Alien. This fix needs to be integrated into each dialect's version of Alien. The bug causes VM crashes due to trying to free stale pointers from previous runs. > > Alien-eem.14 > Author: eem > Time: 18 August 2011, 10:34:20.024 am > UUID: 39bedad1-6159-4ba4-be35-277df2a25977 > Ancestors: Alien-eem.13 > > Fix startUp: discarding of stale values from Alien's GCMallocedAliens class var. > > -- > best, > Eliot >

Aug. 18, 2011

[Pharo-project] Alien bug fix

by Eliot Miranda

Hi All, I've just published Alien-eem.14 to http://www.squeaksource.com/Alien. This fix needs to be integrated into each dialect's version of Alien. The bug causes VM crashes due to trying to free stale pointers from previous runs. Alien-eem.14 Author: eem Time: 18 August 2011, 10:34:20.024 am UUID: 39bedad1-6159-4ba4-be35-277df2a25977 Ancestors: Alien-eem.13 Fix startUp: discarding of stale values from Alien's GCMallocedAliens class var. -- best, Eliot

Aug. 18, 2011

Re: [Pharo-project] Typo in Pragma class comment

by Marcus Denker

On Aug 18, 2011, at 11:26 AM, Dennis Schetinin wrote: > Look for "browsse". > > Sorry, if this is incorrect place to report this kind of things. > > The best is always to add a tracker entry like this: http://code.google.com/p/pharo/issues/list?thanks=4659 This way it will just be fixed with the next update.. -- Marcus Denker -- http://marcusdenker.de

Aug. 18, 2011

Re: [Pharo-project] Typo in Pragma class comment

by StÃ©phane Ducasse

no this is the right place We love bug reports and please create a bug entry :) Stef On Aug 18, 2011, at 11:25 AM, Dennis Schetinin wrote: > Look for "browsse". > > Sorry, if this is incorrect place to report this kind of things. > > -- > Dennis Schetinin

Aug. 18, 2011

[Pharo-project] [update 1.4] #14094

by StÃ©phane Ducasse

14094 ----- - Issue 4649: Limit the use of Smalltalk getSystemAttribute:. Thanks Camillo Bruni and Igor Stasenko for the first draft :) Igor we fixed some problems with imagePath and friends as well as some problem with OSPlatform referencing to Smalltalk deprecated methods :) Stef

Aug. 18, 2011

[Pharo-project] Typo in Pragma class comment

by Dennis Schetinin

Look for "browsse". Sorry, if this is incorrect place to report this kind of things. -- Dennis Schetinin

Aug. 18, 2011

Re: [Pharo-project] [Pharo-fuel] Two nice things I did in 2 hours with Fuel

by Mariano Martinez Peck

On Thu, Aug 18, 2011 at 8:40 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Aug 18, 2011, at 1:16 AM, Craig Latta wrote: > > > > >> Do I hear "remote tools" ? > > > > How would that work, exactly? Wouldn't you want to keep the > > contexts where they are, and interact with them with remote messages? > > Otherwise, it seems like differences between the two object memories > > would cause trouble eventually. > > > Yes. For remote tools one wants to do it differently... > Mariano's experiment was just meant as a Demo to show Fuel serialization. > > Exactly. The same as the example with Riak. I am not saying that Fuel is able to do remove tools nor to be an excellent persistence solution. What I am DO saying is that with Fuel we want to be able to serialize whatever, contexts, closures, etc. And that allows further experiments and work. Fuel only takes care about the serialization infrastructure ;) With Riak all I wanted to show is that it is really easy to take a graph, serialize it with Fuel and store/retrieve it from a NoSQL database. > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > > -- Mariano http://marianopeck.wordpress.com

Aug. 18, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Henrik Johansen

On Aug 18, 2011, at 8:52 44AM, Philippe Marschall wrote: > On 17.08.2011 22:57, Henrik Sperre Johansen wrote: >> On 17.08.2011 22:29, Philippe Marschall wrote: >>> On 17.08.2011 22:17, StÃ©phane Ducasse wrote: >>>> I wrote >>>> >>>> >>>> cull: anArg >>>> "Execute the receiver with one or zero argument. >>>> >>>> [ 1 + 2 ] cull: 5 >>>> returns 3 >>>> [ :x | 1+ 2 + x] cull: 5 >>>> returns 8 >>>> " >>>> ^numArgs = 0 >>>> ifTrue: [self value] >>>> ifFalse: [self value: anArg] >>>> >>> >>> So it's like #valueWithPossibleArgument:? >> Almost. >> cull: raises error if given blocks with too many args, >> valueWithPossibleArgument(s): evaluates with the extra args as nil. >>> Why do we need two methods >>> that do the same thing? >> Because valueWithPossibleArguments was there first, and we can't simply >> remove it. >> cull is more natural to use in 99.9% of the cases. >> >> Also, #cull: protocol only goes up to 4 arguments, mirroring #value: >> (#cullWithArguments: not being present is mostly an oversight though... ) > > So we #valueWithPossibleArgument:? > > Cheers > Philippe #valueWithPossibleArgument: / #valueWithPossibleArgs: / #valueWithEnoughArguments: all execute the block with nil args if passed too few. #cull:'s raise an error. Other than that, they are equivalent from a users POV, yes. Cheers, Henry

Aug. 18, 2011

Re: [Pharo-project] what are the comments of cull: cull: cull:cull: and friends?

by Philippe Marschall

On 17.08.2011 22:57, Henrik Sperre Johansen wrote: > On 17.08.2011 22:29, Philippe Marschall wrote: >> On 17.08.2011 22:17, StÃ©phane Ducasse wrote: >>> I wrote >>> >>> >>> cull: anArg >>> "Execute the receiver with one or zero argument. >>> >>> [ 1 + 2 ] cull: 5 >>> returns 3 >>> [ :x | 1+ 2 + x] cull: 5 >>> returns 8 >>> " >>> ^numArgs = 0 >>> ifTrue: [self value] >>> ifFalse: [self value: anArg] >>> >> >> So it's like #valueWithPossibleArgument:? > Almost. > cull: raises error if given blocks with too many args, > valueWithPossibleArgument(s): evaluates with the extra args as nil. >> Why do we need two methods >> that do the same thing? > Because valueWithPossibleArguments was there first, and we can't simply > remove it. > cull is more natural to use in 99.9% of the cases. > > Also, #cull: protocol only goes up to 4 arguments, mirroring #value: > (#cullWithArguments: not being present is mostly an oversight though... ) So we #valueWithPossibleArgument:? Cheers Philippe

Aug. 18, 2011

Re: [Pharo-project] [Pharo-fuel] Two nice things I did in 2 hours with Fuel

by Marcus Denker

On Aug 18, 2011, at 1:16 AM, Craig Latta wrote: > >> Do I hear "remote tools" ? > > How would that work, exactly? Wouldn't you want to keep the > contexts where they are, and interact with them with remote messages? > Otherwise, it seems like differences between the two object memories > would cause trouble eventually. > Yes. For remote tools one wants to do it differently... Mariano's experiment was just meant as a Demo to show Fuel serialization. Marcus -- Marcus Denker -- http://marcusdenker.de

Aug. 18, 2011