flex (2.6.1-1.1) UNRELEASED; urgency=medium In this upload, the flex package drops its dependency on libfl-dev, because it is impossible to forward the correct architecture constraint. It contains the FlexLexer.h header and is thus required for using the FlexLexer C++ interface. Packages using this library need to add libfl-dev to their Build-Depends. -- Helmut Grohne Wed, 23 Nov 2016 13:18:32 +0100 flex (2.5.33-7) unstable; urgency=low This version of Flex is a major upgrade from previous versions. There have been extensive changes. These changes require source changes in lex input files. The new direction flex is taking is to incorporate new functionality at the expense of POSIX or backward compatibility. This can also be considered part of the gcc migration process; flex has been updated (the buggy, rickety set of patches required to make it work with gcc was dumped in favour of a well engineered upstream migration). Flex scanners are now reenterant, you may have multiple scanners in the same program with differing sets of defaults, and they play nicer with modern C and C++ compilers. C++ scanners are compatible with recent c++ compilers (conform to ANSI C++, gcc 3.2), supports bison variables yylval and yylloc. Some variables have been renamed. Flex generates C99 defs now, see YY_TRADITIONAL_FUNC_DEFS. yylineno is present in all scanners. yylineno is per-buffer in reentrant scanners. Flex tries its best to output only the relevant portions of the skeleton when generating a scanner, thus avoiding as much conditional compilation as possible The signature of all functions has changed. flex has new command line options, and option parsing has changed (now also supports POSIX conventions optionally). Handles POSIXLY_CORRECT environment variable. Various i18n translations are included in the distribution. Flex now works with recent bison versions. The new scanners do not polllute the global name space, and thus macros that used to be available to user code are no longer present. Flex has gained an extensive new test suite run at build time to test for regressions. The flip side is that Flex no longer conforms to the POSIX lex behaviour, and the scanners require conforming implementations when flex is used in ANSI C mode. Flex has broken backwards compatibility. This is not a bug, but done deliberately, by design. The package flex-old provides the same behaviour as version 2.5.4a of Flex. Please make sure you are prepared for these changes in Flex before continuing with its upgrade. -- Manoj Srivastava Fri, 31 Oct 2003 21:53:16 -0600