diff options
| author | Siri Hansen <[email protected]> | 2014-11-18 10:07:16 +0100 |
|---|---|---|
| committer | Siri Hansen <[email protected]> | 2014-11-18 10:07:16 +0100 |
| commit | 9366932892711cc4cce7a54b1e098e6d5c3db468 (patch) | |
| tree | c876bac66f4cedd5c407b3a595b6f1b2b896f3a5 /lib/stdlib/doc/src | |
| parent | 761e1318abdaee269be8cdcbb6b3e6f5d3f2a65d (diff) | |
| parent | 08504087f66ab23e39c082782524e2d1e531e3e7 (diff) | |
| download | otp-9366932892711cc4cce7a54b1e098e6d5c3db468.tar.gz otp-9366932892711cc4cce7a54b1e098e6d5c3db468.tar.bz2 otp-9366932892711cc4cce7a54b1e098e6d5c3db468.zip | |
Merge branch 'siri/no-unicode-atoms/OTP-12172' into maint
* siri/no-unicode-atoms/OTP-12172:
Remove comments about unicode atoms in OTP 18
Diffstat (limited to 'lib/stdlib/doc/src')
| -rw-r--r-- | lib/stdlib/doc/src/unicode_usage.xml | 15 |
1 files changed, 5 insertions, 10 deletions
diff --git a/lib/stdlib/doc/src/unicode_usage.xml b/lib/stdlib/doc/src/unicode_usage.xml index bebfbd4514..29b8940c62 100644 --- a/lib/stdlib/doc/src/unicode_usage.xml +++ b/lib/stdlib/doc/src/unicode_usage.xml @@ -50,12 +50,8 @@ encoded files in several circumstances. Most notable is the support for UTF-8 in files read by <c>file:consult/1</c>, release handler support for UTF-8 and more support for Unicode character sets in the - I/O-system.</p> - - <p>In Erlang/OTP 17.0, the encoding default for Erlang source files was - switched to UTF-8 and in Erlang/OTP 18.0 Erlang will support atoms in the full - Unicode range, meaning full Unicode function and module - names</p> + I/O-system. In Erlang/OTP 17.0, the encoding default for Erlang source files was + switched to UTF-8.</p> <p>This guide outlines the current Unicode support and gives a couple of recipes for working with Unicode data.</p> @@ -289,8 +285,8 @@ <tag>The language</tag> <item>Having the source code in UTF-8 also allows you to write string literals containing Unicode characters with code points > - 255, although atoms, module names and function names will be - restricted to the ISO-Latin-1 range until the Erlang/OTP 18.0 release. Binary + 255, although atoms, module names and function names are + restricted to the ISO-Latin-1 range. Binary literals where you use the <c>/utf8</c> type, can also be expressed using Unicode characters > 255. Having module names using characters other than 7-bit ASCII can cause trouble on @@ -385,8 +381,7 @@ external_charlist() = maybe_improper_list(char() | using characters from the ISO-latin-1 character set and atoms are restricted to the same ISO-latin-1 range. These restrictions in the language are of course independent of the encoding of the source - file. Erlang/OTP 18.0 is expected to handle functions named in - Unicode as well as Unicode atoms.</p> + file.</p> <section> <title>Bit-syntax</title> <p>The bit-syntax contains types for coping with binary data in the |