Tobias Specht

I created a new issue for the external preprocessor and updated the issue description of #688. In this way we can better separate those two features.

Maybe "parsed" was misleading. Actually, I cannot distinguish between parsed by the CDT and persisted in the graph. What I have observed is, that everything inside the `extern` statement is...

I see your point with the license and the library. I'm still not sure, if the `csv` export should replace the `cpg-vis-neo4j` or if there should be something like `cpg-vis-csv`.

I had not yet time to run performance analysis on this PR. But I noticed a crash, which does not occur on current master. ``` git clone https://salsa.debian.org/sdl-team/libsdl-sge.git cpg-neo4j --no-neo4j...

> Thanks for the write up. I would avoid the term annotation. Basically it seems that `# 4 "main.c"` is a shorthand version of the #line preprocessor declaration https://docs.microsoft.com/en-us/cpp/preprocessor/hash-line-directive-c-cpp?view=msvc-170 Thanks...

I had some thoughts on tree-sitter and I think, I see more clear now. If I see correctly, the tree-sitter parse-tree can only be updated by reloading the source file....

Currently, the cpg handles macro resolution in the following way:  Code and file location are pointing to the un-resolved macro, but the node type and its specific properties (eg....

I just noticed, that tree-sitter is also not resolving everything correctly: https://github.com/tree-sitter/tree-sitter-c/issues/99 Did you also come along similar problems? I'm still not sure, if this is a bug or intended...

This does also apply to the cpp parser.

Thank you for the hint! That's basically what I'm looking for. As far as I can see, there are certain strategies defined for the visitor in `Strategy.java`: walking the EOG,...