Great ! I look into this. I'm curious to see how you integrated the parse=
r
with the symbol table. Though, to me it seems difficult to integrated the
symbol parsing with the symbol table (you need some tough 'undo' in case =
a
rule fails to match and has already made some change in the symbol table)=
.
Changing the examples stuff was the correct thing to do. The src/ don't h=
ave
unit test execution environment yet.
To debug C++ extension, you put something like:
Debug program:
python.exe
Argument:
E:\prg\vc\CppParser\src\pyrfta\dumpnodetree.py
E:\prg\vc\CppParser\src\pyrfta\samples\sources\declspec.h.tree
Working directory:
E:\prg\vc\CppParser\src\pyrfta
in the debugging tab of your c++ extension project.
Good luck with your second child ;-)
Baptiste.
----- Original Message -----=20
From: "Andre Baresel" <and...@gm...>
To: "CppTool Mailing List" <Cpp...@li...>;
"Baptiste Lepilleur" <gai...@fr...>
Sent: Friday, August 20, 2004 9:34 PM
Subject: Changes for symbol extraction by grammar keywords...
> Hello Baptiste,
>
> I checked in the proposed changes to the grammar for symbol extraction.
> A simple case the declaration of a class-id has been integrated into th=
e
> cpp_grammar.txt file
> and the symboldeclarator code for this part has been deactivated.
>
> I used the "example" branch since it runs fine with my vc6 and also
> debugging c++ problems
> from the running python environment was not yet comfortable for me yet.
> any suggestions ?
>
> greetings,
> from Andr=E9
>
> My holiday has ended today - we will see when i find time for some more
> coding.
> (will not be easy with my second child born now :-)
>
>
|
