X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f X-Authentication-Warning: kendall.sfbr.org: jeffw set sender to jeffw AT darwin DOT sfbr DOT org using -f Date: Mon, 25 Feb 2002 14:25:33 -0600 From: JT Williams To: djgpp AT delorie DOT com Cc: bug-bison AT gnu DOT org Subject: Re: ANNOUNCE: DJGPP port of GNU bison 1.33 uploaded Message-ID: <20020225142533.A15413@kendall.sfbr.org> Mail-Followup-To: djgpp AT delorie DOT com, bug-bison AT gnu DOT org References: <200202221724 DOT g1MHOpQ10770 AT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200202221724.g1MHOpQ10770@delorie.com>; from ST001906@HRZ1.HRZ.TU-Darmstadt.De on Fri, Feb 22, 2002 at 03:17:50PM +0100 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk In the latest bison (1.33), something has changed with YYDEBUG. It appears that YYDEBUG is now #define'd (to 0?) when it used to be left #undef'ed. Thus, the following block #ifdef YYDEBUG ... #endif was (correctly) skipped in pre-1.33 bison (`bison -d -y foo.y') but with bison 1.33 this block is now entered (even when debugging support is not requested). Changing `#ifdef YYDEBUG' to `#if YYDEBUG' in your bison .y sources appears to be required user-level adjustment. (I checked, and the only two .y files in the djgpp distro do not use YYDEBUG and compile okay with 1.33.) The YYDEBUG change is Posix-mandated: the bison 1.33 NEWS file reports: * When the generated parser lacks debugging code, YYDEBUG is now 0 (as POSIX requires) instead of being undefined. This entry was made for bison 1.31 (not ported to djgpp). Due to the bug in bison 1.32 I continued to use bison 1.30 and so did not encounter the YYDEBUG snafu. I have not tried the corrected bison 1.32 port, but presumably it will now show the same behavior as 1.33.