From: Pavel Vozenilek (pavel_vozenilek_at_[hidden])
Date: 2005-08-02 14:09:12
> You can generalize it a step further when you can give a range to
> n_m_of(): n minimum number of values that must satisfy the test and m
> maximum number of values that must satisfy the test. Ok, ok no more
> complexity as necessary ;-) Your n_of would also be useful with the
> junctions approach (This provides all steps between "and" and "or"
> inclusive "xor" in one function).
Complexity that is missing from library will be
reimplemented (likely with bugs and pain) by user.
Properly named and documented and tested
features are most convincing argument for people
to use a tool.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk