| /third_party/boost/libs/spirit/doc/x3/abstracts/ |
| D | syntax_diagram.qbk | 35 Non-terminals are represented by boxes. Diagrams are modularized using
36 named non-terminals. A complex diagram can be broken down into a set of
37 non-terminals. Non-terminals also allow recursion (i.e. a non-terminal can call
|
| /third_party/boost/libs/yap/doc/ |
| D | concepts.qbk | 110 terminals (or references to terminals):
128 This one takes any call expression with two terminals (or references to
129 terminals) containing values convertible to `double`:
|
| D | codegen.qbk | 42 If we increase the number of terminals by a factor of four:
49 However, increasing the number of terminals by an additional factor of 2.5
50 (for a total of 90 terminals), the inliner can no longer do as well for _yap_
|
| D | examples.qbk | 167 So far we've only seen examples with custom terminals that own the values in
251 get special behavior on terminals. In this case, we want to create a
258 need is for the `OPCODE` to be the value of the terminals we produce, and for
259 these function-terminals to have the call operator.
282 Sometimes it can be useful only to transform the terminals in an expression.
284 `simd<double>`, you may want to replace all the `double` terminals with
288 In this example, we're replacing all the terminals with something essentially
289 arbitrary, the sequence of integer terminals `N, N + 1, N + 2, ...`. This
|
| D | primer.qbk | 28 terminals, one for the callable, and one for its single argument.
62 The children of the `std::sqrt(3.0)` subexpression are terminals. This means
70 Notice a couple of things here: 1) non-terminals (the top-level plus operation
72 expressions, and 2) terminals have tuple elements, *none of which* are _yap_
87 terminals in the expression we want to capture and evaluate lazily. Here,
|
| D | rationale.qbk | 13 Though this creates minor difficulties (for instance, _yap_ terminals cannot
|
| D | tutorial.qbk | 225 if they are terminals _emdash_ whether they contain or refer to their values.
245 through. It still takes values out of terminals and unwraps _expr_ref_
248 The auto-unwrapping of terminals means that you can effectively ignore the
250 just deal with the values inside terminals, and not the terminals
296 The transforms returned by _replacements_ replace only placeholder terminals.
|
| /third_party/boost/libs/spirit/doc/abstracts/ |
| D | syntax_diagram.qbk | 41 Non-terminals are represented by boxes. Diagrams are modularized using
42 named non-terminals. A complex diagram can be broken down into a set of
43 non-terminals. Non-terminals also allow recursion (i.e. a non-terminal
|
| /third_party/python/Tools/peg_generator/pegen/ |
| D | first_sets.py | 130 terminals = self.visit(item.rhs)
132 terminals.add("")
133 self.first_sets[item.name] = terminals
|
| /third_party/node/deps/npm/node_modules/wcwidth/docs/ |
| D | index.md | 14 applications and (teletype-style) character terminals using the
18 how many cell positions on character terminals. These routines are
49 up a proper standard for the behavior of UTF-8 character terminals
|
| /third_party/boost/libs/proto/doc/ |
| D | calculator.qbk | 14 see how to define the terminals in your mini-language, how to compose them into
33 // Define the Protofied placeholder terminals
49 Now that we have terminals, we can use Proto's operator overloads to combine
50 these terminals into larger expressions. So, for instance, we can immediately
91 terminals by defining the appropriate overloads of the function call operator.
93 non-placeholder terminals), Proto will evaluate the expression in the "default"
175 // Define the Protofied placeholder terminals, in the
226 …nly placeholders and literals that are convertible to doubles are valid terminals. Later on we'll …
|
| D | intermediate_form.qbk | 26 …out how to build a front-end for your EDSL "compiler" -- you can define terminals and functions th…
54 is a list of child types, or in the case of terminals, the terminal's value
297 …ep-copy your expression template so that all intermediate nodes and the terminals are held /by val…
315 …ression tree, all intermediate nodes and all terminals are stored by value. The only exception is …
339 In order to call _display_expr_, all the terminals in the expression must be Streamable (that is, t…
617 …uments of a lazy function invocation, we would like to iterate over the terminals in an addition e…
630 …not describe a flat sequence of terminals --- it describes a binary tree. We can treat it as a fla…
668 First, let's define some terminals we can use in our lazy I/O expressions:
785 …terminals in an expression tree could be const or non-const references, or they might not be refer…
789 The table below shows how Proto matches terminals. The simple rule is: if you want to match only re…
[all …]
|
| D | back_end.qbk | 197 // Handle placeholder terminals here...
209 // Handle other terminals here...
411 integer terminals, and you would like to increment each integer in-place. You
423 // Increment integer terminals
461 // integer terminals in-place.
470 // Handle int terminals here:
515 of placeholder terminals, and delegate the handling of all other nodes to the
519 // explicitly handles placeholder terminals, but defers the
540 terminals, we can evaluate calculator expressions, as demonstrated
588 // A simple Proto grammar that matches all terminals
[all …]
|
| D | front_end.qbk | 13 … designing an EDSL interface using Proto. We'll cover the definition of terminals and lazy functio…
19 …ion, the simplest way to get an EDSL up and running is simply to define some terminals, as follows.
27 With some terminals and Proto's operator overloads, you can immediately start creating expression t…
29 Defining terminals -- with aggregate initialization -- can be a little awkward at times. Proto prov…
49 Once we have some Proto terminals, expressions involving those terminals build expression trees for…
110 If we limited ourselves to nothing but terminals and operator overloads, our embedded domain-specif…
146 It is important to note that there is nothing special about terminals that contain function pointer…
311 … case of the calculator, the context is also what defines the meaning of the placeholder terminals.
619 …sion or not (using _is_expr_), and then turn non-expressions into Proto terminals by wrapping them…
687 …-wiring our domain's `as_child<>` to `as_expr<>`, we guarantee that all terminals that can be held…
[all …]
|
| D | rationale.qbk | 19 initialized]. Why is static initialization important? The terminals of many embedded
|
| /third_party/boost/libs/spirit/repository/doc/qi/ |
| D | nonterminals.qbk | 9 [section:nonterminal Qi Parser Non-terminals]
|
| /third_party/boost/libs/spirit/repository/doc/karma/ |
| D | nonterminals.qbk | 9 [section:nonterminal Karma Generator Non-terminals]
|
| /third_party/python/Doc/howto/ |
| D | curses.rst | 21 keyboard-handling facility for text-based terminals; such terminals
23 by various programs. Display terminals support various control codes
25 screen, and erasing areas. Different terminals use widely differing
29 true that character-cell display terminals are an obsolete technology,
204 terminal connections in mind; with these terminals, minimizing the
321 ``move(y,x)`` method. Because some terminals always display a flashing cursor,
372 The curses library also supports color on those terminals that provide it. The
391 on all terminals.
420 Very fancy terminals can change the definitions of the actual colors to a given
549 video of a PyCon 2013 talk on controlling terminals using curses or Urwid.
|
| /third_party/boost/tools/auto_index/src/ |
| D | auto_index.cpp | 255 static std::set<const char*, string_cmp> terminals; in should_flatten_node() local
257 if(terminals.empty()) in should_flatten_node()
258 terminals.insert(names.begin(), names.end()); in should_flatten_node()
259 return 0 != terminals.count(name); in should_flatten_node()
|
| /third_party/boost/libs/phoenix/doc/inside/ |
| D | custom_terminal.qbk | 16 Custom terminals could be any wrapper class:
|
| /third_party/node/deps/npm/node_modules/console-control-strings/ |
| D | README.md | 101 * **bold** – Display text as bold. In some terminals this means using a
104 * **italic** – Display text as italic. This is not available in most Windows terminals.
|
| /third_party/node/deps/npm/node_modules/wide-align/ |
| D | README.md | 4 A wide-character aware text alignment function for use in terminals / on the
|
| /third_party/node/deps/npm/node_modules/ansistyles/ |
| D | README.md | 46 but didn't have any effect on the terminals that I tested on Mac Lion and Ubuntu Linux.
|
| /third_party/boost/libs/phoenix/doc/ |
| D | organisation.qbk | 41 Expressions are used to combine these terminals together to provide more
|
| /third_party/boost/libs/spirit/doc/karma/ |
| D | basics.qbk | 13 Some generators (e.g. primitives and non-terminals) may take in additional
|