aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
Diffstat (limited to 'src')
-rw-r--r--src/compat.h10
-rw-r--r--src/test/README.md (renamed from src/test/README)4
2 files changed, 7 insertions, 7 deletions
diff --git a/src/compat.h b/src/compat.h
index 3924445b1a..8fbafb6cce 100644
--- a/src/compat.h
+++ b/src/compat.h
@@ -28,16 +28,16 @@
#include <windows.h>
#include <ws2tcpip.h>
#else
+#include <sys/fcntl.h>
+#include <sys/mman.h>
+#include <sys/socket.h>
#include <sys/types.h>
+#include <net/if.h>
+#include <netinet/in.h>
#include <arpa/inet.h>
#include <ifaddrs.h>
#include <limits.h>
-#include <net/if.h>
#include <netdb.h>
-#include <netinet/in.h>
-#include <sys/fcntl.h>
-#include <sys/mman.h>
-#include <sys/socket.h>
#include <unistd.h>
#endif
diff --git a/src/test/README b/src/test/README.md
index 77f7faa815..7efce6f052 100644
--- a/src/test/README
+++ b/src/test/README.md
@@ -1,3 +1,4 @@
+# Notes
The sources in this directory are unit test cases. Boost includes a
unit testing framework, and since bitcoin already uses boost, it makes
sense to simply use this framework rather than require developers to
@@ -17,5 +18,4 @@ uint256_tests.cpp.
For further reading, I found the following website to be helpful in
explaining how the boost unit test framework works:
-
-http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/
+[http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/](http://www.alittlemadness.com/2009/03/31/c-unit-testing-with-boosttest/). \ No newline at end of file