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-06 05:21:34
> It seems like a reasonable problem to solve. Neil, what other solutions
> did you think about?
> Another question: is your fix widely portable?
I have no idea. Our partition_point unit tests will check that. I just checked in a fall-back for BOOST_NO_TEMPLATE_PARTIAL_SPECIALIZATION (and renamed it to lazy_typedef, similar to lazy_enable_if):
-- 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