> I am not sure, but I think FixUnderscores should be useful for old packages > loaded in pharo.
The problem with the FixUnderscores package is that it does a string replacement and thus might perform incorrect transformations. You need to manually visit each change to be sure that it did correctly. The RB engine does a tree based transformation, which is always correct. I am all for kicking this package. It also contains old code that changes font glyphs, that's not needed any longer. Lukas > For example, some projects still use _, so we need FixUnderscore to fix them > automatically. > Personally, I use it on the whole Pharo 3 months ago. > Cheers, > Jannik > > On Mar 18, 2010, at 23:37 , Mariano Martinez Peck wrote: > > http://code.google.com/p/pharo/issues/detail?id=2165 > > There are some packages that has to be removed. For example: > - PinesoftEnhancementsForFreeType: This package is empty > - FixUnderscores: This package is old, is not needed any more and has no > references > > The fix is to evaluate: > > (MCPackage named: 'PinesoftEnhancementsForFreeType') unload. > (MCPackage named: 'FixUnderscores') unload. > > Cheers > > Mariano > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
