[C++-sig] multiply defined to_python_converter

David Abrahams dave at boost-consulting.com
Wed Dec 11 20:12:24 CET 2002

"Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com> writes:

> --- David Abrahams <dave at boost-consulting.com> wrote:

>> One thing I worry about a little is that we might have gone
>> too far in the direction of automatically publishing all conversions
>> for v2:
> I think we definitely did go too far. 

Ouch!  I was really hoping you'd disagree!

> The more I think about it the more I am surprised that we missed
> this important point until now.

Ouch, ouch, ouch!

> Your import<> idea looks interesting. Here is another wild idea:
> Tie the conversions to scope(). If a function is def'ed in scope a.b.c look for
> conversions in c first, then b, then a. It's not clear to me what to do about
> cross-package conversions. Maybe one could use a special module-level variable,
> like
> import other_module_1
> import other_module_2
> __boost_python_conversion_path__=[other_module_1, other_module_2]
> To support this the registry would have to keep track in what scope each
> conversion was registered. However, the current C++ interface could maybe left
> untouched.

That wouldn't handle the issue of ABI/type_info compatibility.

Ralf, can you give me a call about this?

                       David Abrahams
   dave at boost-consulting.com * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution

More information about the Cplusplus-sig mailing list