Re: [pygccxml-development] declarations string, stability

[Gustavo C. <gjc...@gm...>]

On 08/12/2007, Ben Schleimer <bsc...@lu...> wrote:
>
>
>
>
> No, what you want is to use declarations.full_name function.
>
> Are you sure?  It does not seem to include the full signature. Example,
> for the methods:
>
>     int get_int (const char *from_string);
>     int get_int (double from_float);
>
> full_name prints:
>
> '::SomeObject::get_int'
> '::SomeObject::get_int'
>
>
> You could use str(declaration). That'll print out the full signature of
> the member functions.
>

str(declaration) is not good because:
  1. it prints parameter names (which clearly are not part of the
signature);
  2. it adds a redundant "[member function]" description which I do not need
and am afraid might change one day;
  3. I don't think there are any guarantees the string format won't change
in the future.

Otherwise, you'll probably have to write your own formatting function.
>

I guess I could do it.  I was just hoping pygccxml had it already, to save
me some work... :P

-- 
Gustavo J. A. M. Carneiro
INESC Porto, Telecommunications and Multimedia Unit
"The universe is always one step beyond logic." -- Frank Herbert