From 5c9be03d6d7ccc5c8ad2ca47e8e767b37a3708b1 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Wed, 26 May 2004 17:45:45 +0000 Subject: [PATCH] Also mention that %union can depend on prerequisite types. --- doc/bison.texinfo | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/bison.texinfo b/doc/bison.texinfo index fe23e60..c1dcbd2 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -3745,10 +3745,12 @@ If the parser output file is named @file{@var{name}.c} then this file is named @file{@var{name}.h}. 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}. -- 2.7.4