Future posts: Parsing C++ using Eclipse CDT

Well, I've never really have been much into blogging. Never really had much enthusiasm to do it, but now I'm working in a project which I think deserves some posts.

I'll be writing in English, since this way the posts will be available to more readers than if I write them in Portuguese.

The next posts will be about parsing C++ using Eclipse CDT. Since everything I've read about parsing C++ consists of "frustrations", with people saying it's hard, ambiguous, etc. While these sentences are true, I'm not interested in parsing obscure c++, so I can stick with what CDT can handle.

I won't talk about LL(1) parsers, or anything related. I'll cover how to USE the CDT framework (which is written in Java) to get what I need.

All the projects of the company I work are written using the Borland 6 compiler. The project I'm engaging consists creating a "helper" to migrate from Borland C++ to Visual Studio C++.

There is a lot of GUI written using VCL. Visual Studio obviously doesn't support these files, so, instead of migrating towards another graphical toolkit, like QT, we'll keep all the Borland files and "communicate" with them using a DLL (which will have automatically generated C code).

To create this DLL and the other classes we need to parse the projects and the VCL files to know which symbols we need to generate code for.

So in the next posts I'll cover how I'm using the CDT framework to parse the C++ files.