Use single header file

There are drawbacks with this approach, but the benefit -- for a
small-ish project -- is that the single header file can serve as a
very good overview and guide for people exploring the code for the
first time.

1 files changed, 0 insertions, 17 deletions

diff --git a/query.h b/query.h
deleted file mode 100644
index d9c7ac9..0000000
--- a/query.h
+++ /dev/null
@@ -1,17 +0,0 @@
-#define TRUNCATED(s) s[-1]
-
-struct query{
-	int method;
-	int length; /* Content length. */
-	char *string;
-} query;
-
-enum method{
-	GET,
-	POST
-};
-
-char *nextparam(enum method, int *, int);
-void setquery(void);
-char *split(char *);
-int urldecode(char *, int);
\ No newline at end of file