bison-patches
[Top][All Lists]
Advanced

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

Patch queue at Savannah


From: Tim Landscheidt
Subject: Patch queue at Savannah
Date: Sat, 17 Mar 2012 18:02:44 +0000
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)

Hi,

Savannah's Bison page has some very old patches
(<URI:https://savannah.gnu.org/patch/?group=bison>).  Four
are IMHO completely obsolete:

- "vcg.c layoutalgorithm": "--graph" now outputs dot files.

- "xvcg-1.3 graph output validation testtool": Dito (very
  sad for the code though :-)).

- "Wrong type in C++ skeleton": Fixed independently with
  0f0e1a.

- "stack::height return type is wrong for 64-bit environ-
  ment": Fixed independently with 56017c.

One has been partly obsoleted:

- "bison.texinfo fixes": Attached is a rework that applies
  to HEAD.

One has been superseded (I think):

- "A polymorphic YYSTYPE for C++ (instead of the %union)":
  This seems to be covered now by "C++ Variants".

This gives one remaining:

- "Warning/Error format compatible with Visual Studio": Ba-
  sically, the patch author wants to replace Bison's loca-
  tion format in error messages from the GNU Coding Stand-
  ards':

  | sourcefile:lineno:column

  to:

  | sourcefile(lineno) : column

  to please his IDE.

I have insufficient karma to close the reports myself.

Tim
>From 55cbc57ef4edf66b0cd3f95834db91f345081aad Mon Sep 17 00:00:00 2001
From: Tim Landscheidt <address@hidden>
Date: Sat, 17 Mar 2012 03:27:38 +0000
Subject: [PATCH] Patch #4306.

---
 doc/bison.texinfo |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index d24d0c6..4850f07 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -8328,7 +8328,7 @@ exp (9)
 Bison then proceeds onto the automaton itself, describing each state
 with it set of @dfn{items}, also known as @dfn{pointed rules}.  Each
 item is a production rule together with a point (marked by @samp{.})
-that the input cursor.
+for the input cursor.
 
 @example
 state 0
@@ -8358,7 +8358,7 @@ report lists @code{NUM} as a lookahead token because 
@code{NUM} can be
 at the beginning of any rule deriving an @code{exp}.  By default Bison
 reports the so-called @dfn{core} or @dfn{kernel} of the item set, but if
 you want to see more detail you can invoke @command{bison} with
address@hidden to list all the items, include those that can
address@hidden to list all the items, including those that can
 be derived:
 
 @example
@@ -8411,7 +8411,7 @@ state 2
 
 @noindent
 In state 2, the automaton can only shift a symbol.  For instance,
-because of the item @samp{exp -> exp . '+' exp}, if the lookahead if
+because of the item @samp{exp -> exp . '+' exp}, if the lookahead is
 @samp{+}, it will be shifted on the parse stack, and the automaton
 control will jump to state 4, corresponding to the item @samp{exp -> exp
 '+' . exp}.  Since there is no default action, any other token than
-- 
1.6.2.5


reply via email to

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