Re: yacc.c fix to avoid use of uninitialized variables in initial action

[Akim Demaille]

>>> "Paul" == Paul Eggert <address@hidden> writes:

 >> And this value is not used, it is copied.  A tool such as Valgrind
 >> makes the difference.

 > Sorry, I don't quite follow this point.

 > We didn't find the problem with valgrind.  The problem was found
 > because GCC 4 is smart enough to warn that yylloc is used without
 > being initialized, when the initial action doesn't set the line
 > number.

OK.  I meant that Valgrind is smarter (well, of course it can and GCC
cannot in general) and reports actual use of initialized _values_.
Here, it would only have complained if the value was truly used
(copying being merely propagating).

This patch is fine, but doesn't it apply to glr too?