clisp uses custom preprocessors for C, so it keeps the sources in *.d files which actually contain C code. ohloh identifies then as written in "d programming language". I suggest a custom per-project map identifying which files are in which labguage, similar to the existing cvs uid map. e.g., I should be able to specify that *.l in clocc is actually lisp and *.d in clisp is actually C.
incorrect language identification
about 1 year ago
about 1 year ago
another example is the *.tst (regression tests) files in clisp, which are actually lisp files.
about 1 year ago
I like this a lot. We've discussed similar approaches in the past, it might be time for us to re-evaluate.
A twist to add here is that if we allow file GLOB specifiers we could potentially overlap another highly-requested feature: ignoring directories.
Example directives:
/test/*.tst : LISP <-- treat as LISP
/doc/* : NULL <-- ignore all files in the doc directory
The challenge here is how could ohloh support this in a manageable way (not cause too much stress on servers, how to limit the possibly blooming support requests, etc..). We'll talk about it today and report back on our position ;-).
about 1 year ago
note another usage: ignoring generated files: configure:NULL
about 1 year ago
I think generated files shouldn't be in source control anyway.
runs away before this becomes an argument
about 1 year ago
I think generated files shouldn't be in source control anyway.
let us not confuse normative and positive issues.