> Well you would change the syntax of Pharo I'm not sure this is a syntax change like others. Haven yet thought about it too deeply. Where is the difference between an unary method #m and #% from the callers point of view?
Either there is an argument object then % is a binary - if not it is an unary. Maybe it is hard to parse or introduces new problems. >But I would imagine that people do and will do named unary selectors within >their projects (which is something quite >different to having all of it in Pharo by default) I dont want to have them inside by default in the base image - but people might be interested in implementing % (for percent), € (Euro) or ‰ (promille) as own unary messages in an own custom external package. Or having binary messages with Unicode. Just an idea to discuss what it would mean to have such beasts or if it would be useful ;) Bye T.
