[erlang-bugs] R16 breaks dots
Sat Mar 30 10:42:04 CET 2013
It was pretty useful to be able to write unquoted fully-qualified node names in the prompt, e.g.
Furthermore, it feels to me like their removal was a mistake, as demonstrated by this:
* 1: syntax error before: '.'
1> foo. bar.
What you can see here is that the blanks after a dot are still mandatory to properly parse a '.' character as a 'dot' token, terminating an expression in the shell (or a form in a module), this was mandatory to distinguish dot terminators from dots in atoms.
If dots are really to not be allowed anymore in atoms, the blanks should be made optional, to be consistent with the rest of the language where blanks are optional before or after a symbol (with the notable exception of a match '=' followed by a binary literal '<<...>>').
Le 29 mars 2013 à 21:34, Josh Marchán a écrit :
> It's widely known that it's useful to be able to use
> dots/periods/full-stops (choose your dialect) in Erlang code to maximize
> Unfortunately for the world of Erlang, R16 breaks something that has been
> tremendously useful. I am no longer able to do this:
> console.log("Hello from erlang", 1, 2, "More string here", TildePMe)
> which is leading to a lot of confusion when I regularly switch between
> I would like to formally request that $. once again become a valid
> character in Erlang identifiers. Until such a time, I regret I must divest
> from version upgrades. I look forward to your response (and prompt bugfix).
> Josh Marchán
More information about the erlang-bugs