Home | History | Annotate | Download | only in bison

Lines Matching full:prologue

874   A traditional Yacc prologue directive is written in the form:
889 "Prologue Alternatives" for a detailed discussion including the
890 advantages of %code over the traditional Yacc prologue directive.
1094 the traditional Yacc prologue blocks. Those have now been consolidated into
1105 manual for a summary of the new functionality. See the new section "Prologue
1109 The prologue alternatives are experimental. More user feedback will help to
1207 ** Handling of traditional Yacc prologue blocks is now more consistent but
1210 As before, you declare prologue blocks in your grammar file with the
1211 "%{ ... %}" syntax. To generate the pre-prologue, Bison concatenates all
1212 prologue blocks that you've declared before the first %union. To generate
1213 the post-prologue, Bison concatenates all prologue blocks that you've
1216 Previous releases of Bison inserted the pre-prologue into both the header
1223 Now, Bison never inserts the pre-prologue into the header file. In the code
1227 prologue blocks: %before-header, %start-header, %end-header, and
1236 /* Bison treats this block like a pre-prologue block: it inserts it into
1249 /* Unlike the traditional Yacc prologue blocks, the output order for the
1261 /* Bison treats this block like a post-prologue block: it inserts it into
1271 [Although we failed to mention this here in the 2.3a release, the prologue