]> git.proxmox.com Git - ceph.git/blame - ceph/src/boost/libs/spirit/repository/doc/qi/advance.qbk
bump version to 12.2.2-pve1
[ceph.git] / ceph / src / boost / libs / spirit / repository / doc / qi / advance.qbk
CommitLineData
7c673cae
FG
1[/==============================================================================
2 Copyright (C) 2001-2011 Hartmut Kaiser
3 Copyright (C) 2001-2011 Joel de Guzman
4 Copyright (C) 2011 Aaron Graham
5
6 Distributed under the Boost Software License, Version 1.0. (See accompanying
7 file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
8===============================================================================/]
9
10[section:advance Qi advance Parser]
11
12[heading Description]
13
14The __qi__ `advance` is a primitive parser component allowing the parser to
15skip (advance) through a specified number of iterations without performing
16unnecessary work:
17
18 advance(distance)
19
20The most obvious existing alternative to this, the `repeat` directive, will
21cause the parser to advance one iterator at a time while usually performing
22operations at each step. In some cases that work is unnecessary, as in the case
23where large binary objects are being parsed. Take, for example, the following
24binary data:
25
26[pre
27 00 00 00 01 77 fc b4 51 0a b3 b7 ... 1e 60 70 b6 00 00 01 00
28]
29
30If the first 4 bytes are a little-endian 32-bit integer describing the length
31of the subsequent data, but the data itself is not relevant to parsing, then the
32repeat directive would cause all of the subsequent 16 MB of data to be consumed
33one byte at a time while generating page faults or other superfluous I/O. If the
34value is large, as it is in this case, the parser becomes very slow.
35
36 little_dword[_a = _1] >> repeat(_a)[byte_] >> little_dword...
37
38The `advance` parser component solves this problem by performing as little work
39as possible to advance the parser's iterator, and will optimize for the case of
40random-access iterators by advancing directly to the desired relative iterator
41position.
42
43 little_dword[_a = _1] >> advance(_a) >> little_dword...
44
45[heading Header]
46
47 // forwards to <boost/spirit/repository/home/qi/primitive/advance.hpp>
48 #include <boost/spirit/repository/include/qi_advance.hpp>
49
50[heading Synopsis]
51
52 advance(distance)
53
54[heading Parameters]
55
56[table
57 [[Parameter] [Description]]
58 [['distance'] [The distance that the iterator shall be advanced]]
59]
60
61[heading Attribute]
62
63The `advance` component exposes no attribute (the exposed attribute type is
64`unused_type`):
65
66 advance --> unused
67
68[heading Example]
69
70The following example shows simple use cases of the `advance` component. We will
71illustrate its usage by generating parsers for some binary data (for the full
72example code see
73[@../../example/qi/advance.cpp advance.cpp])
74
75[import ../example/qi/advance.cpp]
76
77[heading Prerequisites]
78
79In addition to the main header file needed to include the core components
80implemented in __qi__ we add the header file needed for the new `advance`
81component.
82
83[qi_advance_includes]
84
85In order to make the examples below more readable we introduce or use the
86following namespaces.
87
88[qi_advance_namespaces]
89
90[heading Setting up the Grammar]
91
92This is a very simple grammar that recognizes several fields of a binary stream
93of data. There are two fields explicitly delimited by a field indicating the
94number of bytes that are spanned. They are separated by a literal string.
95
96[qi_advance_grammar]
97
98Note that the second binary field may either contain the number of specified
99bytes, or the word "qi". If the `advance` parser component fails to advance the
100specified number of bytes before reaching the end of input, it will fail and
101the parser will attempt to descend into alternatives.
102
103[heading Parsing a Correctly-delimited String of Data]
104
105The data below is correctly delimited and will thus result in a valid parse.
106Note that both random-access and bidirectional iterators are used here.
107
108[qi_advance_example1]
109
110[heading Parsing the Alternative Representation]
111
112The data below is not correctly delimited, but will correctly parse because the
113alternative word "qi" is available.
114
115[qi_advance_example2]
116
117[heading Notes]
118
119The `advance` parser component will fail unconditionally on negative values.
120It will never attempt to advance the iterator in the reverse direction.
121
122[endsect]