Re: [pygccxml-development] declarations string, stability

[Ben S. <bsc...@lu...>]

>=20
> I almost agree with you. I could improve the interface,=20
> meanwhile you can use decl_visitor_t (=20
> http://language-binding.net/pygccxml/apidocs/pygccxml.declarat
> ions.decl_visitor.decl_visitor_t-class.html
> )
> class and apply_visitor function (
> http://language-binding.net/pygccxml/apidocs/pygccxml.declarat
> ions.algorithm-module.html#apply_visitor
> )

Oh, I didn't know about that functionality. Well, I'll definitely try
using it next time...

>=20
> > I know this would be useful because I had to search for=20
> decls based on=20
> > their attributes which wasn't a param in=20
> scopedef.member_functions(..)=20
> > so I had to manually test the attributes anyway.
>=20
> So why do you need visitor? You already know that you need=20
> member functions, the only thing left is to specialized the=20
> query. This is easily done by passing a callable to the=20
> member_functions function:
>=20
> ns.mem_funs( lambda x: len( x.arguments ) > 19 )
>=20

Argg, again, I didn't know about it because its not mentioned anywhere
in the documentation.
Maybe again a paragraph about decl_visitor_t and callable would make
them more clear to the
End users.


>=20
> P.S. What functionality is missing from the member_functions=20
> interface?

The ability to search for decls based on their attributes.
This really should be a visitor or callable function because it's
entirely string matching and project specific.

Cheers
Ben