Hello, Brian and all,
>If you have any urgent needs for the release, please speak up now.
the current "proof of concept" Inline::Yacc implements Inline::Yacc as
a subclass of Inline::C. It uses an own preparser, processes its
results, generates a yacc grammar with C actions and passes it to yacc.
Finally, it takes yacc's result, which is C code, and passes it as "C
input" to Inline::C to perform the remaining usual C/Perl binding
steps.
My point here is that I had to duplicate Inline::C code in
Inline::Yacc. It basically worked, but for future releases (and more
subclassing Inline:: modules) I ask for an interface which allows to
include additional "preparation" steps as described, without having to
copy parts from the parent module (which might be(come) subject to
changes).
This interface could possibly be cascaded and therefore made be
general. For example, there
might be another Inline::XY which wants to produce yacc code from
something inlined and therefore could be implemented as an Inline::Yacc
subclass to reuse existing code. (Even if this is not really probable,
you get the cascading idea ...)
Greetings
Jochen
