On Fri, Nov 26, 2010 at 4:35 AM, Lukas Renggli <renggli@gmail.com> wrote:
I agree, removing the option in Pharo 1.2 is maybe a bit early. The idea is to gradually increase the pain of underscore assignments, to finally get rid of them.
That's fine. But the scanner still needs to support them always because otherwise you'll get a syntax error parsing old source files containing underscores. That's the intent of my Scanner>>#initScannerForTokenization method which is used by the ChangeScanner so that old files can still be examined. Right? Eliot
Lukas
On 26 November 2010 09:02, Torsten Bergmann <astares@gmx.de> wrote:
Hi Lukas,
In Pharo 1.2 we hopefully remove the option (underscore assignments) to get rid of them for all and forever.
You wont get rid of them just by removing the option. :(
There is a lot of "legacy" code out there that is not converted and will then not be loadable in Pharo >= 1.2 or greater.
Keeping the option would allow to load this code and convert it to standard assignment in the future. Otherwise one has to use Squeak or Pharo < 1.2 to convert before using it in recent images.
On the other side we havent cared on backward compatibily too much anyway (yet) ...
Bye T.
-- GMX DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://portal.gmx.net/de/go/dsl
-- Lukas Renggli www.lukas-renggli.ch