Re: [pygccxml-development] array_t vs pointer_t

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

Roman Yakovenko wrote:
>>> An other way to solve this issue is to create small parser, that will parse all
>>> header files and will create table with relevant information. Then you
>>> can just use
>>> that information from your script.
> 
> I glad you found this solution simple and useful.

Not really simple, but definitely useful... ;)

>> Now I have the problem that the argument policy mechanism sometimes
>> produces wrapper methods that are ambiguous. Looks like I have to
>> improve my prototype so that it recognizes these cases and asks for user
>> help.
> 
> Can you post example in relevant thread? ( Where we discuss the feature ).

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)...

[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)

- Matthias -