Hi, Just a quick remark. Why don't you split policies into different categories? Error handling policy is orthogonal with constraint policy. The more reasonable definition would be template< typename ConstraintPolicy, typename ErrorPolicy=default_error_policy> class range { //... }; In regards of naming, contrained_value would be much better. Regards. Pavol On Sat, May 15, 2004 at 10:37:43PM -0400, christopher diggins wrote:
Here is my latest range.hpp file, I should probably change the name back to constrained_value because of the conflict with iterator ranges? I am a first time boost contributor , so I would appreciate comments on my style, and whether this file overextends its intended scope.
To Jeff Garland: do you want me to be fully compatible with your existing constrained_value type, so that you can link this in without rewriting a thing?
Thanks to all in advance.