From one perspective, full names are clearer at the cost of some typing 33 percent 45 dollar 100 kilometerPerHour 4 newtonMeter 200 bitsPerSecond
And just like there is a limited namespace for class names (and prefixes to separate them), the namespace of selectors is global and limited too. #percent and #second(s) already exist, for example. So there might be conflicts. > On 17 Nov 2017, at 10:32, Torsten Bergmann <[email protected]> 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. >
