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

Re: [Pharo-project] Issue with gofer/metacello

by StÃ©phane Ducasse

argh! lukas is it possible to lower the pain of dale? Stef On Dec 27, 2009, at 10:27 PM, Dale Henrichs wrote: > The latest Gofer API is not backward compatible with the earlier versions of the Gofer API. This means that I need to have different versions of Metacello to use with the different versions of Gofer. Unfortunately, I can't use Gofer to detect which version of Gofer is loaded because of the API changes. So I will have to write more code than I'd like to detect which version of Gofer is pre-installed. The API changes also impact the bootstrapping code. > > Solving these problems are a larger project than I can undertake on a Sunday and I _am_ on vacation the coming week as well. > > So until further notice, if you want to use Metacello 1.0-beta.17 (or earlier) in Pharo you will have to manually ensure Gofer-lr.83 (or earlier) is loaded into your image before attempting to load any Metacello configurations. I'm not sure that you use Gofer to load an earlier version of itself (I'll be finding out in the next few days)... > > Metacello 1.0-beta.18 works with Gofer-lr.107 (in pharo 1.0-10502). If you want to use Metacello 1.0-beta.18 (currently in development, so it's subject to change). You will have to manually bootstrap Metacello by executing: > > Gofer new > gemsource: 'metacello'; > package: 'ConfigurationOfMetacello'; > load. > (Smalltalk at: #ConfigurationOfMetacello) perform: #ensureMetacello18. > ((Smalltalk at: #ConfigurationOfMetacello) project version: '1.0-beta.18') load: 'ALL'. > > before loading your configuration. > > I won't release 1.0-beta.18 until I've resolved the bootstrapping problem. I'm pretty sure that there is a technical solution, but it will take several days for me to get it implemented. > > Dale > > ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: > > | Version 1.0-beta.18 (development) should have fixes for the latest > | Gofer. 1.0-beta.18 is currently in #development so it is automatically > | loaded. When I get the chance to test the Metacello fixes with 10502, > | I'll #release 1.0-beta.18 (and will be automatically loaded). > | > | Dale > | ----- "Alexandre Bergel" <alexandre(a)bergel.eu> wrote: > | > | | Hi Lukas, > | | > | | In a fresh 10502 I evaluated: > | | -=-=-=-=-=-=-=-=-= > | | [ Gofer gofer load ] > | | on: Error > | | do: [ :err | err retry ]. > | | Gofer gofer recompile. > | | Gofer new > | | squeaksource: 'Mondrian'; > | | addPackage: 'ConfigurationOfMondrian'; > | | load. > | | (Smalltalk at: #ConfigurationOfMondrian) perform: #loadLastStable. > | | -=-=-=-=-=-=-=-=-= > | | > | | I have the same error. > | | The error comes from: > | | > | | -=-=-=-=-=-=-=-=-= > | | MetacelloMCProject>>updateProject > | | "load the latest version of the configuration package" > | | > | | | mcLoader | > | | (mcLoader := self loader) == nil > | | ifTrue: [ mcLoader := self project loaderClass on: nil ]. > | | mcLoader doingLoads: [ > | | | gofer | > | | gofer := Gofer new. > | | MCWorkingCopy > | | managersForClass: self configuration class > | | do: [:mgr | > | | gofer add: (GoferPackageReference name: mgr packageName > | | repository: mgr repositoryGroup) versionReference. > | | Transcript cr; show: 'Loading -> ', mgr packageName, ' <-' ]. > | | gofer load ]. > | | ^true > | | -=-=-=-=-=-=-=-=-= > | | > | | Cheers, > | | Alexandre > | | > | | On 27 Dec 2009, at 17:27, Lukas Renggli wrote: > | | > | | >> After proceeding these warnings, I have a rollback: MNU > | | >> GoferPackageReference class>>name:repository: > | | > > | | > Can you evaluate > | | > > | | > [ Gofer gofer load ] > | | > on: Error > | | > do: [ :err | err retry ]. > | | > Gofer gofer recompile. > | | > > | | > ? I don't have any senders of #name:repository: to > | | > GoferPackageReference. > | | > > | | > Lukas > | | > > | | > -- > | | > Lukas Renggli > | | > http://www.lukas-renggli.ch > | | > > | | > _______________________________________________ > | | > Pharo-project mailing list > | | > Pharo-project(a)lists.gforge.inria.fr > | | > > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > | | > > | | > | | -- > | | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > | | Alexandre Bergel http://www.bergel.eu > | | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > | | > | | > | | > | | > | | > | | > | | _______________________________________________ > | | 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 27, 2009

Re: [Pharo-project] Feedback on issue 1703

by StÃ©phane Ducasse

Issue 1703: Closing last windows raise error 1 person starred this issue and may be notified of changes. Back to list Status: Closed Owner: marianopeck Closed: Today Cc: mike.rueger Milestone-1.1 Add a comment andmake changes below Reported by marianopeck, Today (4 hours ago) Pharo image: PharoCore Pharo core version: v Virtual machine used: Squeak 4.2.2beta1U.app Steps to reproduce: 1. Open several windows (whatever) 2. Close all of them 3. Press cmd + w (like trying to close another window). You will get the attached error. The problem is that the message closeTopWindow is being sent to SystemWindow and this is not impelented. I look in older version and it is like this: SystemWindow class >> closeTopWindow "Try to close the top window. It may of course decline" TopWindow ifNotNil: [TopWindow delete] So, adding this method the error is dissappear, but: 1) It even works creating the message doing nothing 2) I think this is not the correct fix. The real fix should do some ifEmpty: don't send the message closeTopWindow or something like that. 3) I don't understand why the closing of OTHERS windows than the last one, use another message then closeTopWindow

Dec. 27, 2009

Re: [Pharo-project] moose collection extensions

by StÃ©phane Ducasse

On Dec 27, 2009, at 9:32 PM, Nicolas Cellier wrote: > 2009/12/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Adrian I imagine that we clarified some of the flatCollectAsSet:.. >> I do not remember but we moved method names around because they were not fitting well. >> Now for shuffle I do not know if we used them and I would remove it. >> >> Stef >> > > flatCollectAsSet: ? > I wonder if you should not rather provide a flatCollect:as: like > Levente did to the simple collect: Probably. Adrian K. (you see we put your name in the comments :)). Adrian I was wondering if we could have another / faster implementation that does not really on stream. Now I'm too tired to think. Stef > > Nicolas > >> On Dec 27, 2009, at 7:56 PM, Adrian Kuhn wrote: >> >>> StÃ©phane Ducasse <stephane.ducasse@...> writes: >>> >>>> here are the collection extensions we use in Moose. I copied them to >>>> PharoTaskForces so that we can discuss and tweak the code if wanted. >>> >>> Just missed #collectAsSet: and #groupedBy: yesterday :) Given that I have >>> written all of these extensions (except #copyEmpty: and #groupedBy: which are >>> provided by VW as far I recall) I am of course baised, but also pleased to >>> see them being used and possibly included in Pharo. >>> >>> There is also a #trasitiveClosure: extensions, which was ported by Oscar >>> already, see http://www.squeaksource.com/CodePhoo but with different >>> semantics than in the original Codefoo. >>> >>> An (incomplete) documentation of Codefoo can be found here >>> http://scg.unibe.ch/staff/adriankuhn/codefoo >>> >>> NB: #shuffle: does not produce all permutations with the same likelihood! It >>> should be changed. I can provide the correct implementation. Also then, >>> #shuffle: times should be removed. That is nonsense, a broken shuffle does >>> no get better the longer you shuffle :) >>> >>> cheers, >>> AA >>> >>> >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 27, 2009

Re: [Pharo-project] Happy new year in advance :)

by Schwab,Wilhelm K

Stef, Sometimes pushing doe not work, but getting out in front and pulling does - thanks for doing that! As for Smalltalk in quotes, I am a strong believer in never doing to the language what can readily be done with the language. That approach will lead me to advocate for new frameworks, editors and inspectors where new syntax might seem like the most direct approach. I look forward to a new year of debate on such topics, not to mention a couple of releases of Pharo! Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Sunday, December 27, 2009 4:35 AM To: Pharo-project(a)lists.gforge.inria.fr Development Subject: [Pharo-project] Happy new year in advance :) Hi guys I just want to thank you for your positive energy. We had a dream with marcus about a better Smalltalk and this is happening. This is cool. It was not easy but the community is moving - more than we would ever thought after all these years trying to push with less success. Our vision for pharo is described on the pharo web site :) http://www.pharo-project.org/about Now my personal challenge/vision is the following: - I want Pharo to be a cool vehicule for innovation. - I want Pharo to be a solid vehicule for companies to succeed making a living with "Smalltalk" --- I put "" because I would like to avoid to get bound until the end of my life with just a Smalltalk :) but I would love to see companies starting in France around Pharo if you are interested contact me :) Let us really invent the future building on the past. If you want to help, check the mailing-list - you can see our open-process: open and pragmatic communication, discussing and learning are key for us -- sorry for the volume of mails. Spread the word: Pharo is what we will make it to be. Don't always trust what others write between the lines on us. ;-D Check by yourself (drink a beer with us before) and study history - all is in there. Stef _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 27, 2009

Re: [Pharo-project] [Metacello] Re: Issue with gofer/metacello

by Dale Henrichs

Doru, I've seen that ... more changes to the gofer api were made after I did my initial port:( I'm writing an email to the pharo list covering the problem and will cc it here as well. Dale ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: | Hi Dale, | | I did, but there seems to be an error during the bootstrapping of the | | metacello in a new Pharo image. | | Cheers, | Doru | | | On 27 Dec 2009, at 20:06, Dale Henrichs wrote: | | > Doru, | > | > Have you tried 1.0-beta.18 with the "latest gofer"? | > | > Dale | > ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: | > | > | Hi, | > | | > | The problem is that Metacello is not quite working with the | latest | > | Gofer. | > | | > | Cheers, | > | Doru | > | | > | | > | On 27 Dec 2009, at 17:39, Alexandre Bergel wrote: | > | | > | > Hi Lukas, | > | > | > | > In a fresh 10502 I evaluated: | > | > -=-=-=-=-=-=-=-=-= | > | > [ Gofer gofer load ] | > | > on: Error | > | > do: [ :err | err retry ]. | > | > Gofer gofer recompile. | > | > Gofer new | > | > squeaksource: 'Mondrian'; | > | > addPackage: 'ConfigurationOfMondrian'; | > | > load. | > | > (Smalltalk at: #ConfigurationOfMondrian) perform: | #loadLastStable. | > | > -=-=-=-=-=-=-=-=-= | > | > | > | > I have the same error. | > | > The error comes from: | > | > | > | > -=-=-=-=-=-=-=-=-= | > | > MetacelloMCProject>>updateProject | > | > "load the latest version of the configuration package" | > | > | > | > | mcLoader | | > | > (mcLoader := self loader) == nil | > | > ifTrue: [ mcLoader := self project loaderClass on: nil ]. | > | > mcLoader doingLoads: [ | > | > | gofer | | > | > gofer := Gofer new. | > | > MCWorkingCopy | > | > managersForClass: self configuration class | > | > do: [:mgr | | > | > gofer add: (GoferPackageReference name: mgr packageName | > | > repository: mgr repositoryGroup) versionReference. | > | > Transcript cr; show: 'Loading -> ', mgr packageName, ' <-' | ]. | > | > gofer load ]. | > | > ^true | > | > -=-=-=-=-=-=-=-=-= | > | > | > | > Cheers, | > | > Alexandre | > | > | > | > On 27 Dec 2009, at 17:27, Lukas Renggli wrote: | > | > | > | >>> After proceeding these warnings, I have a rollback: MNU | > | >>> GoferPackageReference class>>name:repository: | > | >> | > | >> Can you evaluate | > | >> | > | >> [ Gofer gofer load ] | > | >> on: Error | > | >> do: [ :err | err retry ]. | > | >> Gofer gofer recompile. | > | >> | > | >> ? I don't have any senders of #name:repository: to | > | >> GoferPackageReference. | > | >> | > | >> Lukas | > | >> | > | >> -- | > | >> Lukas Renggli | > | >> http://www.lukas-renggli.ch | > | >> | > | >> _______________________________________________ | > | >> Pharo-project mailing list | > | >> Pharo-project(a)lists.gforge.inria.fr | > | >> | > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | > | >> | > | > | > | > -- | > | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | > | > Alexandre Bergel http://www.bergel.eu | > | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | > | > | > | > | > | > | > | > | > | > | > | > | > | > _______________________________________________ | > | > Pharo-project mailing list | > | > Pharo-project(a)lists.gforge.inria.fr | > | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- | > project | > | | > | -- | > | www.tudorgirba.com | > | | > | "From an abstract enough point of view, any two things are | similar." | | -- | www.tudorgirba.com | | "What is more important: To be happy, or to make happy?"

Dec. 27, 2009

Re: [Pharo-project] Issue with gofer/metacello

by Dale Henrichs

The latest Gofer API is not backward compatible with the earlier versions of the Gofer API. This means that I need to have different versions of Metacello to use with the different versions of Gofer. Unfortunately, I can't use Gofer to detect which version of Gofer is loaded because of the API changes. So I will have to write more code than I'd like to detect which version of Gofer is pre-installed. The API changes also impact the bootstrapping code. Solving these problems are a larger project than I can undertake on a Sunday and I _am_ on vacation the coming week as well. So until further notice, if you want to use Metacello 1.0-beta.17 (or earlier) in Pharo you will have to manually ensure Gofer-lr.83 (or earlier) is loaded into your image before attempting to load any Metacello configurations. I'm not sure that you use Gofer to load an earlier version of itself (I'll be finding out in the next few days)... Metacello 1.0-beta.18 works with Gofer-lr.107 (in pharo 1.0-10502). If you want to use Metacello 1.0-beta.18 (currently in development, so it's subject to change). You will have to manually bootstrap Metacello by executing: Gofer new gemsource: 'metacello'; package: 'ConfigurationOfMetacello'; load. (Smalltalk at: #ConfigurationOfMetacello) perform: #ensureMetacello18. ((Smalltalk at: #ConfigurationOfMetacello) project version: '1.0-beta.18') load: 'ALL'. before loading your configuration. I won't release 1.0-beta.18 until I've resolved the bootstrapping problem. I'm pretty sure that there is a technical solution, but it will take several days for me to get it implemented. Dale ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | Version 1.0-beta.18 (development) should have fixes for the latest | Gofer. 1.0-beta.18 is currently in #development so it is automatically | loaded. When I get the chance to test the Metacello fixes with 10502, | I'll #release 1.0-beta.18 (and will be automatically loaded). | | Dale | ----- "Alexandre Bergel" <alexandre(a)bergel.eu> wrote: | | | Hi Lukas, | | | | In a fresh 10502 I evaluated: | | -=-=-=-=-=-=-=-=-= | | [ Gofer gofer load ] | | on: Error | | do: [ :err | err retry ]. | | Gofer gofer recompile. | | Gofer new | | squeaksource: 'Mondrian'; | | addPackage: 'ConfigurationOfMondrian'; | | load. | | (Smalltalk at: #ConfigurationOfMondrian) perform: #loadLastStable. | | -=-=-=-=-=-=-=-=-= | | | | I have the same error. | | The error comes from: | | | | -=-=-=-=-=-=-=-=-= | | MetacelloMCProject>>updateProject | | "load the latest version of the configuration package" | | | | | mcLoader | | | (mcLoader := self loader) == nil | | ifTrue: [ mcLoader := self project loaderClass on: nil ]. | | mcLoader doingLoads: [ | | | gofer | | | gofer := Gofer new. | | MCWorkingCopy | | managersForClass: self configuration class | | do: [:mgr | | | gofer add: (GoferPackageReference name: mgr packageName | | repository: mgr repositoryGroup) versionReference. | | Transcript cr; show: 'Loading -> ', mgr packageName, ' <-' ]. | | gofer load ]. | | ^true | | -=-=-=-=-=-=-=-=-= | | | | Cheers, | | Alexandre | | | | On 27 Dec 2009, at 17:27, Lukas Renggli wrote: | | | | >> After proceeding these warnings, I have a rollback: MNU | | >> GoferPackageReference class>>name:repository: | | > | | > Can you evaluate | | > | | > [ Gofer gofer load ] | | > on: Error | | > do: [ :err | err retry ]. | | > Gofer gofer recompile. | | > | | > ? I don't have any senders of #name:repository: to | | > GoferPackageReference. | | > | | > Lukas | | > | | > -- | | > Lukas Renggli | | > http://www.lukas-renggli.ch | | > | | > _______________________________________________ | | > Pharo-project mailing list | | > Pharo-project(a)lists.gforge.inria.fr | | > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | > | | | | -- | | _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: | | Alexandre Bergel http://www.bergel.eu | | ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. | | | | | | | | | | | | | | _______________________________________________ | | 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

Dec. 27, 2009

[Pharo-project] Feedback on issue 1703

by Mariano Martinez Peck

Does someone has something to comment for http://code.google.com/p/pharo/issues/detail?id=1703 ? Thanks Mariano

Dec. 27, 2009

Re: [Pharo-project] moose collection extensions

by Nicolas Cellier

2009/12/27 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Adrian I imagine that we clarified some of the flatCollectAsSet:.. > I do not remember but we moved method names around because they were not fitting well. > Now for shuffle I do not know if we used them and I would remove it. > > Stef > flatCollectAsSet: ? I wonder if you should not rather provide a flatCollect:as: like Levente did to the simple collect: Nicolas > On Dec 27, 2009, at 7:56 PM, Adrian Kuhn wrote: > >> StÃ©phane Ducasse <stephane.ducasse@...> writes: >> >>> here are the collection extensions we use in Moose. I copied them to >>> PharoTaskForces so that we can discuss and tweak the code if wanted. >> >> Just missed #collectAsSet: and #groupedBy: yesterday :) Given that I have >> written all of these extensions (except #copyEmpty: and #groupedBy: which are >> provided by VW as far I recall) I am of course baised, but also pleased to >> see them being used and possibly included in Pharo. >> >> There is also a #trasitiveClosure: extensions, which was ported by Oscar >> already, see http://www.squeaksource.com/CodePhoo but with different >> semantics than in the original Codefoo. >> >> An (incomplete) documentation of Codefoo can be found here >> http://scg.unibe.ch/staff/adriankuhn/codefoo >> >> NB: #shuffle: does not produce all permutations with the same likelihood! It >> should be changed. I can provide the correct implementation. Also then, >> #shuffle: times should be removed. That is nonsense, a broken shuffle does >> no get better the longer you shuffle :) >> >> cheers, >> AA >> >> >> _______________________________________________ >> 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 >

Dec. 27, 2009

Re: [Pharo-project] [Metacello] Re: Issue with gofer/metacello

by Tudor Girba

Hi Dale, I did, but there seems to be an error during the bootstrapping of the metacello in a new Pharo image. Cheers, Doru On 27 Dec 2009, at 20:06, Dale Henrichs wrote: > Doru, > > Have you tried 1.0-beta.18 with the "latest gofer"? > > Dale > ----- "Tudor Girba" <tudor.girba(a)gmail.com> wrote: > > | Hi, > | > | The problem is that Metacello is not quite working with the latest > | Gofer. > | > | Cheers, > | Doru > | > | > | On 27 Dec 2009, at 17:39, Alexandre Bergel wrote: > | > | > Hi Lukas, > | > > | > In a fresh 10502 I evaluated: > | > -=-=-=-=-=-=-=-=-= > | > [ Gofer gofer load ] > | > on: Error > | > do: [ :err | err retry ]. > | > Gofer gofer recompile. > | > Gofer new > | > squeaksource: 'Mondrian'; > | > addPackage: 'ConfigurationOfMondrian'; > | > load. > | > (Smalltalk at: #ConfigurationOfMondrian) perform: #loadLastStable. > | > -=-=-=-=-=-=-=-=-= > | > > | > I have the same error. > | > The error comes from: > | > > | > -=-=-=-=-=-=-=-=-= > | > MetacelloMCProject>>updateProject > | > "load the latest version of the configuration package" > | > > | > | mcLoader | > | > (mcLoader := self loader) == nil > | > ifTrue: [ mcLoader := self project loaderClass on: nil ]. > | > mcLoader doingLoads: [ > | > | gofer | > | > gofer := Gofer new. > | > MCWorkingCopy > | > managersForClass: self configuration class > | > do: [:mgr | > | > gofer add: (GoferPackageReference name: mgr packageName > | > repository: mgr repositoryGroup) versionReference. > | > Transcript cr; show: 'Loading -> ', mgr packageName, ' <-' ]. > | > gofer load ]. > | > ^true > | > -=-=-=-=-=-=-=-=-= > | > > | > Cheers, > | > Alexandre > | > > | > On 27 Dec 2009, at 17:27, Lukas Renggli wrote: > | > > | >>> After proceeding these warnings, I have a rollback: MNU > | >>> GoferPackageReference class>>name:repository: > | >> > | >> Can you evaluate > | >> > | >> [ Gofer gofer load ] > | >> on: Error > | >> do: [ :err | err retry ]. > | >> Gofer gofer recompile. > | >> > | >> ? I don't have any senders of #name:repository: to > | >> GoferPackageReference. > | >> > | >> Lukas > | >> > | >> -- > | >> Lukas Renggli > | >> http://www.lukas-renggli.ch > | >> > | >> _______________________________________________ > | >> Pharo-project mailing list > | >> Pharo-project(a)lists.gforge.inria.fr > | >> > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > | >> > | > > | > -- > | > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > | > Alexandre Bergel http://www.bergel.eu > | > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > | > > | > > | > > | > > | > > | > > | > _______________________________________________ > | > Pharo-project mailing list > | > Pharo-project(a)lists.gforge.inria.fr > | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- > project > | > | -- > | www.tudorgirba.com > | > | "From an abstract enough point of view, any two things are similar." -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Dec. 27, 2009

Re: [Pharo-project] Fwd: 2GB changes file and a pony (was: [squeak-dev] ALL CLEAR (Re: CompiledMethodTrailers ready for use))

by StÃ©phane Ducasse

Thanks David. I will look at the methodTrailer fixes soon. Now my knowledge is limited in this area and I would prefer to have marcus have a look. I will at least check the code and see if it looks ok. Stef On Dec 27, 2009, at 8:25 PM, David T. Lewis wrote: > Note, the change sets for this update are also on Mantis > http://bugs.squeak.org/view.php?id=5205 > along with discussion of other approaches to the problem. > > These changes are now in Squeak trunk. > > Dave > > On Sun, Dec 27, 2009 at 09:19:46PM +0200, Igor Stasenko wrote: >> ---------- Forwarded message ---------- >> From: David T. Lewis <lewis(a)mail.msen.com> >> Date: 2009/12/27 >> Subject: Re: 2GB changes file and a pony (was: [squeak-dev] ALL CLEAR >> (Re: CompiledMethodTrailers ready for use)) >> To: The general-purpose Squeak developers list >> <squeak-dev(a)lists.squeakfoundation.org> >> >> >> I have put the updates for large changes and sources files into the >> inbox. I would appreciate if someone can review this before moving >> into trunk. >> >> There are three mcz updates: >> ??Files-dtl.62 >> ??System-dtl.205 >> ??Kernel-dtl.347 >> >> Important: The changes *must* be loaded in the order listed above. >> This will require a configuration map update when the changes are >> moved to trunk. >> >> The use of ExpandedSourceFileArray takes effect after the first >> image restart. To change back to using the StandardSourceFileArray, >> the procedure is as follows: >> >> ??1) Evaluate 'StandardSourceFileArray install' >> ??2) Edit SourceFileArray class>>concreteClass to answer >> ?? ??StandardSourceFileArray rather than ExpandedSourceFileArray. >> >> Thanks, >> Dave >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> 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

Dec. 27, 2009