On Monday, December 28, 2015 04:37:47 PM Thomas Lübking wrote: > On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote: > > Lxr can't search across every open source project in the world, so that's > > a > > point for Google. > > Presuming google could, why would I. Or anyone? > I dig for certain variables or strings in specific code, but why would I > look for m_foo or "SomeSetting" "across every open source project in the > world"? Lower STR? Search who copied "my" code?
Are you aware that not even every KDE developer knows about LXR? I constantly have to tell people about it. Now consider someone outside of KDE even, trying to figure out where KAwesomeClass is defined, or how it is implemented quickly -> bummer. (right now there's api.kde.org, which at least gives results about signatures, but the content of the .cpp or .h files are not indexed afaics) So having KDE source code indexed by Google would be definitely a win for everyone. It being linked back to LXR even more (=> people learn LXR exists when googling for KDE source code) Cheers, Kevin > Don't get me wrong, I don't care if anyone can - fine. But the inability > doesn't exactly like shooting yourself. > > Shrug, > Thomas > > >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe > >> << -- Kevin Funk | kf...@kde.org | http://kfunk.org
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
