CopperSpice Forum

This would involve a complete redesign of the entire program. DoxyPress requires multiple passes to gather documentation from different sources and then collate the data. Processing the files could potentially be done using multithreading however the later stages could not due to cross referencing.

Thanks for the confirmation. We are moving all of our CI Unix VM's to use Docker which is a bit of work but well worth it. Ansel has just started the initial configuration but it does look like RHEL version 8 is the best choice. What is holding things up is the release of CentOS 8 which is what we w...

CopperSpice version 1.6 has been in development for several months. This update will add a great deal of new functionality to almost all of the libraries. The timeline was recently updated to reflect the status of the project as of May 2019. To see the current progress of CopperSpice please visit gi...

We have it noted to announce the CopperSpice 1.5.2 release as well as the DoxyPress 1.3.3 release on the forum. Thanks for reminder. The last week has been very busy as we prepared for the first CopperSpice European tour. We are giving a C++ presentation at the Dutch C++ Users Group, presenting at e...

We are very happy to announce the newest version of CopperSpice 1.5.1 (released Sept 14 2018) builds with MSVC 15.8.1 (released Aug 8 2018).

Our thanks to everyone who contributed changes to CopperSpice for this release. A full list of the contributors can be found in our git repository.

I hope that doxypress will also be available to jenkins users. Good suggestion. If you have the time It would be wonderful if you could investigate the details to make this happen. As an alternative you can add a build step to run DoxyPress on your Jenkins project. We use Jenkins version 2.133 for ...

This change was pushed to github and will be part of our September release, version 1.3.2.

This change was pushed to github and will be part of our September release, version 1.3.2.

We dropped your test code into our test suite and it did not break.

My initial guess is that this could be related to a JSON tag setting. If you can email a copy of your JSON project file we can look that over and see what might be different.

Barbara

I used the code shown below and there were no warnings. The output was exactly what we expected for the "detailed documentation" so \ifnot appears to be working. If you rework our example to produce a warning please let us know. Documenting class TagTest. This text will appear in the outpu...