On Tue, 06 Nov 2012 21:22:17 +0100 Michael Stapelberg <stapelberg@debian.org> wrote: > > Another important step would be a way of excluding matches > > within comments from the results. > I have considered this, but when you think about it, identifiers > (variable names, function names, …) and comments are really are there is > searchable in source code. Could you give me a few convincing points on > why it would be useful to exclude comments (that is, examples)? Any search term which can be a variable name and frequently occurs in licence headers or doxygen markup or email addresses (copyright). (I dread to think what results come from searching just for 'debian', even with filetype:c it's all licence headers / email addresses.) http://codesearch.debian.net/search?q=QofBook+filetype%3Ac Any similar term which is frequently used across doxygen-style API docs will give a mix of comments and code. e.g. http://codesearch.debian.net/search?q=modify+filetype%3Ac That's just swamped by licences, as would be received and lots of other common words (which are, rightly or wrongly, used as variable names or as part of function names). Without exclusions on comments (and without fixes for filetype: matches below) then any common word is going to be swamped. > > The filetype seems a little confused in places too. Searching for > > things in filetype:perl I get matches in debian/control and > > debian/copyright. > Can you give me the exact query for which this happens, please? http://codesearch.debian.net/search?q=codehelp+filetype%3Aperl filetype:perl just doesn't seem to be working: http://codesearch.debian.net/search?q=QofBook+filetype%3Aperl ... lists a lot of .c files ... filetype:python does the same - some .py but then a lot more .c -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgp4qkXAw4xVm.pgp
Description: PGP signature