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" <[email protected]> > | To: [email protected] > | 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 > | <[email protected]> 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 > | > | > | > | > | >
