Tidy up use of GENERATING_DOCS

CHANGELOG

@@ -1,6 +1,8 @@
 1.0.0-b6
 
+* Add HTTP field value parsers
 * Use SFINAE on return values
 * Use beast::error_code instead of nested types
+* Tidy up use of GENERATING_DOCS
 
 --------------------------------------------------------------------------------

TODO.txt

@@ -7,11 +7,7 @@ Boost.Http
 Docs:
 * Include Example program listings in the docs
 * Fix index in docs
-* Figure out why namespace rfc2616 is included in docs
-  (currently disabled via GENERATING_DOCS macro)
 * melpon sandbox?
-* Check DOXYGEN, GENERATIC_DOCS directives in source
-  - See if we can include them now that xsl is fixed
 * Implement cleanup-param to remove spaces around template arguments
   e.g. in basic_streambuf move constructor members
 * Don't put using namespace at file scope in examples,
@@ -23,15 +19,12 @@ Core:
 * Complete allocator testing in basic_streambuf
 
 WebSocket:
+* more invokable unit test coverage
+* More control over the HTTP request and response during handshakes
 * optimized versions of key/masking, choose prepared_key size
-* invokable unit test
-* Don't try to read requests into empty_body
 * Give callers control over the http request/response used during handshake
 * Investigate poor autobahn results in Debug builds
 * Fall through composed operation switch cases
-* Replace stream::error_ with stream::state_, example states: ok, error, abort_io
-  Need a cancel state so waking up a ping stored in invokable knows to call the
-  final handler with operation_aborted
 * Use close_code::no_code instead of close_code::none
 * Make request_type, response_type public APIs,
   use in stream member function signatures
@@ -56,8 +49,5 @@ HTTP:
 * Complete allocator testing in basic_streambuf, basic_headers
 * Add tests for writer using the resume function / coros
 * Custom HTTP error codes for various situations
-* Make empty_body write-only, remove reader nested type
-* Add concepts WritableBody ReadableBody with type checks,
-  check them in read and write functions
 * Branch prediction hints in parser
 * Check basic_parser_v1 against rfc7230 for leading message whitespace

include/beast/core/static_string.hpp

@@ -506,8 +506,6 @@ compare(
 
 } // detail
 
-#if ! GENERATING_DOCS
-
 template<std::size_t N, std::size_t M, class CharT, class Traits>
 bool
 operator==(
@@ -672,8 +670,6 @@ operator>=(
     return detail::compare(lhs, s) >= 0;
 }
 
-#endif
-
 } // beast
 
 #endif

include/beast/http/message.hpp

@@ -145,8 +145,6 @@ private:
     }
 };
 
-#if ! GENERATING_DOCS
-
 /// A typical HTTP request
 template<class Body,
     class Headers = basic_headers<std::allocator<char>>>
@@ -157,8 +155,6 @@ template<class Body,
     class Headers = basic_headers<std::allocator<char>>>
 using response = message<false, Body, Headers>;
 
-#endif
-
 } // http
 } // beast
 

include/beast/http/message_v1.hpp

@@ -50,8 +50,6 @@ struct message_v1 : message<isRequest, Body, Headers>
     }
 };
 
-#if ! GENERATING_DOCS
-
 /// A typical HTTP/1 request
 template<class Body,
     class Headers = basic_headers<std::allocator<char>>>
@@ -62,8 +60,6 @@ template<class Body,
     class Headers = basic_headers<std::allocator<char>>>
 using response_v1 = message_v1<false, Body, Headers>;
 
-#endif
-
 /// Returns `true` if a HTTP/1 message indicates a keep alive
 template<bool isRequest, class Body, class Headers>
 bool