Google Code Search Reveals Dark Corners 297
saccade.com writes, "The new Google Code Search isn't just for hackers sniffing for passwords. Jason Kottke and friends have discovered the new feature reveals all sorts of dark corners hidden in our code. And you thought nobody ever read your comments!" From the article: "Code search is a great resource for web developers and programmers, but like the making available of all previously unsearched bodies of information, it's given lots of flashlights to people interested in exploring dark corners."
google seems to inspire... (Score:5, Interesting)
Dark corners? (Score:5, Interesting)
Old-school (Score:5, Interesting)
Ahh frustrated programmers (Score:3, Interesting)
Fucks. (Score:5, Interesting)
Re:Dark corners? (Score:5, Interesting)
" but IE6's implementation fucks up the..."
"
Re:For the record (Score:3, Interesting)
No fun! (Score:3, Interesting)
Instead potential employers (like me) can google your code and read those comments that you wrote in there. Don't worry though... I won't hold those against you.
Anyway, "unless you really know what you're doing" and "smoking cracK" are also fun searchesa over there...
Favorite (Score:5, Interesting)
You are not expected... (Score:4, Interesting)
See here [bell-labs.com] for an explanation (from the horse's mouth, as it were...)
memset( pointer, size, 0 ) - NO! (Score:2, Interesting)
Re:Dark corners? (Score:5, Interesting)
Just better not SCO know about this
malloc(strlen(\w\)); (Score:2, Interesting)
and these new char[strlen(\w+)]; [google.com]
Re:And the Ever Popular... (Score:5, Interesting)
"guy who wrote this" [google.com] "in case some idiot" [google.com] "ugly hack" [google.com] "rewrite this later" [google.com] "hail mary" [google.com] "this shouldn't work" [google.com] "compiler happy" [google.com] "what the fuck" [google.com] "blows goats" [google.com]
And I really love this one: i=i++ [google.com]
Re:Wow. Just wow. (Score:3, Interesting)