Well you would change the syntax of Pharo, which I don't think will be met with a lot of enthusiasm.

How would you distinguish it from unary messages?
How would you distinguish it from something that should trigger compilation error instead? ($ for characters)

Also; 1 ml is one milliliter, or one mile?

Also considering how was the #, selector was shut down for Bloc vectors, this seems rather bold. :)

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)

Peter

On Fri, Nov 17, 2017 at 10:32 AM, Torsten Bergmann <astares@gmx.de> wrote:
Hi,

just something to think about: one thing I always liked about Smalltalk is that it allows for nice DSL's. We have nice things
like a unit framework in Pharo, ...

In the most simple case one can easily implement own units just by providing a unary messages:

��1 m
��1 second
��1 px
��1 EUR

One can easily implement an own Money class with a currency and then do polymorphic tricks like

�� 10 EUR + 20 EUR

But we can currently can not implement special unary selectors (including special unary selectors with unicode) like:

�� 100 %
�� 20 $
�� 40 ���
�� 12 ����� (for promille)

Especially things like 20 % would be nice for layout issues or other (Bloc comes to mind).

Maybe we should put that on the roadmap of Pharo because IMHO it would be cool to support such things in the
future. Dont know how much effort it currently means on the technical level but maybe others can comment.

Thx
T.