Lines Matching refs:terminals

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
593     // A simple Proto grammar that matches all terminals
616     // "Value" also defines a function object that accepts terminals
674 …and since the first alternate handles all terminals, the second alternate handles all (and only) n…
686 In the grammar defined in the preceding section, the transform associated with non-terminals is a l…
709 The very first transform we looked at simply extracted the value of terminals. Let's do the same th…
711     // A simple Proto grammar that matches all terminals,
898     // Fold the terminals in output statements like
907             // Put all other terminals at the head of the
993     // Fold the terminals in output statements like
1002             // Put all other terminals at the head of the
1103 …arameters. Let's take another look at the transform associated with non-terminals from the last se…
1198             // Evaluate terminals by simply returning their value
1201             // Non-terminals are handled by unpacking the expression,
1210 …l` algorithm at the bottom. Terminals are handled quite simply, but non-terminals could be unary, …
1212 Non-terminals are evaluated with this callable transform:
1252 … front end that defines a domain, a grammar, an expression wrapper, and some placeholder terminals.