Lines Matching full:code
7 /// the placement of their contents within the generated code at defined points
12 /// \code
28 /// Java targeted grammars allow the special section <code>\@init</code> to be placed after the declaration
30 /// variables that are local to the code generated for that rule. You can then reference them within
31 /// your rule action code.
33 /// With the C target, the generated code is subject to the restrictions of C semantics and this
35 /// <code>\@init</code> section, which C programmers should use to initialize their local variables, the C
36 /// target provides the <code>\@declarations</code> section, which is also a rule based section. This section
40 /// \code
58 /// Using the <code>\@declarations</code> and <code>\@init</code> sections guarantees that your generated code will
59 /// compile correctly on any standard C compiler (assuming, of course, that you type in valid C code.)
63 /// The <code>\@parser::header</code> or <code>\@lexer::header</code> annotations cause the code they encapsulate
67 /// \bNOTE: Be careful not to confuse this concept with placing code in the generated .h header file. The name choice is
73 /// \code
88 /// The <code>\@parser::includes</code> or <code>\@lexer::includes</code> annotations cause
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.
92 /// Here you could for instance place a <code>\#include</code>
93 /// statement to cause your grammar code to include some standard definitions. Because you
95 /// <code>#define</code> statements here, but in the <code>\@postinclude</code> section. Then you
96 /// may create different <code>\#defines</code> for different recognizers.
100 /// \code
115 /// The <code>\@parser::preincludes</code> or <code>\@lexer::preincludes</code> annotations cause
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.
120 /// in the code before the standard ANTLR runtime includes defined them. This allows you
123 /// special version of malloc, you can <code>\#define</code> #ANTLR3_MALLOC to match the definition
128 /// The <code>\@parser::postinclude</code> or <code>\@lexer::postinclude</code> annotations cause
129 /// the code they encapsulate to be placed in the generated <b>.C</b> file, after the generated include
132 /// Code you place here then will be subject to any macros defined by your own includes, by the
133 /// generated include and by the standard ANTLR3 includes. This is a good place to <code>\#undef</code>
137 /// This is also a good place to <code>#define</code> any macros you may wish to use in the generated
