Bison, yystpcpy, yystrlen

[Akim Demaille]

Hi Paul,

When running the test suite in paranoid mode (./configure
--enable-gcc-warnings), there is a problem in the parsers, revealed by



## --------------------------- ##
## GNU Bison 1.30f test suite. ##
## --------------------------- ##
31. torture.at:83: testing Exploding the Stack Size with Alloca...
torture.at:85: bison input.y -o input.c
torture.at:85: $CC $CFLAGS $CPPFLAGS input.c -o input
stderr:
cc1: warnings being treated as errors
/home/lrde/prof/akim/src/bison-1.29/src/bison.simple:307: warning: function 
declaration isn't a prototype
torture.at:85: exit code was 1, expected 0
31. torture.at:83: FAILED near `torture.at:85'

32. torture.at:104: testing Exploding the Stack Size with Malloc...
torture.at:106: bison input.y -o input.c
torture.at:106: $CC $CFLAGS $CPPFLAGS input.c -o input
stderr:
cc1: warnings being treated as errors
/home/lrde/prof/akim/src/bison-1.29/src/bison.simple:307: warning: function 
declaration isn't a prototype
torture.at:106: exit code was 1, expected 0
32. torture.at:104: FAILED near `torture.at:106'



The problem is that the static functions yystpcpy etc., which are used
if not found on the system, are not defined in ANSI.  Therefore, even
though they are static, GCC warns since they have not been declared.

I don't know what is the best path to warning-free parsers.

I tend to believe we do have to avoid all the warnings: by the past,
Bison had to face way too many bugs reports because of warnings.