[C++-sig] Renaming indexing_v2 directory [was Re: Merging indexing_v2 to mainline]

[Roman Yakovenko]

2008/4/28 Andreas Klöckner <lists at informa.tiker.net>:
> On Sonntag 27 April 2008, Raoul Gough wrote:
>  > #include <boost/python/suite/indexing/container_suite.hpp>
>  > #include <boost/python/suite/indexing/vector.hpp>
>  >
>  > -->
>  >
>  > #include <boost/python/suite/indexing_v2/container_suite.hpp>
>  > #include <boost/python/suite/indexing_v2/vector.hpp>
>  >
>  > Does anyone have a strong opinion about this?
>
>  Sounds reasonable. What would the status of the "old" indexing suite become?
>  Deprecated, to be removed in a future version? Kept indefinitely?

In my opinion old indexing suite could stay forever: it works, it is
stable and have good documentation.

>  Unrelatedly: I've been a user of the old indexing suite for a while now, and
>  I'm overall happy with what it does. Can you summarize in a few words why I
>  might want to look into the new one?

Here is a short list of items, I remember:

1. Support for almost all STL containers
2. Few new features, that allow you to expose even plain C arrays as
Python containers
3. I didn't tried to change the old indexing suite, but I didn't have
any problems to fix\add new to the V2
4. It is not that difficult to use V2 functionality as a building
blocks and expose your own container.
5. You have pretty good control over exposed functionality. For
example, if you class doesn't have operator==, you will not define
"in" operator in the container class.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/