Re: [pygccxml-development] Weird problem apparently caused by decl.readme()
Brought to you by:
mbaas,
roman_yakovenko
From: Roman Y. <rom...@gm...> - 2010-05-12 18:15:15
|
On Wed, May 12, 2010 at 8:08 PM, Benoit Leveau <ben...@mo...> wrote: > Hello, Good evening > I just found a very odd problem when using py++. > I don't have time right now to generate files that exhibit the error, > but still thought I would report it. > Maybe it sounds familiar to someone. > > C++ input: > - Class A with some virtual functions > - Class B inherits from A (and doesn't override the virtual functions) > > Steps: > - The binding code first includes all declarations from A and B (class, > functions, variables, etc.). > While doing this, it also calls readme() on each declaration. > - Later, it calls exclude() on the set of virtual functions, for both > classes. > > Result: > In the file generated by py++ for class B, the virtual functions are > present. > > Expected result: > The virtual functions have been specifically excluded and should not be > present. > > Cause: > When removing the call to readme(), the virtual functions are correctly > excluded in the generated files. > I verified that it's indeed caused by the call to readme() and not by > the fact that some of the code parses the result of the call. Interesting. I will take a look, may be I will see something. Thanks for reporting. -- Roman Yakovenko C++ Python language binding http://www.language-binding.net/ |