2010/3/6 Lukas Renggli <renggli@gmail.com>:
Nicolas published a version for pharo and it would be really cool if you could help me     http://code.google.com/p/pharo/issues/detail?id=2115
What should I do?
- I can update the RB so that it works the same way.
Yes
- I can provide rewritten code for the complete core system that uses ambiguous constructs like 1@-2.
Compiler recompileAll will transcript the ambiguous constructs already. If you want, that would be useful to avoid spreading my initials everywhere (I hate spreading, at least when I add no value).
For the compile changes themselves I wouldn't throw a warning, not even in interactive mode. Also I wouldn't add a setting, that just causes troubles in many years ahead.
Agree about Preferences for accepting incompatible syntax : it is poisonous. This preference would be usefull only to load old packages, but risk to be abused to write non conforming code. Personnally, I want the warning. It's so easy to get bitten by ^x/-2... It would be good to have a Preference for the warning. Nicolas
Lukas
-- Lukas Renggli http://www.lukas-renggli.ch
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project