bison-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[PATCH 0/8] Various improvements prompted by api.prefix


From: Akim Demaille
Subject: [PATCH 0/8] Various improvements prompted by api.prefix
Date: Wed, 4 Jul 2012 16:52:56 +0200

The following changes were prompted more or less directly
by api.prefix.  Installed in maint.

Akim Demaille (8):
  tests: more logs.
     The tests were failing weirdly, and that was actually due
     to compiling with a given value of YYDEBUG, and including
     with another.
  glr.cc: formatting changes.
  c++: fewer #includes in the headers.
     The tests for api.prefix caught macros that were needlessly
     exported, and highlighted that some #includes were not needed.
  tests: portability fixes.
     Hydra showed issues with G++ 4.2.
  api.prefix: do not use #define to handle YYSTYPE_IS_TRIVIAL etc.
     The test suite revealed a severe weakness in the handling
     of YYSTYPE_IS_TRIVIAL's renaming via api.prefix.
  YYLLOC_DEFAULT: factor, and don't export it in headers.
     Was uselessly exported, and uselessly duplicated in the sources.
  glr.cc: do not override C++ definitions by C macros.
     The test for api.prefix, applied to glr.cc, has shown several
     weaknesses in the handling of the parse-params etc. due to
     c.m4's overriding c++.m4 insead of the converse.
  tests: headers.at: strengthen.
     This is the version of the api.prefix test that caught the
     previous issues.

 data/c++.m4      | 29 ++++++++++++++++++++++++++++
 data/c.m4        | 29 ++++++++++++++++++++++++++++
 data/glr.c       | 45 +++++++++++--------------------------------
 data/glr.cc      | 58 ++++++++++++++++++++------------------------------------
 data/lalr1.cc    | 33 ++++++++------------------------
 data/location.cc |  4 ++--
 data/yacc.c      | 42 ++++++++--------------------------------
 tests/headers.at | 41 +++++++++++++++++++++++++++------------
 8 files changed, 137 insertions(+), 144 deletions(-)

-- 
1.7.11.1




reply via email to

[Prev in Thread] Current Thread [Next in Thread]