Searched refs:calculator_domain (Results 1 – 5 of 5) sorted by relevance
| /third_party/boost/libs/proto/example/ |
| D | calc3.cpp | 61 struct calculator_domain struct
94 : proto::extends<Expr, calculator_expression<Expr>, calculator_domain>
97 proto::extends<Expr, calculator_expression<Expr>, calculator_domain>
|
| D | calc2.cpp | 21 struct calculator_domain struct
57 : proto::extends<Expr, calculator_expression<Expr>, calculator_domain>
|
| /third_party/boost/libs/proto/doc/ |
| D | calculator.qbk | 133 struct calculator_domain
139 define. The `calculator_domain` is what informs Proto about our wrapper. It is used
147 : proto::extends<Expr, calculator<Expr>, calculator_domain>
150 proto::extends<Expr, calculator<Expr>, calculator_domain>
270 struct calculator_domain
275 parameter to the `proto::domain<>` template when defining `calculator_domain`. With
|
| D | front_end.qbk | 262 struct calculator_domain;
270 : proto::extends< Expr, calculator< Expr >, calculator_domain >
273 proto::extends< Expr, calculator< Expr >, calculator_domain >
334 BOOST_PROTO_EXTENDS(Expr, calculator<Expr>, calculator_domain)
360 BOOST_PROTO_BASIC_EXTENDS(Expr, calculator<Expr>, calculator_domain)
466 …n do that by specifying an expression generator when we define our `calculator_domain`, as follows:
468 // Define the calculator_domain we forward-declared above.
471 struct calculator_domain
482 struct calculator_domain
488 …d through unchanged. But since we've specified a generator above, `calculator_domain::operator()`…
[all …]
|
| D | back_end.qbk | 823 : proto::extends<Expr, calculator<Expr>, calculator_domain>
826 proto::extends<Expr, calculator<Expr>, calculator_domain>
|