#include <stdio.h>
#include <errno.h>
#include <stdlib.h>
+#include <stdint.h>
/* end standard C headers. */
%+
/* begin standard C++ headers. */
#else /* ! __cplusplus */
/* We're not in a C++ compiler, so by default,
- we generate traditional function defs, unless you explicitly ask
- for C99 defs. */
-
-#ifndef YY_NO_TRADITIONAL_FUNC_DEFS
-#ifndef YY_TRADITIONAL_FUNC_DEFS
-#define YY_TRADITIONAL_FUNC_DEFS
-#endif
-#endif
+ we generate C99 function defs, unless you explicitly ask
+ for traditional defs by defining YY_TRADITIONAL_FUNC_DEFS */
#if __STDC__
the scanning routine using a K&R-style/non-prototyped function
declaration, you must terminate the definition with a semi-colon (;).
-@code{flex} generates K&R-style function definitions by default. This is solely
-to support bootstrapping gcc on old systems. Worse, it prevents us from using
-any standard data types smaller than int (such as short, char, or bool) as
-function arguments. For this reason, future versions of @code{flex} may
-generate standard C99 code, leaving K&R-style functions to the historians.
-Currently, if you want C99 definitions, then you'll have to define
-@code{YY_NO_TRADITIONAL_FUNC_DEFS}.
+@code{flex} generates @samp{C99} function definitions by default. However flex
+does have the ability to generate obsolete, er, @samp{traditional}, function
+definitions. This is to support bootstrapping gcc on old systems.
+Unfortunately, traditional definitions prevent us from using any standard data
+types smaller than int (such as short, char, or bool) as function arguments.
+For this reason, future versions of @code{flex} may generate standard C99 code
+only, leaving K&R-style functions to the historians. Currently, if you do
+@strong{not} want @samp{C99} definitions, then you must define
+@code{YY_TRADITIONAL_FUNC_DEFS}.
@cindex stdin, default for yyin
Whenever @code{yylex()} is called, it scans tokens from the global input