Skip to content

Releases: suokko/dealer

Build system improvement and bug fix release

14 Feb 07:11
Compare
Choose a tag to compare

Build system is now capable to install all files. That alone warrants a new
release to make packaging dealer easier. Other changes to build system include
fake autotools like configure to allowing using existing tools build around
autotools interface.

Changes:

  • Install all tools and manuals
  • Basic cross-compile support
  • Windows build is known to work with mingw
  • Changed make to read CFLAGS and CXXFLAGS environment variables
  • Improvements to double dummy library randomness

2014 February release with number of bug fixes and minor improvements

02 Feb 11:49
Compare
Choose a tag to compare

The new dealer version had number of bug fixes thanks to number of new unit tests managing to expose broken and missing features. With lcov coverage checking the new test suit is known to test all code paths. But dealer rules are complex that means there still can be bugs hidden in the code if using some specific combination of rules. Most important bug fixes include length bias dealing, unlimited number of shape function use, rnd function fix to positive numbers on 64 bits, allow entering negative numbers between -1000 and -9999 and evalcontract function fix.

Other major change is nearly complete rewrite of build system. That is very likely to mean some portable issues but any portable bug will be a high priority issue. The new build system is nonrecursive makefile based build. That makes it simple to add new files and modules to build because build rules are auto generated from simple make variables.

New features include filter of zero frequency rows and columns, filter expression for average function printing and switch to Bo's double dummy solver.

If you find any bugs they an be reported to https://github.com/suokko/dealer/issues. The most helpful bug report would be one with a test case attached that can be added to unit test suit. The new test case would make sure same bug won't surface again in future.,

Contribution are welcome also. The preffered method is a github pull request with web based review process. But I will also check emailed patch files if you prefer that method.