argh! I loved magic. In that case I would go for 2 because supporting migration is important.
Stef >> Now could not we have 3? >> 3 >> do 1 (ie no preference) but transform the code from _ into := >> automatically. >> It would be really great in fact > > That would be the magic solution :-) > > The problem is that it would not be clear how to parse a_1. Is it the > assignment of 1 to a or the access of the variable a_1? > > I don't like the proposal of requiring a delimiter before and after an > underscore assignment: (1) there is existing code where this is not > the case, (2) it complicates the scanning significantly, the same > token represents different things depending on context and an extended > lookahead is required to parse it, and (3) it allows that people > continue to use crappy underscore assignments, there will be a mess > forever. > > 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
