Re: Bison H file generation

[Paul Eggert]

Tim Van Holder <address@hidden> writes:

> This also applies to cases where %union uses a type defined elsewhere,
> not only to user definitions of YYSTYPE.

Thanks; I installed this further patch.

2004-05-26  Paul Eggert  <address@hidden>

        * doc/bison.texinfo (Decl Summary): Also mention that %union
        can depend on prerequisite types.  Problem reported by Tim
        Van Holder.

--- bison.texinfo.~1.123.~      2004-05-25 12:01:29 -0700
+++ bison.texinfo       2004-05-26 10:37:56 -0700
@@ -3745,10 +3745,12 @@ If the parser output file is named @file
 is named @address@hidden
 
 Unless @code{YYSTYPE} is already defined as a macro, the output header
-declares @code{YYSTYPE}.  Therefore, if you have defined a
+declares @code{YYSTYPE}.  Therefore, if you are using a @code{%union}
+(@pxref{Multiple Types, ,More Than One Value Type}) with components
+that require other definitions, or if you have defined a
 @code{YYSTYPE} macro (@pxref{Value Type, ,Data Types of Semantic
-Values}) you need to arrange for this definition to be propagated to
-all modules, e.g., by putting the macro definition in another,
+Values}), you need to arrange for these definitions to be propagated to
+all modules, e.g., by putting them in a
 prerequisite header that is included both by your parser and by any
 other module that needs @code{YYSTYPE}.