Yacc Parsers

How to properly release heap-based symbols in a POSIX-compliant parser generated by Yacc? Standard Yacc does not support the convenient %destructor directive present in modern versions of GNU Bison.

The only possible alternatives I see in this behalf are:
    - Avoid heap allocation and use static allocation; (easy but bad)
    - Provide some means to save every allocated pointer during grammar traversal in some context and release the pointers appropriately afterwards; (boring to implement, bloats the code, not worth the hassle)
    - Use some pool allocator. (Inconvenient and yield pointers without free()-semantics)

Suggestions are appreciated.

use bison

easy but bad
Why? If it works, use it.

>>2
I want it to be compliant instead of relying on the presence of the GNU toolchain. Specifically I want it to work on byacc (and possibly other implementations).

>>3
It is hard to predict a reasonable limit. Any reasonable (for example, some KBs for a string, to be conservative) amount will be harmful in several ways; specially harmful if the generated parser creates (that is, declares in its generated code) symbols unnecessarily in its scope and the data is declared to be large enough to contain some expected values during runtime, trashing the stack to a large extent, and creating incredible overhead due to copying (since you cannot manipulate pointers).

not anime