Re: YYDEBUG and so forth

[Paul Hilfinger]

> We should really stop using YYDEBUG, YYERROR_VERBOSE and so forth in
> our skeletons.  yacc.c has to, since that specified by POSIX.  But the
> other skeletons should rely only on %directives.

Akim,

I'm not quite sure what you mean here.  If you are saying that we
ought to control the presence/absence of debugging code by
%directives, that's fine.  But one way to do that is to have
conditionalization code in the skeleton, controlled by symbols like
YYDEBUG, which are in turn set according to directives in the .y file.
The only difference with yacc.c is then that you don't document (and
therefore don't guarantee) that these symbols are present in the 
generated code.  They are simply parts of the implementation, in that case.

So perhaps you could clarify precisely what change you have in mind.

Paul



 > 
 > Hi Paul,
 > 
 > We should really stop using YYDEBUG, YYERROR_VERBOSE and so forth in
 > our skeletons.  yacc.c has to, since that specified by POSIX.  But the
 > other skeletons should rely only on %directives.