1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<refentry id="token.element">
<?dbhtml filename="token.html"?>
<refentryinfo>
<pubdate>$Date$</pubdate>
<releaseinfo>$Revision$</releaseinfo>
</refentryinfo>
<refmeta>
<indexterm><primary>elements</primary>
<secondary>token</secondary></indexterm>
<refentrytitle>token</refentrytitle>
<refmiscinfo>Element</refmiscinfo>
</refmeta>
<refnamediv>
<refname>token</refname>
<refpurpose>&token.purpose;</refpurpose>
</refnamediv>
&token.synopsis.gen;
<refsect1 condition='ref.description'><title>Description</title>
<para>
A <sgmltag>Token</sgmltag> identifies a unit of information. Usually,
<quote>tokens</quote> are the result of some processing pass that
has performed lexical analysis and divided a data set into the
smallest units of information used for subsequent processing.
</para>
<para>
Exactly what constitutes a token varies by context.
</para>
<refsect2><title>Processing expectations</title>
<para>
&format.inline;
</para>
</refsect2>
&token.parents.gen;
&token.children.gen;
</refsect1>
<refsect1 condition='ref.elem.seealso'><title>See Also</title>
&token.seealso.gen;
</refsect1>
<refsect1><title>Examples</title>
<informalexample role="example-source">
<programlisting>&token.example.1.txt;</programlisting>
</informalexample>
<anchor id="ex.os.token.1" role="HACK-ex.out.start"/>
&token.example.1.gen;
<anchor id="ex.oe.token.1" role="HACK-ex.out.end"/>
&token.example.seealso.gen;
</refsect1>
</refentry>
|
