On 8 Jun 2011, at 23:38, Panayiotis Karabassis wrote:
>> You can put code in various locations; see the %code directive, sec. 3.7.14.
>> You might even tweak the skeleton file to define more code places, but then
>> you may have to patch when the original is changed with new Bison releases.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2011 11:29 PM, Hans Aberg wrote:
> [Please keep the cc to the Bison Help list, so that others can follow the
> issue.]
Sorry about that, I hit the wrong button. I resent the message to the list.
> You can put code in various locations; see
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/26/2011 02:06 AM, Hans Aberg wrote:
>
> On 23 May 2011, at 09:40, Panayiotis Karabassis wrote:
>
>> What is the recommended way to get extra declarations in y.tab.h (in my
>> case Parser.h) for a C++ parser?
>
> Have you checked the Bison manual,
[Please keep the cc to the Bison Help list, so that others can follow the
issue.]
On 8 Jun 2011, at 21:48, Panayiotis Karabassis wrote:
>>> What is the recommended way to get extra declarations in y.tab.h (in my
>>> case Parser.h) for a C++ parser?
>>
>> Have you checked the Bison manual, sec.
On 23 May 2011, at 09:40, Panayiotis Karabassis wrote:
> What is the recommended way to get extra declarations in y.tab.h (in my
> case Parser.h) for a C++ parser?
Have you checked the Bison manual, sec. 10.1.6 A Complete C++ Example? One can
put it into a new header and include the header.
Ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
What is the recommended way to get extra declarations in y.tab.h (in my
case Parser.h) for a C++ parser?
Currently I have wrapped y.tab.h in my own header file and use that, but
it does not seem very elegant.
- --
Best regards,
Panayiotis K
