Gecode 3.2.2 released
Gecode version 3.2.2 has been released. It can be downloaded here.
From the Changelog:
From the Changelog:
Changes in Version 3.2.2 (2009-11-30)
This release adds the sequence constraint (contributed by David Rijsman, Quintiq) and has as always some small additions and fixes.
- Kernel
- Bug fixes
- Added missing assignment operator for space-based allocators for STL data structures. (minor, thanks to Gustavo Gutierrez)
- Search engines
- Bug fixes
- The memory reported could be sometimes too low (the previous fix for 3.2.0 did not fix it for branch and bound search). (minor)
- Finite domain integers
- Additions
- Added sequence constraint. (major , contributed by David Rijsman)
- Bug fixes
- The global cardinality (count) constraint now accepts unsorted arrays of values. It previously propagated incorrectly if the array was not sorted. (minor, thanks to Alberto Delgado)
- Fixed bug in the ICL_VAL propagator for global cardinality. (minor)
- Subscription to constant views did not honor the flag to avoid processing. (minor)
- Finite integer sets
- Bug fixes
- Subscription to constant views did not honor the flag to avoid processing (did not occur in practice). (minor)
- Script commandline driver
- Additions
- Report if search engine has been stopped. (minor)
- Range and value iterators
- Other changes
- Renamed test for subset or disjointness of range iterators to "compare". (minor)
- Example scripts
- Additions
- Added car sequencing example (problem 1 in CSPLib). Uses the new sequence-constraint. (minor)
- Gecode/FlatZinc
- Bug fixes
- Support search annotations with constants in the variable arrays. (minor, thanks to Håkan Kjellerstrand)
- The set_in and set_in_reif constraints were buggy when used with Boolean variables (which are usually not generated by mzn2fzn so that the issue probably does not occur in practice). (minor)
- The global_cardinality constraint was not completely compatible with the MiniZinc semantics. It would constrain values not mentioned in the array to have zero occurrences, while in MiniZinc they are unrestricted. (minor)
- Element constraints in reified positions produced an error in the mzn2fzn translation. (major, thanks to Håkan Kjellerstrand)