Re: [pygccxml-development] FT - name uniqueness

[Roman Y. <rom...@gm...>]

On 10/11/06, Matthias Baas <ba...@ir...> wrote:
> Right. And as long as the alias is used for the wrapper names (which is
> currently the case) the above problem doesn't exist.

You are wrong. Consider next case:

struct window{
void get_size( int&, int& );
};

struct image{
void get_size( int&, int& );
};

What you propose will force user always specify a function alias. While in my
proposition, user will have to do this only in case he has overloaded functions
in the same scope.

> The question may then rather be: who should report the error, Py++ or
> the compiler? I think it's desirable that Py++ notices this situation
> and can issue an error, but I don't think it's a good idea to mangle the
> name so that the code compiles but produces functions that could not be
> called because they are shadowed by other functions.

Generated code should work. And it is possible to achieve this. In case we have
problems like this, it could be nice to compare function signatures
and to decide
what alias to give for the functions.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/