The following set of patches was prompted by the absence of
documentation about how mid-rule actions are translated, and in
particular, what $@1 and @1 mean when they appear in a report (text,
graph, xml, etc.).

Writing the documentation showed that some of our diagnostics were
using suboptimal locations about mid-rule actions, especially visibly
with -fcaret.

Compiling verbosely the PDF file also revealed several possible
improvements.  Plain reading did too.

Finally, some changes to please more compilers in more situations.

I'd really appreciate comments, especially about the new documentation
parts.  Will push in the next couple of days.

Akim Demaille (6):
  build: beware of Clang++ not supporting POSIXLY_CORRECT
  tests: be robust to C being compiled with a C++11 compiler
  tests: ignore more useless compiler warnings
  doc: various minor improvements and fixes
  error: use better locations for unused midrule values
  doc: explain how mid-rule actions are translated

 NEWS                    |  10 +-
 configure.ac            |   3 +-
 doc/Makefile.am         |   9 +-
 doc/bison.texi          | 346 +++++++++++++++++++++++++++++++++++-------------
 doc/figs/example.dot    |  35 +++++
 doc/figs/example.y      |   4 +
 m4/c-working.m4         |  42 +++---
 m4/cxx.m4               |   9 ++
 src/reader.c            |   4 +-
 tests/actions.at        |   8 +-
 tests/atlocal.in        |  34 +++--
 tests/glr-regression.at |  96 +++++++-------
 tests/input.at          | 143 ++++++++++++++------
 tests/local.at          |   4 +-
 tests/synclines.at      |   9 +-
 15 files changed, 528 insertions(+), 228 deletions(-)
 create mode 100644 doc/figs/example.dot
 create mode 100644 doc/figs/example.y

-- 
1.8.0.1


Reply via email to