Re: [pygccxml-development] Template constructors
Brought to you by:
mbaas,
roman_yakovenko
From: Matthias B. <mat...@gm...> - 2008-03-17 21:12:20
|
Roman Yakovenko wrote: > Matthias unfortunately the problem is on the GCCXML side > > I don't see any work around to the problem :-(. It seems that template > constructors of template class is a special case, that GCCXML > could\does not treat. Yes, unfortunately. I noticed that it doesn't appear in the generated XML file. I was just hoping there's a different way of instantiating the class that might change things. > I think the best solution in this case is to add "constructor > declaration" to the classes. ok, thanks. If only constructors are affected by this then it's not that bad. By the way, here's another (minor) thing I noticed about the warnings that Py++ generates. When you wrap a function that actually takes Boost.Python types as input or returns them as output, then Py++ generates a warning that, for example, boost::python::list is not exposed and this might lead to errors at runtime. But of course, the list object is a built-in Boost.Python type, so this one doesn't need to be wrapped. So it would be nice if Py++ would be aware of the Boost.Python types and could suppress those warnings. At the moment, I don't have many warnings, so it's not such a big issue but I guess as a project grows you might get more and more of those which makes it harder to spot "real" warnings. - Matthias - |