> Given that in Pharo we have Symbol>>value:, are there any reasons not > to have also > > Symbol>>value: anObject value: anotherObject > ^ anObject perform: self with: anotherObject
While Symbol>>#value: is at the border of being readable, Symbol>>#value:value: is even worse. It is not immediately obvious what it does. The order of receiver and arguments is hardcoded and thus the construct cannot be applied in most cases without rewriting the code. Fixed arguments cannot be given. Instead of adding new #value: variants, we should rather try to remove Object>>#value which is a real nightmare ;-) Cheers, 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
