diff options
| author | Björn Gustavsson <[email protected]> | 2017-05-17 06:24:02 +0200 |
|---|---|---|
| committer | Björn Gustavsson <[email protected]> | 2017-05-17 06:45:31 +0200 |
| commit | b8d4bd38e343488b5e8539f913650b150cab3ade (patch) | |
| tree | 06bfca27396931f5e37cb9fd43aa3275bbf6580e /system | |
| parent | a29bb639a5a0acf7da4d4fa65e4dd7c9cdcadb3c (diff) | |
| download | otp-b8d4bd38e343488b5e8539f913650b150cab3ade.tar.gz otp-b8d4bd38e343488b5e8539f913650b150cab3ade.tar.bz2 otp-b8d4bd38e343488b5e8539f913650b150cab3ade.zip | |
Add a link to the Reference Manual from the example page
When doing a Google search for "bit syntax", you could end up
on the programming examples page about bit syntax. The example
page has some reference material, but is far from complete.
Therefore, add a link to the page about bit syntax in the
Reference Manual.
https://bugs.erlang.org/browse/ERL-387
Diffstat (limited to 'system')
| -rw-r--r-- | system/doc/programming_examples/bit_syntax.xml | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/system/doc/programming_examples/bit_syntax.xml b/system/doc/programming_examples/bit_syntax.xml index 0af295b7b7..03645bba1b 100644 --- a/system/doc/programming_examples/bit_syntax.xml +++ b/system/doc/programming_examples/bit_syntax.xml @@ -32,6 +32,8 @@ <section> <title>Introduction</title> + <p>The complete specification for the bit syntax appears in the + <seealso marker="doc/reference_manual:expressions#bit_syntax">Reference Manual</seealso>.</p> <p>In Erlang, a Bin is used for constructing binaries and matching binary patterns. A Bin is written with the following syntax:</p> <code type="none"><![CDATA[ @@ -165,8 +167,9 @@ end.]]></code> separated by hyphens.</p> <taglist> <tag>Type</tag> - <item>The type can be <c>integer</c>, <c>float</c>, or - <c>binary</c>.</item> + <item>The most commonly used types are <c>integer</c>, <c>float</c>, and <c>binary</c>. + See <seealso marker="doc/reference_manual:expressions#bit_syntax">Bit Syntax Expressions in the Reference Manual</seealso> for a complete description. +</item> <tag>Signedness</tag> <item>The signedness specification can be either <c>signed</c> or <c>unsigned</c>. Notice that signedness only matters for |