xerus issueshttps://git.hemio.de/xerus/xerus/-/issues2017-03-28T21:55:56+02:00https://git.hemio.de/xerus/xerus/-/issues/183Use the new thread local mersenne twister2017-03-28T21:55:56+02:00Sebastian WolfUse the new thread local mersenne twisterEither as default or only engine for random functions and for all testcases.Either as default or only engine for random functions and for all testcases.Version 3.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/178timestamp of log msg is from before the execution of whatever is printed2017-03-28T21:55:56+02:00Fuchsi*timestamp of log msg is from before the execution of whatever is printedVersion 3.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/177error.log is always created2017-03-28T21:55:56+02:00Fuchsi*error.log is always createdmaybe we should remove the feature of streaming the log to a file altogether. same thing can be achieved by calling the application with "./foo 2>error.log"maybe we should remove the feature of streaming the log to a file altogether. same thing can be achieved by calling the application with "./foo 2>error.log"Version 3.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/171improve selection of severity of errors2017-03-28T21:55:56+02:00Fuchsi*improve selection of severity of errorsa typical error (ie. user / usage error) should be an "error" (but still throw an exception)
critical error as internal error
fatal as errors that we cannot recover froma typical error (ie. user / usage error) should be an "error" (but still throw an exception)
critical error as internal error
fatal as errors that we cannot recover fromVersion 3.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/170use boost instead of misc functions where appropriate2017-03-28T21:55:56+02:00Fuchsi*use boost instead of misc functions where appropriatethis might be appropriate for
- [ ] misc::product
- strings:
- [ ] misc::explode by boost::split
- [ ] misc::trim by boost::trimthis might be appropriate for
- [ ] misc::product
- strings:
- [ ] misc::explode by boost::split
- [ ] misc::trim by boost::trimVersion 3.0https://git.hemio.de/xerus/xerus/-/issues/168LOG_ABSOLUTE_TIME not compatible to GCC 4.92017-03-28T21:55:56+02:00Fuchsi*LOG_ABSOLUTE_TIME not compatible to GCC 4.9std::put_time was only added in GCC 5.0 -> we need to find another solution (likely some ugly c functions - dig in git to check what we used before put_time?)std::put_time was only added in GCC 5.0 -> we need to find another solution (likely some ugly c functions - dig in git to check what we used before put_time?)Version 2.3Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/167Pipe operator of xerus::misc::generic_error destroys type information.2017-03-28T21:55:56+02:00Sebastian WolfPipe operator of xerus::misc::generic_error destroys type information.The pipe operator returns an object of type generic_error&, apparently this disallows a catch statement to determine any specialized objects.The pipe operator returns an object of type generic_error&, apparently this disallows a catch statement to determine any specialized objects.Version 2.3https://git.hemio.de/xerus/xerus/-/issues/141Failing Failtests don't provide sufficent information.2017-05-29T23:27:29+02:00Sebastian WolfFailing Failtests don't provide sufficent information.Version 2.0Sebastian WolfSebastian Wolfhttps://git.hemio.de/xerus/xerus/-/issues/90Replace the blasAnalysis by a general performance measument system placed in ...2018-04-01T13:07:03+02:00Sebastian WolfReplace the blasAnalysis by a general performance measument system placed in misc.Sebastian WolfSebastian Wolfhttps://git.hemio.de/xerus/xerus/-/issues/126ALLOW_MOVE for template types2018-04-23T03:03:36+02:00Fuchsi*ALLOW_MOVE for template typesmacro should have the definition ALLOW_MOVE(newName, ...) to allow arbitrary template arguments (ie. those with ',' in them....)macro should have the definition ALLOW_MOVE(newName, ...) to allow arbitrary template arguments (ie. those with ',' in them....)version 1.4Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/67clean up global definitions2018-04-23T03:03:38+02:00Fuchsi*clean up global definitionssome misc stuff (eg logger and test) are not yet inside the MISC namespace, there is a `___THIS_IS_A_NEW_NAMESPACE___` namespace and a namespace called "r". also some objects inside xerus:: that are unnecessarz (eg: n,m,r).
some misc stuff (eg logger and test) are not yet inside the MISC namespace, there is a `___THIS_IS_A_NEW_NAMESPACE___` namespace and a namespace called "r". also some objects inside xerus:: that are unnecessarz (eg: n,m,r).
version 1.1Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/64Make xerus build with clang2018-04-23T03:03:38+02:00Sebastian WolfMake xerus build with clangAt the moment xerus cannot be build using clang++, because clang++ doesn't understand the SFINAE constructs we are using.At the moment xerus cannot be build using clang++, because clang++ doesn't understand the SFINAE constructs we are using.version 1.1Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/63Fix the header includes to take advantage of new fiel structure2018-04-23T03:03:38+02:00Sebastian WolfFix the header includes to take advantage of new fiel structureVersion 1.0Sebastian WolfSebastian Wolfhttps://git.hemio.de/xerus/xerus/-/issues/49Define guard for test coverage2018-04-23T03:03:39+02:00Sebastian WolfDefine guard for test coverageThere should be a define guard to enable/disable the code coverage test, since the coverage is not of interest for users of xerus, but only for the developers.There should be a define guard to enable/disable the code coverage test, since the coverage is not of interest for users of xerus, but only for the developers.Version 1.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/44REQUIRE_TEST macro file name identification (in cases of ../ in the path)2018-04-23T03:03:39+02:00Fuchsi*REQUIRE_TEST macro file name identification (in cases of ../ in the path)Version 1.0Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/33problems with the MISC_NAMESPACE macro2018-04-23T03:03:39+02:00Fuchsi*problems with the MISC_NAMESPACE macro1. not defining it before including any individual misc/*.h file will result in a warning about undefined macros / variables
2. setting it via `#define MISC_NAMESPACE` results in `#define MISC` which interestingly results in the followi...1. not defining it before including any individual misc/*.h file will result in a warning about undefined macros / variables
2. setting it via `#define MISC_NAMESPACE` results in `#define MISC` which interestingly results in the following error message:
```
bla.cpp:(.text+0xa58): undefined reference to `(anonymous namespace)::get_call_stack()'
```
This might be the only way to reference an anonymous namespace...???version 1.1https://git.hemio.de/xerus/xerus/-/issues/23Code coverage detection not working properly2018-04-23T03:03:39+02:00Sebastian WolfCode coverage detection not working properlyCode coverage says:
file index.hpp : 2 of 4 tests performed
However there are only two REQUIREs in index.hpp, which are most certainly called. Probably the problem is that the corresponding functions also appear inlined?Code coverage says:
file index.hpp : 2 of 4 tests performed
However there are only two REQUIREs in index.hpp, which are most certainly called. Probably the problem is that the corresponding functions also appear inlined?Version 1.2Fuchsi*Fuchsi*https://git.hemio.de/xerus/xerus/-/issues/231Add Skip option for test cases for non-regression failing tests2019-03-31T12:47:04+02:00RoteKekseAdd Skip option for test cases for non-regression failing testsVersion 4.0Sebastian WolfSebastian Wolfhttps://git.hemio.de/xerus/xerus/-/issues/242Add a CI test using _GLIBCXX_ASSERTIONS2019-04-02T15:39:55+02:00Sebastian WolfAdd a CI test using _GLIBCXX_ASSERTIONSThe config file allows to use the additional assertions of the GLIBC via `-D _GLIBCXX_ASSERTIONS`. There should be a CI test where this is active as it would directly expose e.g. vector out-of-bounds errors.The config file allows to use the additional assertions of the GLIBC via `-D _GLIBCXX_ASSERTIONS`. There should be a CI test where this is active as it would directly expose e.g. vector out-of-bounds errors.Version 4.0Sebastian WolfSebastian Wolfhttps://git.hemio.de/xerus/xerus/-/issues/15Upgrade the UnitTests to support unit test rules for different types, e.g. Fu...2019-04-03T18:52:12+02:00Sebastian WolfUpgrade the UnitTests to support unit test rules for different types, e.g. FullTensor and SparseTensor