Thanks for installing that patch into Debian; that will simplify my life once it gets into Debian stable.
Here is some followup, which is now only of historical interest: Manoj Srivastava <[EMAIL PROTECTED] (va, manoj)> writes: > C89, however, is 16 years old now. C99 is 6 years old. How long > must we hold on to outdated and obsolete versions of the language? So long as any project that uses 'flex' wants to generate distributions that can be built by older compilers. To give you an idea of how long that might be, when operating in yacc mode, Bison still supports K&R C compilers, even though these have been obsolete since 1989. We are thinking of removing the K&R support from Bison next year, which would be about 17 years after C89 came out. But this is because we've done a preliminary survey of applications using Bison, and nobody cares about K&R C compilers any more. There are still a few people who care about porting to K&R C libraries like the SunOS 4.x library, so we'll continue to be be portable to those for a while longer; this is a separate issue from the compiler proper. (I also plan to ask on the Bison forums about this before making the change.) > I posted a report with the version of GCC shipping along > side the version of flex we are talking about: I'm more worried about the case where people like me build distributions on Debian stable, and people on less-advanced systems try to use their system's C compiler. Older GCC versions complain about the code in question, as do many non-GCC implementations that are still widely-used enough to cause bug reports to be sent to us. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
