Re: [pygccxml-development] compiler generated declarations?

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

On Wed, Aug 27, 2008 at 3:04 PM, Gustavo Carneiro <gjc...@gm...> wrote:
> I have been trying latest gccxml and pygccxml trunk with pybindgen, and am
> finding something new that is happening:
>
> /home/gjc/projects/pybindgen/trunk/tests/foo.h:193: AnnotationsWarning:
> Annotation 'automatic_type_narrowing=True' not used (used in
> SomeObject::NestedClass &
> SomeObject::NestedClass::operator=(SomeObject::NestedClass const & arg0)
> [member operator])
>
> This operator= method is generated by the compiler or pygccxml, yet it
> appears to be a real declaration with a physical location.  As a side
> effect, pybindgen will look for annotation comments and complain when the
> found annotations cannot be used.
>
> Is there any way to distinguish between real definitions and synthetic ones?

You are looking for declarations.is_artificial property

http://language-binding.net/pygccxml/apidocs/pygccxml.declarations.declaration.declaration_t-class.html#is_artificial

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