Intel XENIX 286 Programmers Guide (86) - Tenox.tc
Intel XENIX 286 Programmers Guide (86) - Tenox.tc Intel XENIX 286 Programmers Guide (86) - Tenox.tc
XENIX Programming yacc: Compiler-Compiler Old Features This section mentions synonyms and features supported for historical continuity, but that, for various reasons, are not encouraged. • Literals may also be delim ited by double quotation marks ("). • Literals may be more than one character long. If all the characters are alphabetic, nu meric, or underscore, the type number of the literal is defined, just as if the literal did not have the quotation marks around it. Otherwise, it is difficult to find the value for such literals. The use of multicharacter literals is likely to mislead those unfamiliar with yacc, since it suggests that yacc is doing a job that must be actually done by the lexical analyzer. • Most places where % is legal, backslash {\) may be used. In particular, the double backslash {\ \} is the same as 9696, \left the same as 96left, etc. • There are a number of other synonyms: 96< is the same as 96left 96> is the same as %right %binary and 962 are the same as 96nonassoc 960 and 96term are the same as %token 96= is the same as 96prec • Actions may also have the form = { . .. } and the curly braces can be dropped if the action is a single C statement. • C code between 96{ and 96} used to be permitted at the head of the rules section, as well as in the declaration section. 10-39
- Page 190 and 191: XENIX Programming lex: Lexical Anal
- Page 192 and 193: XENIX Programm ing lex: Lexical Ana
- Page 194 and 195: XENIX Programming Specifying Source
- Page 196 and 197: XENIX Programming lex: Lexical Anal
- Page 198 and 199: XENIX Programming lex: Lexical Anal
- Page 200 and 201: XENIX Programming The definitions s
- Page 202 and 203: CHAPTER 10 yacc: COMPILER-COMPILER
- Page 204 and 205: XENIX Programming yacc: Compiler-Co
- Page 206 and 207: XENIX Programming yacc: Compiler-Co
- Page 208 and 209: XENIX Programming yacc: Compiler-Co
- Page 210 and 211: XENIX Programming yacc: Compiler-Co
- Page 212 and 213: XENIX Programming yacc: Compiler-Co
- Page 214 and 215: XENIX Programming yacc: Compiler-Co
- Page 216 and 217: XENIX Programming yacc: Compiler-Co
- Page 218 and 219: XENIX Programming yacc: Compiler-Co
- Page 220 and 221: XENIX Programming yacc: Compiler-Co
- Page 222 and 223: XENIX Programming yacc: Compiler-Co
- Page 224 and 225: XENIX Programming yacc: Compiler-Co
- Page 226 and 227: XENIX Programming yacc: Compiler-Co
- Page 228 and 229: XENIX Programming yacc: Compiler-Co
- Page 230 and 231: XENIX Programming yacc: Compiler-Co
- Page 232 and 233: XENIX Programming yacc: Compiler-Co
- Page 234 and 235: XENIX Programming yacc: Compiler-Co
- Page 236 and 237: XENIX Programming %left %left %left
- Page 238 and 239: XENIX Programming I* lexical analys
- Page 242 and 243: CHAPTER 11 m4: MACRO PROCESSOR The
- Page 244 and 245: XENIX Programming m4: Macro Process
- Page 246 and 247: XENIX Programming m4: Macro Process
- Page 248 and 249: XENIX Programming m4: Macro Process
- Page 250 and 251: XENIX Programming m4: Macro Process
- Page 252 and 253: APPENDIX A C LANGUAGE PORTABILITY T
- Page 254 and 255: XENIX Programming This is preferabl
- Page 256 and 257: XENIX Programming C Language Portab
- Page 258 and 259: XENIX Programming C Language Portab
- Page 260 and 261: XENIX Programming C Language Portab
- Page 262 and 263: XENIX Programming C Language Portab
- Page 264: XENIX Programming C Language Portab
- Page 267 and 268: Programming Commands XENIX Programm
- Page 269 and 270: Programming Commands XENIX Programm
- Page 271 and 272: Programming Commands XENIX Programm
- Page 273 and 274: Programming Commands XENIX Programm
- Page 275 and 276: Programming Commands XENIX Programm
- Page 277 and 278: Programming Commands XENIX Programm
- Page 279 and 280: Programming Commands XENIX Programm
- Page 281 and 282: Programming Commands XENIX Programm
- Page 283 and 284: Programming Commands XENIX Programm
- Page 285 and 286: Programming Commands XENIX Programm
- Page 287 and 288: Programming Commands XENIX Programm
- Page 289 and 290: Programming Commands XENIX Programm
<strong>XENIX</strong> Programming yacc: Compiler-Compiler<br />
Old Features<br />
This section mentions synonyms and features supported for historical continuity, but<br />
that, for various reasons, are not encouraged.<br />
• Literals may also be delim ited by double quotation marks (").<br />
• Literals may be more than one character long. If all the characters are<br />
alphabetic, nu meric, or underscore, the type number of the literal is defined, just<br />
as if the literal did not have the quotation marks around it. Otherwise, it is<br />
difficult to find the value for such literals. The use of multicharacter literals is<br />
likely to mislead those unfamiliar with yacc, since it suggests that yacc is doing a<br />
job that must be actually done by the lexical analyzer.<br />
• Most places where % is legal, backslash {\) may be used. In particular, the double<br />
backslash {\ \} is the same as 9696, \left the same as 96left, e<strong>tc</strong>.<br />
• There are a number of other synonyms:<br />
96< is the same as 96left<br />
96> is the same as %right<br />
%binary and 962 are the same as 96nonassoc<br />
960 and 96term are the same as %token<br />
96= is the same as 96prec<br />
• Actions may also have the form<br />
= { .<br />
.. }<br />
and the curly braces can be dropped if the action is a single C statement.<br />
• C code between 96{ and 96} used to be permitted at the head of the rules section,<br />
as well as in the declaration section.<br />
10-39