[boost] Re: New Iterator Adaptors

From: David Abrahams (dave_at_[hidden])
Date: 2003-06-10 19:14:48

hartmutkaiser_at_[hidden] (Hartmut Kaiser) writes:

> David Abrahams wrote:
>
>> > Is there any way to tell, which version of the iterator library is 
>> > installed on a target system? I could think of some pp 
>> constant, which 
>> > allows to configure a piece of code to use the 'old' or the 'new' 
>> > iterator lib. This would allow for a smooth transition of existing 
>> > libraries depending on the iterator_lib and looses the 
>> otherwise tight 
>> > coupling between some user code and a specific Boost version.
>> 
>> Cute idea.  Unless you want to account for all the 
>> transitional versions in CVS, you could always 
>> 
>> #include <boost/version.hpp> 
>> 
>> and check BOOST_VERSION
>
> As a last resort this certainly helps. And in a year or so nobody will
> talk about the transitional CVS versions. But now it would be very
> helpful, if there was a separate BOOST_ITERATOR_ADAPTOR_VERSION pp
> constant, which could be used for this needs (BTW Spirit has such a
> constant from the early beginnings). 
> Please don't get me wrong, I do not want to have a very fine granulated
> version tracking constant. My point is, that such interface breaking
> changes _must_ be track-able.

Well, here are the problems:

    1. There's no definition of this macro in the current sources

    2. The new iterator adaptors don't use the same file paths,
       e.g. boost/iterator/iterator_adaptor.hpp vs
       boost/iterator_adaptors.hpp.

I'm certainly open to any concrete solutions to this problem.  Just
tell me how to do it.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com