aboutsummaryrefslogtreecommitdiffstats
path: root/lib/stdlib/doc/src/unicode_usage.xml
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2017-03-16 15:42:15 +0100
committerBjörn Gustavsson <[email protected]>2017-03-16 16:31:01 +0100
commitfc3b5a1a287780bced92f2f1a1744bf86d7b9ba2 (patch)
treea1050511e6c2eadb85a8c01a046fcdcef3d2f57a /lib/stdlib/doc/src/unicode_usage.xml
parent6a0ca45bb465150ba47d057ecd6c75681b790aab (diff)
downloadotp-fc3b5a1a287780bced92f2f1a1744bf86d7b9ba2.tar.gz
otp-fc3b5a1a287780bced92f2f1a1744bf86d7b9ba2.tar.bz2
otp-fc3b5a1a287780bced92f2f1a1744bf86d7b9ba2.zip
Don't allow module names with non-latin1 characters
In OTP 20, all Unicode characters are allowed in atoms. However, we have decided that we will not allow non-latin1 characters in module names in OTP 20. This restriction may be lifted in a future major release of OTP. Enforce the restriction in erl_lint, so that it will be a compilation error to have a module name containing non-latin1 characters. That means that tools such as debugger, xref, dialyzer, syntax_tools, and so on, do not have to be modified to handle non-latin1 module names.
Diffstat (limited to 'lib/stdlib/doc/src/unicode_usage.xml')
0 files changed, 0 insertions, 0 deletions