Click here to Skip to main content
15,885,757 members
Articles / Programming Languages / C#

Parse C++ header and CPP files for class names and their methods

Rate me:
Please Sign up or sign in to vote.
3.63/5 (6 votes)
19 Feb 2009CPOL1 min read 38.5K   818   13   3
Parsing C++ header and CPP files for class names and methods.

CodeCoverage1

Introduction

This tool parses out your classes and their methods from header and CPP files. It turns out parsing out classes and methods in your C++ projects is actually very easy (if you don't need it to be life or death accurate). I'm not sure this is particularly useful; I had a specific use for this, and I just found it kind of interesting how easy it was. I'm sorry the formatting is wrong here, but CodeProject ate my whole article twice now, so I'm sorry!

Within our loop of headers and the lines in those headers, we simply check for the following; all other lines will be added and parsed later:

C#
if (lines[lineCount].Contains(@"//"))
{
    continue;
}

if (lines[lineCount].Contains(@"friend"))
{
    continue;
}

if (lines[lineCount].Replace(" ", "").Contains(@"template<class"))
{
    continue;
}

if (lines[lineCount].Contains(@"_T("))
{
    continue;
}

To parse the CPP, your loop will exclude only these keywords (I know I'm missing tons of cases here, but surprisingly it seems to work not too shabby :)):

C#
if (lines[lineCount].Contains(@";"))
{
    continue;
}

if (lines[lineCount].Contains(@"//"))
{
    continue;
}

if (lines[lineCount].Contains(@"_T("))
{
    continue;
}

if (lines[lineCount].Contains(@"if"))
{
    continue;
}

if (lines[lineCount].Contains(@"="))
{
    continue;
}

if (lines[lineCount].Contains(@"."))
{
    continue;
}

if (lines[lineCount].Contains(@"."))
{
    continue;
}

if (lines[lineCount].Contains(@"return"))
{
    continue;
}

Obviously, there is a lot missing to make this useful for most people, but it is kind of interesting and perhaps could be used as a learning tool. Also, you could structure this code much cleaner by searching for exclusion keywords and having them in a list, that might be a good exercise for someone.

It also should check for duplicates to handle overloaded methods and many more such issues.

Cheers..

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Software Developer (Senior)
Canada Canada
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions

 
QuestionWhy are we only parsing the header files ? Pin
Member 1388370012-Jul-18 0:24
Member 1388370012-Jul-18 0:24 
GeneralMy vote of 1 PinPopular
wtwhite23-Feb-09 17:37
wtwhite23-Feb-09 17:37 
GeneralRe: My vote of 1 Pin
rj4525-Feb-09 15:09
rj4525-Feb-09 15:09 
I do like that you said why you gave this a one and I agree with your points but I'm not sure it deserves a one simply because this is kind of interesting IMHO. Honestly, to write a parser that is real would probably have hundreds if not thousands of nested cases. It wouldn't be as useful at that point either because the inherent complexity

Like I said in the intro, this is just a starting point for an exercise, albeit not a good one for many applications. This might be a good starting point for doing something like opening a .cpp file in visual studio by clicking on a line in your logs or something. Obviously you'll find a bunch of issues along the way no matter what you do and I said that right up front. The task of parsing a directory for all classes/methods is interesting despite how dirty the code is. Hopefully someone will write a better one.


Thanks,
R.J.

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.