Lines Matching refs:generated

7 /// the placement of their contents within the generated code at defined points
8 /// such as within the generated C header file.
30 /// variables that are local to the code generated for that rule. You can then reference them within
33 /// With the C target, the generated code is subject to the restrictions of C semantics and this
58 …ode>\@declarations</code> and <code>\@init</code> sections guarantees that your generated code will
64 /// to be placed at the start of each generated file, regardless of whether it is a .c or .h file. …
65 /// be useful for inserting copyright information and so on in all your generated files.
67 /// \bNOTE: Be careful not to confuse this concept with placing code in the generated .h header fil…
69 /// in generated java classes. We have therefore kept the intent of this section the same.
89 /// the code they encapsulate to be placed in the generated .h file, \b after the standard
90 /// includes required by the ANTLR generated code.
116 /// the code they encapsulate to be placed in the generated .h file, \b before the standard
117 /// includes required by the ANTLR generated code.
129 /// the code they encapsulate to be placed in the generated <b>.C</b> file, after the generated inc…
133 /// generated include and by the standard ANTLR3 includes. This is a good place to <code>\#undef</c…
137 …/ This is also a good place to <code>#define</code> any macros you may wish to use in the generated
139 /// generated .h file of each of them, possibly globally, but almost certainly in a context where y…