| /external/pigweed/pw_rpc/fuzz/ |
| D | argparse_test.cc | 124 Vector<ArgParserVariant, 3> parsers = { in TEST() local
129 PrintUsage(parsers, "test-bin"); in TEST()
132 void CheckArgs(Vector<ArgParserVariant>& parsers, in CheckArgs() argument
137 EXPECT_EQ(GetArg(parsers, "--verbose", &actual_verbose), OkStatus()); in CheckArgs()
139 EXPECT_EQ(ResetArg(parsers, "--verbose"), OkStatus()); in CheckArgs()
142 EXPECT_EQ(GetArg(parsers, "--runs", &actual_runs), OkStatus()); in CheckArgs()
144 EXPECT_EQ(ResetArg(parsers, "--runs"), OkStatus()); in CheckArgs()
147 EXPECT_EQ(GetArg(parsers, "port", &actual_port), OkStatus()); in CheckArgs()
149 EXPECT_EQ(ResetArg(parsers, "port"), OkStatus()); in CheckArgs()
153 Vector<ArgParserVariant, 3> parsers{ in TEST() local
[all …]
|
| D | client_fuzzer.cc | 31 Vector<ArgParserVariant, 5> parsers{ in FuzzClient() local
48 if (!ParseArgs(parsers, argc, argv).ok()) { in FuzzClient()
49 PrintUsage(parsers, argv[0]); in FuzzClient()
58 if (!GetArg(parsers, "--verbose", &verbose).ok() || in FuzzClient()
59 !GetArg(parsers, "--num-actions", &num_actions).ok() || in FuzzClient()
60 !GetArg(parsers, "--seed", &seed).ok() || in FuzzClient()
61 !GetArg(parsers, "--timeout", &timeout_ms).ok() || in FuzzClient()
62 !GetArg(parsers, "port", &port).ok()) { in FuzzClient()
|
| /external/llvm/utils/lit/tests/unit/ |
| D | TestRunner.py | 40 inputs = [os.path.join(test_path, 'Inputs/testrunner-custom-parsers/')]
81 parsers = self.make_parsers()
82 self.parse_test(parsers)
83 tag_parser = self.get_parser(parsers, 'MY_TAG.')
84 dne_tag_parser = self.get_parser(parsers, 'MY_DNE_TAG.')
89 parsers = self.make_parsers()
90 self.parse_test(parsers)
91 list_parser = self.get_parser(parsers, 'MY_LIST:')
96 parsers = self.make_parsers()
97 self.parse_test(parsers)
[all …]
|
| /external/pigweed/pw_rpc/fuzz/public/pw_rpc/fuzz/ |
| D | argparse.h | 26 /// "port" argument to be parsed, we can create a vector of parsers. In this
27 /// example, we modify the parsers during creation to set default values:
30 /// Vector<ArgParserVariant, 3> parsers = {
41 /// if (!ParseArgs(parsers, argc, argv).ok()) {
42 /// PrintUsage(parsers, argv[0]);
48 /// if (!GetArg(parsers, "--verbose", &verbose).ok() ||
49 /// !GetArg(parsers, "--runs", &runs).ok() ||
50 /// !GetArg(parsers, "port", &port).ok()) {
70 /// with a particular parsers.
85 /// being out of range, etc. Parsers should log additional details before
[all …]
|
| /external/rust/crates/nom/ |
| D | README.md | 11 to build safe parsers without compromising the speed or memory consumption. To
13 fast and correct parsers, and provides functions, macros and traits to abstract most of the
25 - [Binary format parsers](#binary-format-parsers)
26 - [Text format parsers](#text-format-parsers)
27 - [Programming language parsers](#programming-language-parsers)
34 - [Parsers written with nom](#parsers-written-with-nom)
99 …f you need any help developing your parsers, please ping `geal` on IRC (libera, geeknode, oftc), g…
105 ### Binary format parsers
108 to the usual handwritten C parsers, nom parsers are just as fast, free from
114 - Streaming parsers for network formats and huge files
[all …]
|
| D | CHANGELOG.md | 45 - implement `ErrorConvert` on the unit type to make it usable as error type for bits parsers
125 - text to number parsers: in the `character::streaming` and `character::complete` modules, there ar…
129 - now that function combinators are the main way to write parsers, the old macro combinators are co…
131 - regex parsers have been moved into the [nom-regex](https://crates.io/crates/nom-regex) crate. nom…
222 - relax trait bounds on some parsers
309 function parsers, by relaxing the requirements: combinators will return a
311 and parsers can be any type now, as long as they implement the new `Parser` trait.
325 so this will give better options for those parsers.
334 …streaming parsers return the number of additional bytes they need, not the total. This was suppose…
338 - there is now a more general `Parser` trait, so parsers can be something else than a function. Thi…
[all …]
|
| /external/jackson-core/src/main/java/com/fasterxml/jackson/core/util/ |
| D | JsonParserSequence.java | 19 * Parsers other than the first one (which is initially assigned
25 * Configuration that determines whether state of parsers is first verified
30 * {@link JsonParser#nextToken} is always called for all parsers.
33 * so that possible existing token is not considered for parsers.
59 protected JsonParserSequence(JsonParser[] parsers) { in JsonParserSequence() argument
60 this(false, parsers); in JsonParserSequence()
66 protected JsonParserSequence(boolean checkForExistingToken, JsonParser[] parsers) in JsonParserSequence() argument
68 super(parsers[0]); in JsonParserSequence()
71 _parsers = parsers; in JsonParserSequence()
77 * contains all given sub-parsers.
[all …]
|
| /external/rust/crates/winnow/src/_topic/ |
| D | why.rs | 9 //! ## Hand-written parsers
20 //! - Ensuring the safety of any `unsafe` code (buffer overflows being a common bug with parsers)
32 //! Unlike traditional programming language parsers that use
41 //! - [Stateful][crate::Stateful] parsers
46 //! - Some common parsers to help get started, like numbers
64 //! for the parsers yet to be written.
89 //! rather than directly with the parsers.
93 //! GATs](https://github.com/zesterer/chumsky/pull/82) which allows downstream parsers to tell
94 //! upstream parsers when information will be discarded, allowing bypassing expensive operations,
95 //! like allocations. This requires a lot more complex interaction with parsers that isn't as
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/x3/abstracts/ |
| D | attributes.qbk | 12 Parsers in __spirit__ are fully attributed. __x3__ parsers always /expose/ an
15 instance, numeric parsers, such as `int_` or `double_`, return the `int` or
18 which has `int`, or `ascii::char_` which has `char`. Primitive parsers apply the
38 parsers, such as sequences, alternatives, Kleene star, etc. The main attribute
45 [:Given `a` and `b` are parsers, and `A` is the attribute type of `a`, and `B`
61 For a full list of how the different compound parsers consume attributes
64 [heading The Attribute of Sequence Parsers]
95 [heading The Attribute of Alternative Parsers]
97 Alternative parsers are all about - well - alternatives. In
163 [:Given `a` and `b` are parsers, and `A` is the attribute type of
[all …]
|
| /external/rust/crates/winnow/src/_tutorial/ |
| D | chapter_0.rs | 13 //! - "parsers", or functions that take an input and give back an output
14 //! - "combinators", or functions that take parsers and _combine_ them together!
28 //! - The parsers are small and easy to write
29 //! - The parsers components are easy to reuse (if they're general enough, please add them to winno…
30 //! - The parsers components are easy to test separately (unit tests and property-based tests)
32 //! - You can build partial parsers, specific to the data you need at the moment, and ignore the re…
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/notes/ |
| D | porting_from_1_8.qbk | 18 interface. Generally, there is no easy (or automated) way of converting parsers
20 guidelines on how to approach porting your older parsers to the current version
28 the needed header files for your new parsers. Moreover, each section in the
55 the primitives parsers now directly support lazy
111 Note, how character parsers are in a separate namespace (here
118 encoding their type: `"_p"` for parsers, `"_a"` for lazy actions, `"_d"` for
122 integer parser). Overall, most, if not all primitive parsers and directives
129 type. Most parsers expose the pair of iterators pointing to the matched input
130 sequence. As in __qi__ all parsers expose a parser specific attribute type it
134 very much encourage you to rewrite your parsers to take advantage of the
[all …]
|
| /external/python/pyfakefs/pyfakefs/ |
| D | patched_packages.py | 21 import pandas.io.parsers as parsers namespace
23 parsers = None variable
37 patch_pandas = parsers is not None and [int(v) for v in pd.__version__.split(".")] < [
56 classes_to_patch["TextFileReader"] = ["pandas.io.parsers"]
125 self._parsers_module = parsers
127 class TextFileReader(parsers.TextFileReader):
|
| /external/rust/crates/combine/ |
| D | README.md | 7 …y [Parsec](https://hackage.haskell.org/package/parsec). As in Parsec the parsers are [LL(1)](https…
25 // `parse` returns `Result` where `Ok` contains a tuple of the parsers output and any remaining inp…
53 …module](https://docs.rs/combine/3.*/combine/parser/range/index.html) for parsers specialized for z…
55 * __partial parsing__ - Combine parsers can be stopped at any point during parsing and later be res…
59 …parsers as arguments and returns a new parser, created by combining those parsers. For instance, t…
69 Since `combine` aims to crate parsers with little to no overhead, streams over `&str` and `&[T]` do…
75 ## Parsers written in combine
99 There is an additional crate which has parsers to lex and parse programming languages in [combine-l…
|
| /external/jsoncpp/ |
| D | README.md | 4 [](https://github.com/open-source-parsers/js…
5 [](http://open-source-parsers.gi…
6 …lls.io/repos/github/open-source-parsers/jsoncpp/badge.svg?branch=master)](https://coveralls.io/git…
25 [JsonCpp-documentation]: http://open-source-parsers.github.io/jsoncpp-docs/doxygen/index.html
56 https://github.com/open-source-parsers/jsoncpp/wiki/Amalgamated-(Possibly-outdated)
62 If you have trouble, see the [Wiki](https://github.com/open-source-parsers/jsoncpp/wiki), or post a…
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/qi/ |
| D | warming_up.qbk | 12 to build parsers from the simplest parser, building up as we go. When comparing
24 parsers and consistent naming conventions help you keep from going insane!
35 operator. The above program creates a parser from two simpler parsers, glueing
37 composition of smaller parsers. Whitespace between numbers can implicitly be
40 [note When we combine parsers, we end up with a "bigger" parser, but
41 it's still a parser. Parsers can get bigger and bigger, nesting more and more,
42 but whenever you glue two parsers together, you end up with one bigger parser.
92 is included in Spirit's repertoire of predefined parsers. It is a very simple
132 `char_('a') >> 'b'` and `'a' >> char_('b')` are Spirit sequence parsers
|
| D | basics.qbk | 12 Some parsers (e.g. primitives and non-terminals) may take in additional
13 attributes. Such parsers take the form:
29 Some parsers need to know which character set a `char` or `wchar_t` is
37 we place tagged versions of parsers such as `alnum`, `space` etc.
71 These functions test the parsers without attributes.
75 These functions test the parsers with user supplied attributes.
120 to customize the behavior of parsers are described in the section
|
| D | stream.qbk | 9 [section:stream Stream Parsers]
22 [section:stream Stream Parsers (`stream`, `wstream`, etc.)]
101 All parsers listed in the table above are predefined specializations of the
103 possible to directly use this type to create stream parsers using an
122 All of the stream parsers listed above require the type of the value to
134 This operator will be called by the stream parsers to gather the input for
156 parsers is semantically and syntactically equivalent to
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/x3/tutorial/ |
| D | warming_up.qbk | 12 to build parsers from the simplest parser, building up as we go. When comparing
24 parsers and consistent naming conventions help you keep from going insane!
35 operator. The above program creates a parser from two simpler parsers, glueing
37 composition of smaller parsers. Whitespace between numbers can implicitly be
40 [note When we combine parsers, we end up with a "bigger" parser, but
41 it's still a parser. Parsers can get bigger and bigger, nesting more and more,
42 but whenever you glue two parsers together, you end up with one bigger parser.
92 is included in Spirit's repertoire of predefined parsers. It is a very simple
147 `char_('a') >> 'b'` and `'a' >> char_('b')` are Spirit sequence parsers
|
| /external/rust/crates/nom/src/branch/ |
| D | mod.rs | 18 /// Tests a list of parsers one by one until one succeeds.
20 /// It takes as argument a tuple of parsers. There is a maximum of 21
21 /// parsers. If you need more, it is possible to nest them in other `alt` calls,
40 /// // both parsers failed, and with the default error type, alt will return the last error
57 /// Tries to apply all parsers in the tuple in various orders until all of them succeed
61 /// Applies a list of parsers in any order.
63 /// Permutation will succeed if all of the child parsers succeeded.
64 /// It takes as argument a tuple of parsers, and returns a
82 /// // it will fail if one of the parsers failed
87 /// The parsers are applied greedily: if there are multiple unapplied parsers
[all …]
|
| /external/autotest/tko/ |
| D | parser_lib.py | 1 import autotest_lib.tko.parsers.version_0
2 import autotest_lib.tko.parsers.version_1
10 0: autotest_lib.tko.parsers.version_0.parser,
11 1: autotest_lib.tko.parsers.version_1.parser,
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/abstracts/ |
| D | attributes.qbk | 14 Parsers and generators in __spirit__ are fully attributed. __qi__ parsers always
17 input sequence. For instance, numeric parsers, such as `int_` or `double_`,
21 primitive parsers apply the normal C++ convertibility rules: you can use any
60 for all compound parsers and generators, such as sequences, alternatives,
72 [:Given `a` and `b` are parsers (generators), and `A` is the attribute type of
92 [heading The Attribute of Sequence Parsers and Generators]
149 [heading The Attribute of Alternative Parsers and Generators]
151 Alternative parsers and generators are all about - well - alternatives. In
241 [:Given `a` and `b` are parsers (generators), and `A` is the attribute type of
261 Nonterminals are well known from parsers where they are used as the main means
[all …]
|
| /external/sdv/vsomeip/third_party/boost/spirit/test/qi/ |
| D | test.hpp | 21 // we only care that all parsers have it: in test()
36 // we only care that all parsers have it: in test()
51 // we only care that all parsers have it: in binary_test()
64 // we only care that all parsers have it: in binary_test()
77 // we only care that all parsers have it: in test_attr()
92 // we only care that all parsers have it: in test_attr()
107 // we only care that all parsers have it: in binary_test_attr()
120 // we only care that all parsers have it: in binary_test_attr()
|
| /external/sdv/vsomeip/third_party/boost/spirit/doc/advanced/ |
| D | indepth.qbk | 12 [section:parsers_indepth Parsers in Depth]
15 workings of __qi__ parsers, using real code from the __spirit__ library as
20 The `__parser_concept__` class is the base class for all parsers.
32 The Derived parsers, `__primitive_parser_concept__`, `__unary_parser_concept__`,
36 Derived parsers must support the following:
79 [variablelist Parsers
85 [heading Primitive Parsers]
101 /parse/ is the main entry point. For primitive parsers, our first thing to do is
114 even wrote some parsers with it, this simple __spirit__ mechanism
163 [heading Composite Parsers]
[all …]
|
| /external/rust/crates/nom/src/ |
| D | lib.rs | 56 //! about [how to write parsers](https://github.com/Geal/nom/blob/main/doc/making_a_new_parser_from…
68 //! Parser combinators are an approach to parsers that is very different from
80 //! - The parsers are small and easy to write
81 //! - The parsers components are easy to reuse (if they're general enough, please add them to nom!)
82 //! - The parsers components are easy to test separately (unit tests and property-based tests)
84 //! - You can build partial parsers, specific to the data you need at the moment, and ignore the re…
123 //! Writing all the parsers manually, like this, is dangerous, despite Rust's
125 //! nom provides a list of functions to help in developing parsers.
170 …ps://github.com/Geal/nom/blob/main/doc/choosing_a_combinator.md) for an exhaustive list of parsers.
173 //! ## Making new parsers with function combinators
[all …]
|
| /external/libcxx/utils/libcxx/test/ |
| D | format.py | 54 def _get_parser(key, parsers): argument
55 for p in parsers:
106 parsers = self._make_custom_parsers()
108 test, additional_parsers=parsers, require_script=is_sh_test)
130 parsers).getValue()
163 return self._evaluate_fail_test(test, test_cxx, parsers)
166 test_cxx, parsers)
175 test_cxx, parsers): argument
203 is_flaky = self._get_parser('FLAKY_TEST.', parsers).getValue()
225 def _evaluate_fail_test(self, test, test_cxx, parsers): argument
|