[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
FYI: [PATCH 4/4] doc: fix some invalid @ref
From: |
Akim Demaille |
Subject: |
FYI: [PATCH 4/4] doc: fix some invalid @ref |
Date: |
Sun, 8 Apr 2012 10:23:01 +0200 |
Installed in master, will cherry-pick in maint. This is
something I should write a syntax-check for.
From e3fd1dcb8b0b55525876440410f71791d8b4c2f3 Mon Sep 17 00:00:00 2001
From: Akim Demaille <address@hidden>
Date: Sun, 8 Apr 2012 10:17:58 +0200
Subject: [PATCH 4/4] doc: fix some invalid @ref.
* doc/bison.texinfo: Fix incorrect @ref uses.
---
doc/bison.texinfo | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 45125c1..5109009 100644
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -8241,7 +8241,7 @@ tune or simply fix a parser. Bison provides two different
representation of it, either textually or graphically (as a DOT file).
The textual file is generated when the options @option{--report} or
address@hidden are specified, see @xref{Invocation, , Invoking
address@hidden are specified, see @ref{Invocation, , Invoking
Bison}. Its name is made by removing @samp{.tab.c} or @samp{.c} from
the parser implementation file name, and adding @samp{.output}
instead. Therefore, if the grammar file is @file{foo.y}, then the
@@ -10610,7 +10610,7 @@ macros. Instead, they should be preceded by
@code{return} when they
appear in an action. The actual definition of these symbols is
opaque to the Bison grammar, and it might change in the future. The
only meaningful operation that you can do, is to return them.
-See @pxref{Java Action Features}.
address@hidden Action Features}.
Note that of these three symbols, only @code{YYACCEPT} and
@code{YYABORT} will cause a return from the @code{yyparse}
@@ -10626,8 +10626,8 @@ values have a common base type: @code{Object} or as
specified by
an union. The type of @code{$$}, even with angle brackets, is the base
type since Java casts are not allow on the left-hand side of assignments.
Also, @address@hidden and @code{@@@var{n}} are not allowed on the
-left-hand side of assignments. See @pxref{Java Semantic Values} and
address@hidden Action Features}.
+left-hand side of assignments. @xref{Java Semantic Values} and
address@hidden Action Features}.
@item
The prologue declarations have a different meaning than in C/C++ code.
@@ -10643,7 +10643,7 @@ blocks are placed inside the parser class.
@item @code{%code lexer}
blocks, if specified, should include the implementation of the
scanner. If there is no such block, the scanner can be any class
-that implements the appropriate interface (see @pxref{Java Scanner
+that implements the appropriate interface (@pxref{Java Scanner
Interface}).
@end table
--
1.7.9.5
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- FYI: [PATCH 4/4] doc: fix some invalid @ref,
Akim Demaille <=