- Pharo-dev - lists.pharo.org

[Pharo-project] pharo-2.0-tests Â» 32,linux - Build # 308 - Failure!

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

Aug. 21, 2012

[Pharo-project] [update 2.0] #20262

by Marcus Denker

20262 ----- Issue 6585: Fuel has ref to non-existing FLPackageLoader http://code.google.com/p/pharo/issues/detail?id=6585 Issue 6582: ComposableModel >> #instantiateModels: is broken http://code.google.com/p/pharo/issues/detail?id=6582 -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

[Pharo-project] [update 2.0] #20261

by Marcus Denker

20261 ----- Issue 6587: FileSystem API Improvement http://code.google.com/p/pharo/issues/detail?id=6587 -- Marcus Denker -- http://marcusdenker.de

Aug. 21, 2012

Re: [Pharo-project] Trait conflicts wtf?

by StÃ©phane Ducasse

Mariano Mail communication is difficult and takes much more energy than face to face. I do not have this energy now and answer a good answer, so we can talk at esug or via chat (voice) no text for me. What I remember is that there is a problem in the trait implementation but I do not remember it. Damien C. should know it. Stef > We forgot to say that the motivation of this is that if we throw an error or take an assumption on how to resolve the conflict, plus some other changes we already done, we should be able to NOT use the Compiler at all when installing traits. The only place where we would still need the Compiler is when using Alias, but so far we have only ONE user in the image and it is TPureBehavior. Meaning that with this changes, in the 99.99% of the cases (it only uses Compiler when importing Traits with aliases) we can have kernels and boostraped images that can grow (even with traits) without the compiler. > Anyway, besides this "benefit", we didn't like that it silently fails and creates a method saying "self traitConflict". > Maybe we are not saying something.... > > Cheers, > > On Mon, Aug 20, 2012 at 4:48 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > On Mon, Aug 20, 2012 at 4:46 PM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > Trait named: #TA > uses: {} > category: 'ABC' > > Trait named: #TB > uses: {} > category: 'ABC' > > > TA>>a > ^10 > > TB>>a > ^10 > > Object subclass: #A > uses: TA + TB > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'ABC' > > ==> > > A>>a > ^self traitConflict > > > ? > > Why not an exception from a conflictive composition? This is to Mariano me a silent failure :/ > > > Or assume a resolution (like when selectors of classes have precedence over trait methods) > > > Guille > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Aug. 21, 2012

Re: [Pharo-project] we lost the StopTheWorld status in the issue tracker?

by Mariano Martinez Peck

On Tue, Aug 21, 2012 at 3:21 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > Mariano Martinez Peck wrote > > > > I want to mark this: > http://code.google.com/p/pharo/issues/detail?id=6588 > > > > Found and issue updated (it's called HorribleErrorBlockingEverything, and > is > the first status in the dropdown list). > > grrr sorry, I was searching in "label", not "status". Thanks Sean. > Cheers, > Sean > > > > -- > View this message in context: > http://forum.world.st/we-lost-the-StopTheWorld-status-in-the-issue-tracker-… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Aug. 21, 2012

Re: [Pharo-project] Roassal screencast available

by Chris Muller

Really nice. Excellent work! On Mon, Aug 20, 2012 at 4:50 PM, Vanessa PeÃ±a Araya <van.c.pena(a)gmail.com> wrote: > Hello everyone! > > We just wanted to share Roassal screencast: > > https://vimeo.com/47616600 > > For more information, please visit: http://objectprofile.com/ > > Check it out! > > Cheers, > Vanessa.

Aug. 21, 2012

Re: [Pharo-project] we lost the StopTheWorld status in the issue tracker?

by Sean P. DeNigris

Mariano Martinez Peck wrote > > I want to mark this: http://code.google.com/p/pharo/issues/detail?id=6588 > Found and issue updated (it's called HorribleErrorBlockingEverything, and is the first status in the dropdown list). Cheers, Sean -- View this message in context: http://forum.world.st/we-lost-the-StopTheWorld-status-in-the-issue-tracker-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 21, 2012

[Pharo-project] Roassal screencast available

by Vanessa PeÃ±a Araya

Hello everyone! We just wanted to share Roassal screencast: https://vimeo.com/47616600 For more information, please visit: http://objectprofile.com/ Check it out! Cheers, Vanessa.

Aug. 20, 2012

[Pharo-project] we lost the StopTheWorld status in the issue tracker?

by Mariano Martinez Peck

I want to mark this: http://code.google.com/p/pharo/issues/detail?id=6588 but I cannot find the status...did we loose it? thanks, -- Mariano http://marianopeck.wordpress.com

Aug. 20, 2012

Re: [Pharo-project] Trait conflicts wtf?

by Mariano Martinez Peck

We forgot to say that the motivation of this is that if we throw an error or take an assumption on how to resolve the conflict, plus some other changes we already done, we should be able to NOT use the Compiler at all when installing traits. The only place where we would still need the Compiler is when using Alias, but so far we have only ONE user in the image and it is TPureBehavior. Meaning that with this changes, in the 99.99% of the cases (it only uses Compiler when importing Traits with aliases) we can have kernels and boostraped images that can grow (even with traits) without the compiler. Anyway, besides this "benefit", we didn't like that it silently fails and creates a method saying "self traitConflict". Maybe we are not saying something.... Cheers, On Mon, Aug 20, 2012 at 4:48 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Mon, Aug 20, 2012 at 4:46 PM, Guillermo Polito < > guillermopolito(a)gmail.com> wrote: > >> Trait named: #TA >> uses: {} >> category: 'ABC' >> >> Trait named: #TB >> uses: {} >> category: 'ABC' >> >> >> TA>>a >> ^10 >> >> TB>>a >> ^10 >> >> Object subclass: #A >> uses: TA + TB >> instanceVariableNames: '' >> classVariableNames: '' >> poolDictionaries: '' >> category: 'ABC' >> >> ==> >> >> A>>a >> ^self traitConflict >> >> >> ? >> >> Why not an exception from a conflictive composition? This is to Mariano >> me a silent failure :/ >> >> > Or assume a resolution (like when selectors of classes have precedence > over trait methods) > > > >> Guille >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > -- Mariano http://marianopeck.wordpress.com

Aug. 20, 2012