Re: [pygccxml-development] Printing declarations...

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

On 3/17/06, Matthias Baas <ba...@ir...> wrote:
> Hi,
>
> finally I can send a mail as a *user* of pyplusplus again and not as a
> developer... :)

Well, it took some time, but ...

> I was pleased to see that the optional<> stuff is in cvs and working!

:-). Enjoy.

> Should the fix for the copy constructor also be available yet? (they are
> still not wrapped automatically)

I am doing something wrong with constructors. I do not know what :-(.
In order to export constructors I need to take into account too many facts.
So, until somebody will write comprehensive test case it will not be done i=
n few
weeks or may be months. :-(

>The call operator also doesn't seem to
> get wrapped (hasn't that been already done by earlier versions)?

I think you find a bug.  I just run special_operators_tester.py and it pass=
.
Can you reproduce it? Thanks

> Now to my main question for this mail: Is there already a way to obtain
> a "full" string representation of a declaration (for printing)? I'm only
> aware of the full_name() function but (as the name already implies) this
> only returns the name whereas for methods I'd like to see the full
> signature as well (to be able to distinguish between overloaded methods).

x.decl_string

This should do it.

> - Matthias -

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