October 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Metacello bleedingEdge question

by phil＠highoctane.be

Hey, don't. I found it very helpful. I read it thrice actually. Still do find Configurations confusing though. 2012/10/1 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > OK > so we should not talk about it anymore and ban it from all the > configurations. > It would be good to have specific rules for configurations. > > BTW: what do we do with the chapter I'm working on the new book and now > I'm puzzled > because I have invested a large amount of time and I get a chapter that > you never gave feedback on and > that is probably not correct or up to date. So may be the only thing I can > do is to drop it. > And after people will tell that pharo does not have documentation but I > often fell alone. > > Stef > > > #latestVersion actually has a very good reason for existing, just not > for use by end users in loading code ... > > > > It _has_ been dropped from the _convention_, and it shouldn't be dropped > from the code base... > > > > Dale > > > > ----- Original Message ----- > > | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > > | To: Pharo-project(a)lists.gforge.inria.fr > > | Sent: Saturday, September 29, 2012 1:02:17 PM > > | Subject: Re: [Pharo-project] Metacello bleedingEdge question > > | > > | > > | On 29 Sep 2012, at 21:38, StÃ©phane Ducasse > > | <stephane.ducasse(a)inria.fr> wrote: > > | > > | > On Sep 29, 2012, at 5:39 PM, Dale Henrichs wrote: > > | > > > | >> Stef, > > | >> > > | >> #latestVersion is there for backward compatibility. > > | > > > | > Ok > > | > I would simply remove it. > > | > > > | > Stef > > | > > | I was about to say: what's that 'backward compatibility' ? > > | > > | ;-) > > | > > | No seriously, unless there is a very good, important reason to keep > > | it, confusing stuff should be removed going forward. > > | > > | Sven > > | > > | -- > > | Sven Van Caekenberghe > > | http://stfx.eu > > | Smalltalk is the Red Pill > > | > > | > > | > > | > > | > > > > >

Oct. 1, 2012

Re: [Pharo-project] Metacello bleedingEdge question

by StÃ©phane Ducasse

OK so we should not talk about it anymore and ban it from all the configurations. It would be good to have specific rules for configurations. BTW: what do we do with the chapter I'm working on the new book and now I'm puzzled because I have invested a large amount of time and I get a chapter that you never gave feedback on and that is probably not correct or up to date. So may be the only thing I can do is to drop it. And after people will tell that pharo does not have documentation but I often fell alone. Stef > #latestVersion actually has a very good reason for existing, just not for use by end users in loading code ... > > It _has_ been dropped from the _convention_, and it shouldn't be dropped from the code base... > > Dale > > ----- Original Message ----- > | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Saturday, September 29, 2012 1:02:17 PM > | Subject: Re: [Pharo-project] Metacello bleedingEdge question > | > | > | On 29 Sep 2012, at 21:38, StÃ©phane Ducasse > | <stephane.ducasse(a)inria.fr> wrote: > | > | > On Sep 29, 2012, at 5:39 PM, Dale Henrichs wrote: > | > > | >> Stef, > | >> > | >> #latestVersion is there for backward compatibility. > | > > | > Ok > | > I would simply remove it. > | > > | > Stef > | > | I was about to say: what's that 'backward compatibility' ? > | > | ;-) > | > | No seriously, unless there is a very good, important reason to keep > | it, confusing stuff should be removed going forward. > | > | Sven > | > | -- > | Sven Van Caekenberghe > | http://stfx.eu > | Smalltalk is the Red Pill > | > | > | > | > | >

Oct. 1, 2012

Re: [Pharo-project] String>>includesSub[S|s]tring: - do we need another kind of deprecation ?

by StÃ©phane Ducasse

>> I was going to suggest you that. It is also accesible from the Settings UI. >> BTW, maybe we should do this in #cleanUpForProduction? >> > Maybe also there should be a different setting for when tests are run, and/or adding deprecations to the TestRunner result > eg. 15 deprecations, 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes Indeed it would be good. Stef

Oct. 1, 2012

[Pharo-project] [update 2.0] #20317

by Marcus Denker

20317 ----- Issue 6167: ClassFactoryForTestCase has silent extensions from fuel http://code.google.com/p/pharo/issues/detail?id=6167 Issue 6392: DNU for Text initialize http://code.google.com/p/pharo/issues/detail?id=6392 Issue 6277: PharoV10.sources files should be loaded on demand http://code.google.com/p/pharo/issues/detail?id=6277 -- Marcus Denker -- http://marcusdenker.de

Oct. 1, 2012