Source code of Windows XP (NT5)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

46 lines
2.0 KiB

  1. The -r option has been implemented. The -r option tells Yacc to
  2. put the read-only tables in y.tab.c and the code and variables in
  3. y.code.c. Keith Bostic asked for this option so that :yyfix could be
  4. eliminated.
  5. The -l and -t options have been implemented. The -l option tells
  6. Yacc not to include #line directives in the code it produces. The -t
  7. option causes debugging code to be included in the compiled parser.
  8. The code for error recovery has been changed to implement the same
  9. algorithm as AT&T Yacc. There will still be differences in the way
  10. error recovery works because AT&T Yacc uses more default reductions
  11. than Berkeley Yacc.
  12. The environment variable TMPDIR determines the directory where
  13. temporary files will be created. If TMPDIR is defined, temporary files
  14. will be created in the directory whose pathname is the value of TMPDIR.
  15. By default, temporary files are created in /tmp.
  16. The keywords are now case-insensitive. For example, %nonassoc,
  17. %NONASSOC, %NonAssoc, and %nOnAsSoC are all equivalent.
  18. Commas and semicolons that are not part of C code are treated as
  19. commentary.
  20. Line-end comments, as in BCPL, are permitted. Line-end comments
  21. begin with // and end at the next end-of-line. Line-end comments are
  22. permitted in C code; they are converted to C comments on output.
  23. The form of y.output files has been changed to look more like
  24. those produced by AT&T Yacc.
  25. A new kind of declaration has been added. The form of the declaration
  26. is
  27. %ident string
  28. where string is a sequence of characters begining with a double quote
  29. and ending with either a double quote or the next end-of-line, whichever
  30. comes first. The declaration will cause a #ident directive to be written
  31. near the start of the output file.
  32. If a parser has been compiled with debugging code, that code can be
  33. enabled by setting an environment variable. If the environment variable
  34. YYDEBUG is set to 0, debugging output is suppressed. If it is set to 1,
  35. debugging output is written to standard output.