On Jul 17, 2013, at 10:32 PM, Nicolas Cellier <nicolas.cellier.aka.n...@gmail.com> wrote:
> So you would be ready to change notNil -> isNotNil and become a bit more > incompatible with the rest of the world? > I understand that the pair isEmpty/isNotEmpty may seem a bit more > homogeneous, but I see no other selector constructed with (isNot isnt) while > I see many others where is is omitted. > I wonder what this kind of change really serve… I kind of agree. We should pay attention that we do not change for changing even. It is true that this is a bit frustating. Now what would be good is to have rules that can automatically transform code because they could be use when we want to change I would love also to have some rules when I edit the code because I always forget if it is better to use isNil ifNil….. Stef > Nicolas > > > 2013/7/17 Marcus Denker <marcus.den...@inria.fr> > 30276 > ----- > > 7300 Finder raise an error on asking for implementors > https://pharo.fogbugz.com/f/cases/7300 > > 10348 GroupAlreadyExists vs. GroupsAlreadyExists confusion > https://pharo.fogbugz.com/f/cases/10348 > > 11180 Add a filter to the config browser > https://pharo.fogbugz.com/f/cases/11180 > > 11172 notEmpty should be isNotEmpty > https://pharo.fogbugz.com/f/cases/11172 > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1177.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Nautilus-MarcusDenker.492.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/GroupManager-MarcusDenker.43.diff > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Abstract-MarcusDenker.216.diff > > >
