updated the release process
diff --git a/doc/html_generated/main.html b/doc/html_generated/main.html
index f118749..852c5d7 100644
--- a/doc/html_generated/main.html
+++ b/doc/html_generated/main.html
@@ -33,7 +33,7 @@
int res = context.run(); // run
- if(context.shouldExit()) // important - query flags (and --no-run) rely on the user doing this
+ if(context.shouldExit()) // important - query flags (and --exit) rely on the user doing this
return res; // propagate the result of the tests
int client_stuff_return_code = 0;
diff --git a/doc/html_generated/random_dev_notes.html b/doc/html_generated/random_dev_notes.html
index 9a7b867..52b6a07 100644
--- a/doc/html_generated/random_dev_notes.html
+++ b/doc/html_generated/random_dev_notes.html
@@ -3,7 +3,7 @@
<title>random_dev_notes</title>
<xmp theme="united" style="display:none;">
-on big releases spam in hackernews and reddit/r/cpp/gamedev/Cplusplus/programming
+on big releases spam in hackernews and reddit/r/cpp/gamedev/Cplusplus/programming (also in isocpp - https://isocpp.org/editorial-policy )
how to deal with pull requests for the main branch instead of the dev branch
- http://stackoverflow.com/questions/9135913/merge-pull-request-to-a-different-branch-than-default-in-github
diff --git a/doc/html_generated/readme.html b/doc/html_generated/readme.html
index 20f8edb..f972a0e 100644
--- a/doc/html_generated/readme.html
+++ b/doc/html_generated/readme.html
@@ -22,7 +22,7 @@
- [```main()``` entry point and dealing with shared objects](main.html)
- [FAQ](faq.html)
-Support the development of the project with donations! There is a list of planned features which are all important and big - see the [**roadmap**](roadmap.html). I work on this project in my spare time and every cent is a big deal.
+Support the development of the project with donations! There is a list of planned features which are all important and big - see the [**roadmap**](roadmap.html). I took a break from working in the industry to make open source software so every cent is a big deal.
[](https://pledgie.com/campaigns/31280)
diff --git a/doc/html_generated/roadmap.html b/doc/html_generated/roadmap.html
index 74124f6..6f24f94 100644
--- a/doc/html_generated/roadmap.html
+++ b/doc/html_generated/roadmap.html
@@ -11,8 +11,11 @@
This is a list of planned features for future releases (maybe in the given order).
+- switch to using ```std::vector``` and ```std::set``` and remove custom implementations
+- the set holding all registered tests should use a specialized allocator to minimize program startup time
- fix the test coverage reports - currently each example replaces the coverage from the last example
- test with gcc 6 and use it in the CI builds
+- a mechanism for translating exceptions - users should be able to teach the framework about their types (look at Catch for this)
- support for ```std::exception``` and derivatives (mainly for calling the ```.what()``` method when caught unexpectedly)
- test with missed warning flags for GCC - look into https://github.com/Barro/compiler-warnings
- crash handling: signals on UNIX platforms or structured exceptions on Windows
@@ -46,9 +49,18 @@
And here is a list of things that are being considered but not part of the roadmap yet:
+- rework the cmake single header assembly - to use a ```.cmake``` script that sets the permissions of ```doctest.h``` as read only
+- look into MSTest integration
+ - http://accu.org/index.php/journals/1851
+ - https://msdn.microsoft.com/en-us/library/hh270865.aspx
+ - also look into similar Xcode integration
- matchers - should investigate what they are :D
+- generators? - look at Catch - and investigate what they are (also in [boost](http://www.boost.org/doc/libs/1_61_0/libs/test/doc/html/boost_test/tests_organization/test_cases/test_case_generation.html)
- option to list files in which there are test cases who match the current filters
- handle ```wchar``` strings
+- a progress reporter
+- doctest in a GUI environment? with no console? APIs for attaching a console? querying if there is one? should investigate...
+- ability to customize the colors in the console output
- refactor the assertion macros - make proxy functions that do most of the things to minimize code bloat
- pool allocator for the ```String``` class - currently very unoptimized
- ability to specify ASC/DESC for the order option
@@ -58,6 +70,7 @@
- hierarchical test suites - using a stack for the pushed ones - should be easy
- put everything from the ```detail``` namespace also in a nested anonymous namespace to make them with internal linkage
- ability to re-run only newly compiled tests based on time stamps using ```__DATE__``` and ```__TIME__``` - stored in some file
+- submit to [boost](http://www.boost.org/development/requirements.html)?
---------------