Repository is up.
git clone https://github.com/alpha0010/ClangLib.githttps://github.com/alpha0010/ClangLib
Please copy the attached image into src/devel/share/codeblocks/images/codecompletion/
Btw, when do we get the merge of your cc branch into trunk?
From what I can tell, it runs as stable as the trunk (I am using the cc_interface branch as my main code editor). Part of my purpose with testing this Clang plugin is to see if any obvious changes must be made to the interface.
My thoughts are, merge the branch once the interface works without losing any features from the main CC plugin (done), tests from this Clang plugin (in progress...), and the FortranProject (not yet looked at). If we merge before these are complete, the interface would be likely to change soon after (defeating the purpose of working in a branch).
That said, my ideal target is one/two months (which depends a lot on how easy porting the FortranProject turns out to be).
Never understood how clang's CC works in terms of finding symbols outside of local file scope.
The way it is set up, Clang essentially compiles the file (into memory), so all of the #include
s are resolved and expanded. Searches are done per translation unit, not per file (which does mean I had to do a bit of file trickery in this plugin).