Lines Matching refs:ACTION

54 ACTION(name) { statements; }
62 ACTION(IncrementArg1) { return ++(*arg1); }
77 ACTION(Foo) {
89 pre-defined symbols in the body of `ACTION`:
99 For example, when using an `ACTION` as a stub action for mock function:
157 You can view `ACTION` as a degenerated parameterized action where the
172 For maximum brevity and reusability, the `ACTION*` macros don't let
179 ACTION(Foo) {
196 ### Using the ACTION Object's Type ###
198 If you are writing a function that returns an `ACTION` object, you'll
203 | `ACTION(Foo)`            | `Foo()`                      | `FooAction`              |
227 As you may have realized, the `ACTION*` macros resemble closures (also
242 `ACTION*` avoid all these problems.
246 There may be a need for composing `ACTION*` definitions (i.e. invoking
247 another `ACTION` inside the definition of one `ACTION*`).  We are not
249 `ACTION` definitions in function templates and composing the function
252 The reason we don't allow `ACTION*()` inside a function body is that
256 can revisit the implementation and add support for using `ACTION*()`