4 ms·
Sad to see Code Search go. I just tried a simple search for 'pthread_t' on both Koders (http://www.koders.com http://www.koders.com) and Krugle (http://opensear
by ch 15y ago
Sad to see Code Search go. I just tried a simple search for 'pthread_t' on both Koders (http://www.koders.com http://www.koders.com) and Krugle (http://opensearch.krugle.org http://opensearch.krugle.org). Both are mentioned elsewhere in the comments as possible alternatives.
Krugle found no results. Koders found results, but the response time was very large.
Both have a long way to go in being a viable Code Search replacement.
Hopefully Code Search just gets rolled into the primary Google search product.
NOTE:
I was just looking over the Koders results. It is tokenizing 'pthread_t' as 'pthread' 't', so the top results are not what I would consider useful. I'm sure I can change some settings to get proper tokenization for my languages identifiers, but that is more work up front.
- Uhhrrr 15y agoDouble quotes seem to stop it from tokenizing, e.g. "pthread_t".
- ch 15y agoYes, but in a code search engine it would make sense to not break words that are valid symbols in more programming languages than not. It's all about sensible defaults.
- gtani 15y agoThere's a lot of significance in function/method signatures and non-alphanum chars that google is getting to grips with (and hoogle/hayoo for haskell seems to be state of the art). Ruby Class#method, the (dozens or more) symbolic "operators" in scala, haskell, ocaml (which are generally functions, not operators). I think it's up to each language community to build those tools now.