Re: [pygccxml-development] Proper overload resolution

[Benoît L. <ben...@gm...>]

2010/5/17 Roman Yakovenko <rom...@gm...>:
> On Mon, May 17, 2010 at 9:09 PM, Benoit Leveau
> <ben...@mo...> wrote:
>> Ok, that's what I thought!
>> And I guess there is no way to "register" some Python code to be executed
>> when the module is loaded, it must be done in the __init__.py file, right?
>
> No:
> http://www.boost.org/doc/libs/1_43_0/libs/python/doc/tutorial/doc/html/python/embedding.html
>
> In any case, I suggest you to wrap your module in a Python package.
> This will save you a lot of time later. Even now, you will not have to
> learn how to "embed" Python code via Boost.Python. I am sure, this is
> a nice topic to learn, but after all we have to deliver a product and
> get some money :-) ?
This is already a Python package actually ;)
Thanks for the link.

>>> The only help, you get from Py++, is warning "W1010". You can use
>>> "x.readme()" functionality to check whether set of functions have such
>>> problem or not. You can use that functionality as assert for the
>>> "solution 4".
>>
>> Good, I didn't know a warning was issued in that case.
>>
>>>> From my experience patching boost, creates a huge headache. This is
>>>
>>> exactly the reason, why I migrated indexing suite v2 to be header only
>>> library.
>>
>> Thanks!
>
> You are welcome.
>
>
>
> --
> Roman Yakovenko
> C++ Python language binding
> http://www.language-binding.net/

Thanks again!
Benoit