clang-ctags

number of operations on C-language source files." https://github.com/gmarpons/Crisp "A coding rule validation add-on for LLVM/clang. Crisp rules are written in Prolog. A high-level declarative DSL to easily write new rules is under development. It will be called CRISP, an acronym for Coding Rules in Sugared Prolog." https://github.com/drothlis/clang-ctags "Generate tag file for C++ source code." https://github.com/exclipy/clang_indexer "This is an indexer for C and C++ based on the libclang library." https://github.com/holtgrewe/linty "Linty - C/C++ Style Checking with Python & libclang." https://github.com/axw/cmonster "cmonster is a Python wrapper for the Clang C++ parser." https://github.com/rizsotto/Constantine "Constantine is a toy project to learn how to write clang plugin. Implements pseudo const analysis. Generates warnings about variables, which were declared without const qualifier." https://github.com/jessevdk/cldoc "cldoc is a Clang based documentation generator for C and C++. cldoc tries to solve the issue of writing C/C++ software documentation with a modern, non-intrusive and robust approach." https://github.com/AlexDenisov/ToyClangPlugin "The simplest Clang plugin implementing a semantic check for Objective-C. This example shows how to use the DiagnosticsEngine (emit warnings, errors, fixit hints). See also http://l.rw.rw/clang_plugin for step-by-step instructions." https://phabricator.kde.org/source/clazy "clazy is a compiler plugin which allows clang to understand Qt semantics. You get more than 50 Qt related compiler warnings, ranging from unneeded memory allocations to misusage of API, including fix-its for automatic refactoring." https://gerrit.libreoffice.org/gitweb?p=core.git;a=blob_plai... "LibreOffice uses a Clang plugin infrastructure to check during the build various things, some more, some less specific to the LibreOffice source code. There are currently around 50 such checkers, from flagging C-style casts and uses of reserved identifiers to ensuring that code adheres to lifecycle protocols for certain LibreOffice-specific classes. They may serve as examples for writing RecursiveASTVisitor-based plugins.""

end 50% of the time in C++, but the other 50% in shell, makefiles, python, etc. -- and the benefit of better C++ code navigation begins to seem like a micro-optimisation that isn't worth the tradeoff compared to Emacs's support for navigation, version control, compilation, linting, grepping, etc etc, all of which are consistent across all languages. Not to mention Emacs's great support for text manipulation in general. Also Emacs seems to me the best bet for the "one true editor" you'll still be using in 20 years (by which time hopefully few of us will still be using C++). I'll also point out that on OS X, Emacs has a lower learning curve than any other OS, at least as far as the basic keystrokes: OS X's Command key still works for the usual shortcuts (cut, copy, paste, save, open, quit, undo) while the quirky emacs bindings are on the Control and Option keys. This doesn't make it any easier to set up a C++ navigation solution, of course.

ore with Boost, and it works pretty well (i.e. gives correct completion candidates in a namespace). I used CEDET for getting completion candidates all the time in Boost.