Google Git
Sign in
plan9port / plan9 / 9e52ea8a29db42f37188fd8fa35d641724c3d015
commit9e52ea8a29db42f37188fd8fa35d641724c3d015[log] [tgz]
authorDan Cross <cross@gajendra.net>Thu Apr 20 21:35:23 2017 +0000
committerRuss Cox <rsc@swtch.com>Fri Apr 21 14:09:47 2017 +0000
treec09a7b1ac2d0b8ab98058f7e7fe5adaa0a29977b
parent94b38bdb722052838eb0d940c05995b870db4ea0 [diff]
yacc: Fix a bug from at least 1995.

Fix a bug folding newlines in strings constants in C code snippets
in YACC.  This code has existed since at least 2nd Edition Plan 9.

Change-Id: Iba17b89a6529ac9fa6610bf0b44f551904174c26
Signed-off-by: Dan Cross <cross@gajendra.net>
Reviewed-on: https://plan9port-review.googlesource.com/2840
Reviewed-by: Russ Cox <rsc@swtch.com>
1 file changed
tree: c09a7b1ac2d0b8ab98058f7e7fe5adaa0a29977b
  1. acid/
  2. bin/
  3. dict/
  4. dist/
  5. face/
  6. font/
  7. include/
  8. lib/
  9. log/
  10. lp/
  11. mac/
  12. mail/
  13. man/
  14. ndb/
  15. news/
  16. plumb/
  17. postscript/
  18. proto/
  19. sky/
  20. src/
  21. tmac/
  22. troff/
  23. unix/
  24. .gitignore
  25. CHANGES
  26. configure
  27. CONTRIBUTING.md
  28. CONTRIBUTORS
  29. INSTALL
  30. install.txt
  31. LICENSE
  32. Makefile
  33. rcmain
  34. README.md
  35. TODO
README.md

This is a port of many Plan 9 libraries and programs to Unix.

Installation

To install, run ./INSTALL. It builds mk and then uses mk to run the rest of the installation.

For more details, see install(1), at install.txt in this directory and at http://swtch.com/plan9port/man/man1/install.html.

Documentation

See http://swtch.com/plan9port/man/ for more documentation. (Documentation is also in this tree, but you need to run a successful install first. After that, “9 man 1 intro”.)

Intro(1) contains a list of man pages that describe new features or differences from Plan 9.

Helping out

If you'd like to help out, great! The TODO file contains a small list.

If you port this code to other architectures, please share your changes so others can benefit.

Please use codereview(1) to prepare patches.

Git

You can use Git to keep your local copy up-to-date as we make changes and fix bugs. See the git(1) man page here (“9 man git”) for details on using Git.

Contact