| Commit message (Collapse) | Author | Files | Lines |
|
also don't keep adjusted maps around if not necessary
|
|
(also some evaluateNF, leading to slightly less memory usage)
|
|
as per yesterday's discussion about extended scripting variables
|
|
|
|
So far i've never found an instance of -Wname-shadowing telling me
anything useful, so it's disabled now, and most of the other trivial
ones are fixed.
(I assume this means I'll need -Wname-shadowing in about a day or two to
find some bug ...)
|
|
|
|
|
|
|
|
(the format used last year is no longer applicable to this year's event)
|
|
this allows for creating custom URI "schemas" in the linter's config,
which may be either allowed, prefixed, or translated according to
some (domain-based) substitution.
|
|
(these use a rather crude regex for parsing, which may be possible to
side-step, and which should probably be replaced by something that was
actually written while following the relevant rfc)
|
|
This is purely based on a set difference, i.e. it won't catch stupid
things like a map linking to itself, a map link going only one-way, etc.
Also, it only handles map links; it doesn't check if all ressource files
referenced by a map actually exist.
|
|
|
|
(+ checking that paths don't run outside of respositories)
|
|
|
|
This now checks if relative paths are still inside the repository, as a
general safety mechanism to stop the linter from accidentally reading
other things, as well as a nice hint for users.
|