[cdt-dev] Using the CDT Parser as a stand-alone module

[Rick Moseley <rmoseley@xxxxxxxxxx>]

Hi all,

I am on the development team of the open source project 
Frysk(http://sourceware.org/frysk) which is well into the process of 
designing/writing a new monitor/debugger to take advantage of the latest 
hardware/software technologies.  At the current time I am working on the 
UI part of Frysk(there is also a command-line side), specifically the 
source window view.

At the beginning of the Frysk project a couple of years ago we imported 
an older version, 2.0, of the CDT parser which we use to 
markup/highlight the keywords/macros/variables/etc. in our source window 
view.  While this parser has been fairly reliable, we have found a few 
problems and we would like to upgrade it to a newer model.  I understand 
that the latest CDT Parser is available to be used as a stand alone 
module and am very interested in importing it and having Frysk use it as 
its parsing engine.

I have read the documentation Mike Kucera posted to this list at the end 
of June and it has a lot of good information.  I was wondering if there 
was some information somewhere or if someone could give me some guidance 
about pulling the CDT Parser out of the CDT source proper and creating a 
stand alone module.  If there is other info around like how to use it, 
that would be helpful too.  As I said previously, at the current time we 
only use it for highlighting keywords/macros/variables/etc.

BTW, future plans for Frysk are to integrate it into the Eclipse CDT 
framework so it can be used as gdb is right now.  The main focus of 
Frysk for its initial release is for debugging C++ code and handling 
multi-threaded apps more gracefully.

Thanks in advance for any help you can render here.

Rick Moseley
rmoseley@xxxxxxxxxx