How to use eclipse cdt to build abstract syntax tree
The Boost libraries are excellent, don’t waste your time re-inventing a component in that library in all likelihood your component will not be as good anyway. Third, I use anything from the Boost library that suits my needs. For external interfaces I may expose a char* type but under the interface any char* will almost always map straight back to a std::string instance. Second, I use the std::string class in preference of char* strings almost exclusively. First, I use anything in the standard c++ library – in particular I do not write containers.
HOW TO USE ECLIPSE CDT TO BUILD ABSTRACT SYNTAX TREE CODE
The unit testing framework depends on the Google Test libraries.įor what it is worth, I’ve been writing C++ code for a long, long time and am somewhat opinionated regarding some development practices. The libraries are built with the C++11 language features and have dependencies on the Standard Library shipped with GCC and Boost libraries. The interfaces will settle down in time and I will ‘chill’ them at some point in hopefully the not too distant future.Īll of the libraries with the exception of the unit test library link directly with the GCC source code, therefore they are all licensed with GPL V3.0. NB – At the time of writing, I am going through successive revisions and refactoring passes on the library, so expect anything you build now to break with my next commit to GitHub. The libraries are available on Github: ‘stephanfr/GCCPlugin’. In this post I will provide a high level description of the libraries and walk through the dependencies and directory structures. As discussed in the prior post, I have started a set of C++ libraries to reduce the complexity of writing GCC Plugins and interpreting the GCC Abstract Syntax Tree.