February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] fast #becomeForward: crashes without PharoV10.sources

by Esteban Lorenzano

he is talking about some chrashes that happens fast, when you do become :) nothing about "fast become" On Feb 25, 2013, at 10:26 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > mmm what do you mean by "fast becomeForward:" ? > > On Mon, Feb 25, 2013 at 1:01 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > While setting up the new multi platform VM tests I saw that the tests fail extremely quickly > when there are not PharoV10.sources available. > > It is still our know #becomeForward: but on CompiledMethods, but I just want to share that. > > > > -- > Mariano > http://marianopeck.wordpress.com

Feb. 25, 2013

Re: [Pharo-project] [update 2.0] #20569

by Esteban Lorenzano

On Feb 25, 2013, at 10:01 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Mon, Feb 25, 2013 at 5:23 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Feb 25, 2013, at 2:18 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > Why doesn't it work in CogVM? > > because we become: methods when installing a new trailer and cog does not support > become: on active methods. > > It does now. I fixed this last week. no, it still does not works completely... but now it has a clear message and exit, instead a crash :) > > > Is condenseChanges ok now too? > > > I personally think we should not care. In 3.0 we really need get rid of this overly horrible > .sources and .changes monster for something trivially simplistic. > > We saved *a lot* on our Moore's Bank account the last yearsâ¦ at some point it is time > to invest that. Keep in mind that available RAM will double again until we release 3.0â¦ > > Marcus > > > > > > -- > best, > Eliot

Feb. 25, 2013

Re: [Pharo-project] please test 2.0

by Yanni Chiu

On 25/02/13 4:25 PM, Martin Dias wrote: > > What version was you loading? Fuel-MartinDias.685 which corresponds to version 1.8 > (actually, the code that has been integrated should be the definitive > one for Fuel 1.9, but the configuration still needs a revision for old > Pharos) Would it be easy to unload Fuel 1.9 from Pharo-2.0, and load Fuel 1.8 instead? > Tell me if I can help with the migration. I previously migrated from Fuel-MartinDias.259.mcz (which was something between version 1.4 and 1.5 of Fuel). It just takes time to set up the scripts and test the results.

Feb. 25, 2013

Re: [Pharo-project] Adding an entry to the World menu to clear all breakpoints

by phil＠highoctane.be

http://code.google.com/p/pharo/issues/detail?id=7598 2013/2/25 Sean P. DeNigris <sean(a)clipperadams.com>: > Cool idea... will you open an issue please ;) > > > > -- > View this message in context: http://forum.world.st/Adding-an-entry-to-the-World-menu-to-clear-all-breakp… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Feb. 25, 2013

Re: [Pharo-project] fast #becomeForward: crashes without PharoV10.sources

by Mariano Martinez Peck

mmm what do you mean by "fast becomeForward:" ? On Mon, Feb 25, 2013 at 1:01 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > While setting up the new multi platform VM tests I saw that the tests fail > extremely quickly > when there are not PharoV10.sources available. > > It is still our know #becomeForward: but on CompiledMethods, but I just > want to share that. > -- Mariano http://marianopeck.wordpress.com

Feb. 25, 2013

Re: [Pharo-project] please test 2.0

by Martin Dias

Hi Yanni, > I just had to change my build script to stop loading an older version of > Fuel on top of the version already present in Pharo-2.0. After some quick > manual testing, things look good. What version was you loading? > But, the newer Fuel version means I have to migrate Fuel versions again, > which is not something I expected to have to do. Hmmm, will have to back > away from moving to 2.0, for now. The code of Fuel that was integrated today is the same as installing with: Gofer it squeaksource3: 'Fuel'; package: 'ConfigurationOfFuel'; load. (ConfigurationOfFuel project version: '1.9') load. (actually, the code that has been integrated should be the definitive one for Fuel 1.9, but the configuration still needs a revision for old Pharos) Tell me if I can help with the migration. Martin

Feb. 25, 2013

Re: [Pharo-project] [update 2.0] #20569

by Eliot Miranda

On Mon, Feb 25, 2013 at 5:23 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Feb 25, 2013, at 2:18 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > Why doesn't it work in CogVM? > > because we become: methods when installing a new trailer and cog does not > support > become: on active methods. It does now. I fixed this last week. > > Is condenseChanges ok now too? > > > I personally think we should not care. In 3.0 we really need get rid of > this overly horrible > .sources and .changes monster for something trivially simplistic. > > We saved *a lot* on our Moore's Bank account the last yearsâ¦ at some point > it is time > to invest that. Keep in mind that available RAM will double again until we > release 3.0â¦ > > Marcus > > > -- best, Eliot

Feb. 25, 2013

Re: [Pharo-project] Adding an entry to the World menu to clear all breakpoints

by Sean P. DeNigris

Cool idea... will you open an issue please ;) -- View this message in context: http://forum.world.st/Adding-an-entry-to-the-World-menu-to-clear-all-breakp… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 25, 2013

[Pharo-project] Adding an entry to the World menu to clear all breakpoints

by phil＠highoctane.be

Just a little menu entry with: BreakpointManager clear Something that would list them all and clear the ones that are to be removed would be nice as well. (Yeah, 3.0, I know). Phil

Feb. 25, 2013

Re: [Pharo-project] Metacello issues on Pharo 2.0

by Dale Henrichs

I think that the suspendAllWhile: call is important because a) some Metacello tests are sensitive to packages getting marked dirty or other events getting triggered ... ----- Original Message ----- | From: "Christophe Demarey" <Christophe.Demarey(a)inria.fr> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Thursday, February 21, 2013 1:26:31 AM | Subject: Re: [Pharo-project] Metacello issues on Pharo 2.0 | | Dale | | we run the tests simply rewriting runCase as | | runCase | | original | | (self doSilently) ifFalse: [ ^super runCase ]. | original := MetacelloPlatform current bypassGoferLoadUpdateCategories. | [ | MetacelloPlatform current bypassGoferLoadUpdateCategories: true. | ^ SystemAnnouncer uniqueInstance suspendAllWhile: [ super runCase ] | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories: | original ] | | but it seems that we do not have the same behavior between the two | | runCase | | original | | (self doSilently) ifFalse: [ ^super runCase ]. | original := MetacelloPlatform current bypassGoferLoadUpdateCategories. | [ | MetacelloPlatform current bypassGoferLoadUpdateCategories: true. | ^ super runCase ] | ensure: [ MetacelloPlatform current bypassGoferLoadUpdateCategories: | original ] | | So we will run all the tests | | Stef

Feb. 25, 2013