References TRune, links unicode modules where mentioned.
Amends 0f3941b0013ea5d390586719f930fcf02b929f4d.
This commit is contained in:
parent
2c2174f2d0
commit
42f152569d
1 changed files with 7 additions and 4 deletions
|
|
@ -342,7 +342,9 @@ A character is not an Unicode character but a single byte. The reason for this
|
||||||
is efficiency: for the overwhelming majority of use-cases, the resulting
|
is efficiency: for the overwhelming majority of use-cases, the resulting
|
||||||
programs will still handle UTF-8 properly as UTF-8 was specially designed for
|
programs will still handle UTF-8 properly as UTF-8 was specially designed for
|
||||||
this. Another reason is that Nimrod can thus support ``array[char, int]`` or
|
this. Another reason is that Nimrod can thus support ``array[char, int]`` or
|
||||||
``set[char]`` efficiently as many algorithms rely on this feature.
|
``set[char]`` efficiently as many algorithms rely on this feature. The `TRune`
|
||||||
|
type is used for Unicode characters, it can represent any Unicode character.
|
||||||
|
``TRune`` is declared in the `unicode module <unicode.html>`_.
|
||||||
|
|
||||||
|
|
||||||
Numerical constants
|
Numerical constants
|
||||||
|
|
@ -773,7 +775,8 @@ designed for this.
|
||||||
Another reason is that Nimrod can support ``array[char, int]`` or
|
Another reason is that Nimrod can support ``array[char, int]`` or
|
||||||
``set[char]`` efficiently as many algorithms rely on this feature. The
|
``set[char]`` efficiently as many algorithms rely on this feature. The
|
||||||
`TRune` type is used for Unicode characters, it can represent any Unicode
|
`TRune` type is used for Unicode characters, it can represent any Unicode
|
||||||
character. ``TRune`` is declared in the ``unicode`` module.
|
character. ``TRune`` is declared in the `unicode module <unicode.html>`_.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
@ -870,8 +873,8 @@ arrays, they can be used in case statements:
|
||||||
Per convention, all strings are UTF-8 strings, but this is not enforced. For
|
Per convention, all strings are UTF-8 strings, but this is not enforced. For
|
||||||
example, when reading strings from binary files, they are merely a sequence of
|
example, when reading strings from binary files, they are merely a sequence of
|
||||||
bytes. The index operation ``s[i]`` means the i-th *char* of ``s``, not the
|
bytes. The index operation ``s[i]`` means the i-th *char* of ``s``, not the
|
||||||
i-th *unichar*. The iterator ``runes`` from the ``unicode``
|
i-th *unichar*. The iterator ``runes`` from the `unicode module
|
||||||
module can be used for iteration over all Unicode characters.
|
<unicode.html>`_ can be used for iteration over all Unicode characters.
|
||||||
|
|
||||||
|
|
||||||
CString type
|
CString type
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue