8 commits

Author	SHA1	Message	Date
practicalswift	962d8eed5b	Remove boost dependency (boost/assign/std/vector.hpp)	2018-06-27 17:45:18 +02:00
DesWurstes	000000035b	Obsolete #!/bin/bash shebang	2018-06-20 11:12:41 +03:00
practicalswift	3352da8da1	Add "export LC_ALL=C" to all shell scripts	2018-06-14 15:27:52 +02:00
Wladimir J. van der Laan	7c32b414b6	Merge #13230: Simplify include analysis by enforcing the developer guide's include syntax ... 16e3cd380a Clarify include recommendation (practicalswift) 6d10f43738 Enforce the use of bracket syntax includes ("#include <foo.h>") (practicalswift) 906bee8e5f Use bracket syntax includes ("#include <foo.h>") (practicalswift) Pull request description: When analysing includes in the project it is often assumed that the preferred bracket include syntax (`#include <foo.h>`) mentioned in `developer-docs.md` is used consistently. @sipa:s excellent circular dependencies script [`circular-dependencies.py`](50c69b7801/contrib/devtools/circular-dependencies.py) (#13228) is an example of a script making this reasonable assumption. This PR enables automatic Travis checking of the include syntax making sure that the bracket syntax includes (`#include <foo.h>`) is used consistently. Tree-SHA512: a414921aabe8e487ebed42f3f1cbd02fecd1add385065c1f2244cd602c31889e61fea5a801507ec501ef9bd309b05d3c999f915cec1c2b44f085bb0d2835c182	2018-06-11 20:24:58 +02:00
Ben Woosley	9d6c9dbb88	lint: Add linter to error on #include <*.cpp> ... Files should depend on one another by interface, not by implementation. This checks for quoted includes as well. With practicalswift	2018-06-06 02:11:25 -07:00
practicalswift	6d10f43738	Enforce the use of bracket syntax includes ("#include <foo.h>")	2018-06-06 11:09:05 +02:00
practicalswift	81bbd32a2c	build: Guard against accidental introduction of new Boost dependencies	2018-06-04 10:08:08 +02:00
MarcoFalke	fa3c910bfe	test: Move linters to test/lint, add readme	2018-05-24 12:02:15 -04:00

Renamed from contrib/devtools/lint-includes.sh (Browse further)