How can I scan C++ source codes to purge it?

By -

Suppose there is an extensive C++ framework. This framework has multiple modules. I need to develop a tool that can scan all *.cpp, *.h, *.hpp files in the framework, isolate files relevant to one executable, and then remove all source code from those files that are not needed for compiling a specified executable.

For example, the framework has modules for querying relational databases, Document databases, Key-value stores, Column-oriented databases, and Graph databases.

I want to isolate only those files relevant to relational databases, and then I want to remove all those codes not used in relational databases.

Say the framework has a file format_string.hpp. This file contains 73 functions that can format strings in various ways. However, the relational database-related module uses only 15 functions from that file. So, I want to remove the rest of the 58 functions from that file.

Note: I often need to study C++ source codes and translate/convert that source code into other programming languages. This tool will help me understand the algorithms.

The deletion/purge is not permanent. It is only for learning purposes. This is about reducing the amount of source code for further manual inspection.

Question:

I have implemented the file-isolation part using C#.

However, I don't know how to implement the second part.

Do I need to use regex? Or do I need a lexer and a parser?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more