Re: [pygccxml-development] array_t vs pointer_t

[Matthias B. <ba...@ir...>]

Roman Yakovenko wrote:
> On 4/20/06, Matthias Baas <ba...@ir...> wrote:
>> The problem is not in pyplusplus, it's in my own code. For example, I
>> have functions like this:
>>
>>   void getValue(int& val)
>>   void getValue(double& val)
>>
>> When I apply the Output(1) policy, both wrappers look identical (except
>> for their return value, but there are also examples where even the
>> return value is identical):
>>
>>   int getValue_wrapper()
>>   double getValue_wrapper()
>>
>> But meanwhile, I've updated my code so that these clashes are recognized
>> and reported (and can then be resolved manually).
>> After fixing a series of smaller issues in my code it seems to compile
>> again.... (but I can only say for sure in about an hour or so when
>> compilation is done)...
> 
> :-) All you need is reliable way to give function unique name. You can
> construct
> name of wrapper from from name + line number. Every declaration has
> location property. Or another option: every declaration has mangled
> property, you can use it within the name.

Actually, I do have unique names now (using id(decl)), but for different 
reasons. In the above case, this would not be a solution as long as the 
wrappers have the same name in Python (and when they do not have the 
same name, then the above problem doesn't exist anyway). Which version 
should Boost.Python pick when I call getValue() in Python? So the 
wrappers must have different names in Python.

>> [contrib dir]
>>> Go ahead. I like this idea. I saw it in docutils.
>> ok. Do you already know when you will move the code over to svn? (I will
>> wait until this is done. By the way, I will also wait with updating the
>> setup scripts (so that they can be used for the source distributions)
>> until the transition is finished)
> 
> Next week or two. I want to fix some bugs found by people and then to move.

ok

- Matthias -