[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bison 1.50 pre & post prologue bug
From: |
Akim Demaille |
Subject: |
Re: Bison 1.50 pre & post prologue bug |
Date: |
14 Oct 2002 10:43:09 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
| Bison 1.50 does not seem to handle the pre & post prologues properly; that
| is, when writing:
| %{
| pre_prologue
| %}
| ...
| %{
| post_prologue
| %}
| ...
| %%
| ...
| in the .y files as above, the b4_post_prologue macro expands to empty, and
| all stuff goes into the first b4_pre_prologue macro.
|
| -- I need this for writing my C++ skeleton file: Some stuff should then go
| into the header and other into the source file. This is often required with
| polymorphic classes and stuff relying on forward declarations, but also
| useful in order to decrease the number of headers that the header includes.
pre and post-prologue are implementation details. You should tell us
what the *real* problem is.
pre- and post-, as implementation details, are separated by %union.