[C++-sig] [Boost.Python v3] Features and Scope

Stefan Seefeld stefan at seefeld.name
Tue Aug 30 13:04:21 CEST 2011

On 08/30/2011 02:42 AM, Jim Bosch wrote:
> On 08/29/2011 09:41 AM, Stefan Seefeld wrote:
>> On 08/28/2011 02:14 PM, Jim Bosch wrote:
>>> To solve it, I think you'd want anything registered by a specific
>>> module to appear both in that module's registry and the global
>>> registry, with the module's registry taking precedence.  Are there any
>>> cases where you'd want something only to appear in the module-specific
>>> registry?
>> Anything that gets injected into the global registry is prone to violate
>> the ODR. Of course, also adding it into a local registry and letting
>> that have precedence may mask the ODR violation issue. But in that case,
>> it isn't clear why we'd add it to the global registry at all.
> The reason to add it to the global registry is so if you know one of
> the modules you depend on registered a converter, you don't have to do
> it yourself.

As I suggested in reply to Dave, I think it would be better to require
modules that depend on  external converters to explicitly import them.



      ...ich hab' noch einen Koffer in Berlin...

More information about the Cplusplus-sig mailing list