Subject: Re: [boost] [Range] make range_const/mutable_iterator<C>::type non-existent if C is non-range
From: Arno SchÃ¶dl (aschoedl_at_[hidden])
Date: 2009-01-08 03:16:58
> > Thorsten,
> > is it o.k. if I add these Boost.Range changes to my "partition_point" library, so it will be reviewed and adopted as a package? I'd put lazy_typedef into boost::detail::range.
> I don't see why not. As for the portability, I guess we can test that on
> trunk. I'll see if I can get some time to do this...
partition_point library will test this for its use cases, which covers the relevant ones:
- use as return value,
- use as parameter,
- overload disambiguation on it.
-- Dr. Arno Schoedl Â· aschoedl_at_[hidden] Technical Director think-cell Software GmbH Â· Invalidenstr. 34 Â· 10115 Berlin, Germany http://www.think-cell.com Â· phone +49-30-666473-10 Â· toll-free (US) +1-800-891-8091 Directors: Dr. Markus Hannebauer, Dr. Arno Schoedl Â· Amtsgericht Charlottenburg, HRB 85229
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk