Include cscope?

[MichaelAgarkov]

Vim supports cscope out-of-the-box, and can also be used for C++ code.

[skeeto]

When I looked into it years ago, I saw there wasn't a native Windows port and didn't investigate further. However, I just took a closer look, and a port is more feasible than I realized. It requires POSIX regex which I've since solved (#127), and PDCurses is already a dependency for GDB. It also needs fork() and some other unix functions, but the existing DOS (djgpp) port covers nearly all of that, and the DOS port be extended to Windows. So PCRE2 with contrib/libregex.c, PDCurses, and a patch with a handful of changes to port to Windows ought to do it. That all even builds natively in w64devkit itself, too. I still need to consider whether I'd want to include cscope, but it shouldn't be blocked by a technical problem.

[N-R-K]

The main reason I use cscope over ctags (IIRC) is that it allows listing all the places where a symbol occurs along with all the places where a function is called. It's not perfect, since it seems to (?) operate at a textual level and not at a AST level (i.e macros, pointers etc will fool it) but it's better than nothing compared to ctags which only lets you jump to definition.

And while vim does have builtin support for cscope (note that neovim has removed it) I find the interface quite intrusive. I personally use quickr-cscope plugin which has no-nonsense interface that populates the quickfixlist and lets me work at my own pace without any annoying interactive ui popups.

As for including cscope in w64devkit, it wouldn't make much difference to me personally. I try to do most of the editing in my linux machine while using w64dk mainly as a way to compile/test the result.