Skip to content

Type name inconsistencies #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ombre5733 opened this issue Apr 15, 2017 · 1 comment
Open

Type name inconsistencies #76

ombre5733 opened this issue Apr 15, 2017 · 1 comment

Comments

@ombre5733
Copy link

I'm right now playing around with templates and noticed a few inconsistencies in the naming. For example:

>>> type(x)
<class 'pygccxml.declarations.class_declaration.class_declaration_t'>
>>> x.decl_string
'::A::T<A::B::D, bool>'
>>> x.partial_decl_string
'::A::T< A::B::D, bool >'

So the partial_decl_string has spaces after < and before > where the decl_string does not.

Even more severe for me is that the decl string for all types returns a fully qualified name starting
with :: but the template arguments do not. In the example above, I wished that the first template argument would be rendered as ::A::B::D and not only A::B::D.

Is it possible to harmonize the output?

@ombre5733 ombre5733 changed the title Naming inconsistencies Type name inconsistencies Apr 15, 2017
@iMichka
Copy link
Collaborator

iMichka commented Apr 15, 2017

Hi. Thanks for reporting.

Cleaning this up would surely be great. Not sure when I will be able to afford some time for this, probably next week. Changing this may not be too difficult. A pull request would also be welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants