4 ms·

"But they didn't go through and parse the code like we do. It couldn't tell you who else uses this particular function or repository." It may have, but perhaps

"But they didn't go through and parse the code like we do. It couldn't tell you who else uses this particular function or repository." It may have, but perhaps didn't present the UI for external users. Our internal version of Codesearch based on Grok (http://www.stanford.edu/class/ee380/Abstracts/121010.html http://www.stanford.edu/class/ee380/Abstracts/121010.html) is far more powerful and works just like an advanced IDE -> find usages, callers, implementors, overrides, all kinds of auditing/analysis layers too. Some Googlers practically live in Codesearch rather than use the local IDE indexing :)

AceJohnny2 12y ago
As someone stuck with CScope on Linux, I really really wish there were better alternatives for the wider world. (required features: works with C, query from terminal as well as from IDE (inc. Vim/Emacs), possibility to jump to func/type definition as well as callers/users) Codesearch is probably the largest reason I am jealous of my friends at Google.
- justinmk 12y ago
  > As someone stuck with CScope on Linux, I really really wish there were better alternatives Doesn't clang (using a frontend like YCM[1]) provide exactly that? [1] https://github.com/Valloric/YouCompleteMe https://github.com/Valloric/YouCompleteMe
  - AceJohnny2 12y ago
    I didn't know about this! Looks like there's some experimental support for Emacs out there... Thanks!