Lines Matching refs:terminals

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…
769 … domain, `proto::default_domain`. Even non-Proto objects are treated as terminals in the default d…
802 …e and a vector type, that you would like to treat as if they were Proto terminals? Proto usually t…
815 You can non-intrusively make objects of these types Proto terminals by defining the proper operator…
845         // objects as if they were Proto terminals.
849 …verloads that treat `matrix` and `vector` objects as if they were Proto terminals. And since the o…
857     m1 * v1; // two custom terminals are OK, too.