Re: %destructor feedback

[Paul Eggert]

"Joel E. Denny" <address@hidden> writes:

> Providing the user with macros to combat compiler and lint warnings in 
> user code doesn't seem like a job that bison should take on.  However, 
> providing the user with macros to combat bison warnings does.  Thus, I 
> still vote that these should be distinct macros with distinct purposes.

If I'm not mistaken, they should be two macros with two meanings.
YYUSE(E) might actually evaluate E, whereas the macro to combat Bison
warnings should always discard its argument without evaluating it.

Has anyone suggested a name for the new macro?  If not, how about this one?

#define YYUCK(e) /* empty */

The idea being that people should never want to actually use this macro....

OK, so I'm not entirely serious here.  But what would the macro
actually be used for?  I've lost context.