On 11 Jan 2006, at 19:35, Paul Eggert wrote:
Hans Aberg <[EMAIL PROTECTED]> writes:
How is the work on synced Flex/Bison C++ skeletons progressing?
Sorry, I don't know what this refers to.
Specifically, I use my own Bison/Flex C++ skeletons, which require a
Bison tweak. The tweak is covered by a code placement %define. I want
to either switch to some official Flex/Bison C++ skeletons, or in the
wait for that, have a code placement %define.
The Bison developers, I think, decided to put off the code placement %
define implementation in favor of doing the C++ skeletons first. But
I am not sure of the state of the latter -- it could have been
stalled. A Bison C++ skeleton is not enough, if it cannot work
together with a Flex C++ skeleton. I am myself skeptical about trying
to make Flex/Bison skeletons without a code placement %define,
because there are several places one can place code in C++.
In addition, if I should use the Bison static typing mechanism
together with C++, I need a version of %union that triggers this
mechanism without implementing a C/C++ union. I suggested a name "%
typed", but the exact name is irrelevant.
I also get email from people on the Help-Bison list, wanting to know
how to use Bison with C++. All I can do is to refer to the ongoing
work by the Bison developers, and say that I use a C++ skeleton file
they cannot use, in view of the special Bison tweaks I use.
Hans Aberg