Google Code Search team says Goodbye
groups.google.com
groups.google.com
See http://swtch.com/~rsc/regexp/regexp3.html for the original writeup from Russ.
Not possible. You have to parse the file fully to extract that information; regular expressions aren't powerful enough.
And for example, the regex engine from Perl 5.10 and up has had support for recursive patterns. See the faq: http://perldoc.perl.org/perlfaq6.html#Can-I-use-Perl-regular...
And once you have recursion support, you can parse context-free languages.
(And IIRC, the quote originated from a piece of code where jwz actually did use regexps quite a lot, if just to get enough performance out of elisp)
"There is something of a silver lining. googlecode.com will take over search for their projects, and also take over hosting the Chromium search page. (If ChromiumOS or Android are important to you, reach out to whatever contacts you have at Google now and let them know!)There is something of a silver lining. googlecode.com will take over search for their projects, and also take over hosting the Chromium search page. (If ChromiumOS or Android are important to you, reach out to whatever contacts you have at Google now and let them know!)"
edit: I assume they are referring to this http://www.google.com/codesearch/p?hl=en#uX1GffpyOZk/core/ja...
I use it, and I know other people do, to find software exploits. For eg. here is a search to find open source software that trusts the X-Forwarded-For HTTP request header:
http://www.google.com/codesearch#search/&q=%22X_FORWARDE...
http://koders.com/default.aspx?s=%22X_FORWARDED_FOR%22&s...
I hope GitHub implement their own code search now
The plus side is that the team could reflect honestly (and in public). At some companies, commenting publicly would be a career limiting move.
I can't help but feel that this is part of a bigger reaction which itself will slowly kill the company as Google loses its way.
Was a public reason ever given besides "streamlining" ? If Google's business is getting eyeballs, you'd think an already built service would be a no-brainer to keep in maintenance mode. I can't imagine it used so many resources as to make it a net-negative, but perhaps I'm wrong.
"Google’s mission is to organize the world‘s information and make it universally accessible and useful."
My arse.
With source code becoming increasingly available and important, and already in a structured format, this goes completely against the above statement.