>> The only change is that the compiler refuses to compile underscore
>> assignments. It seems to be problematic to throw a deprecated message,
>> as this can happen in all kind of weird situations. So now you just
>> get a syntax error, or in interactive mode (when loading with
>> Monticello) a popup that gives you the possibility to fix the code. I
>> suggest to integrate that into Pharo 1.0. Loading old code is a bit
>> cumbersome, but I guess most people already fixed their code-base.
>
> really in 1.0
> we should pay attention because we want as few as possible of fixes in
> 1.0 :)

It is not a fix. It just throws an error when somebody tries to
compile code with underscore assignments.

I thought that this would give people some time to think about their
code, but probably it is not that useful after all and we better just
fix the real thing.

Lukas

-- 
Lukas Renggli
http://www.lukas-renggli.ch

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to