FORK NOTES

The fork's main branch is called my-master (the default branch is still master which could be kept in sync with the parent repo's master). Every change made should have its own branch, DERIVED FROM master branch. Doing this would allow easy and isolated integration of each one of the branches into the original repository.

Branches

1. doxygen: Adds doxygen build target and its github action for automated deployment on repo's github pages.
2. reform-cmake-lib: Changes how the main cmake file adds the static library, allowing the projects that use cppparser to benefit from the modern CMake.
3. example-manual-ast: Adds examples/ to the source directory, including a example file demonstrating how to build AST maunally from nothing and generate the code from it using cppwriter.
4. feature-ast-visitor: Introduces CppVisitorBase, CppVisitorPrinter, and CppVisitorMatcher as simple-to-use visitors and AST-matchers.

CppParser

An easy, fast, and robust library to parse C/C++ source.

Features

• No pre-processing, and preprocessors are part of the ast.
• Most comments are preserved too.
• Developed from scratch and uses back-tracking yacc (BtYacc) to write C++ grammer, that means no dependency on libclang.
• The result of parsing is an AST where elements of a file are arranged in a tree.
• Minimum dependency. Only external dependency is a lexer which is by default available on unix like platforms and can be easily get on Windows.
• Parsing of multi-file program is supported too.

Motivation

CppParser can be used to build tools that need parsing of C/C++ files. I am using it to develop cib which implements ABI stable SDK architecture for C++ library.

Example

To begin with we will see an example of parsing a hello-world program and see what is the AST that CppParser creates:

 {c++}
#include <iostream>
 
int main()
{
  std::cout << "Hello World!\n";
 
  return 0;
}

For the above hello-world program we can expect that when it is parsed the generated AST should look like following:

So, how we are going to access these elements of AST using CppParser? Below is the program written as unit-test for validating the correctness of generated AST:

 {c++}
#include <catch/catch.hpp>
 
#include "cppparser.h"
 
#include <boost/filesystem.hpp>
 
namespace fs = boost::filesystem;
 
TEST_CASE("Parsing hello world program")
{
  CppParser  parser;
  const auto testFilePath = fs::path(__FILE__).parent_path() / "test-files/hello-world.cpp";
  const auto ast          = parser.parseFile(testFilePath.string());
  REQUIRE(ast != nullptr);
 
  const auto& members = ast->members();
  REQUIRE(members.size() == 2);
 
  CppIncludeEPtr hashInclude = members[0];
  REQUIRE(hashInclude);
  CHECK(hashInclude->name_ == "<iostream>");
 
  CppFunctionEPtr func = members[1];
  REQUIRE(func);
  CHECK(func->name_ == "main");
 
  REQUIRE(func->defn());
  const auto& mainBodyMembers = func->defn()->members();
  REQUIRE(mainBodyMembers.size() == 2);
 
  CppExprEPtr coutHelloWorld = mainBodyMembers[0];
  REQUIRE(coutHelloWorld);
  CHECK(coutHelloWorld->oper_ == CppOperator::kInsertion);
}

This example is a real one and is part of actual unit test of CppParser.

Building CppParser

Get the source

git clone https://github.com/satya-das/CppParser.git

Configure and build

cd cppparser
mkdir builds
cd builds
cmake ..
make && make test

Alternatively, if you prefer Ninja instead of make:

cd cppparser
mkdir builds
cd builds
cmake -G Ninja ..
ninja && ninja test