[pygccxml-development] Reducing or handling new warning output
Brought to you by:
mbaas,
roman_yakovenko
From: Allen B. <al...@vr...> - 2006-07-28 22:01:31
|
First off, I want to say that the new output is a vast improvement. I like how it tells you what the current issues are and tries to give a description of how to fix them. That said, it seems that some of the warnings could be nice to turn off or to have an easy way to auto handle in a generation script. For example: WARNING: __gnu_debug [namespace] > pyplusplus, by default, does not exposes internal compilers > declarations. Names of those declarations starts with "__". I understand this message, I don't want to export this namespace and as far as I know, I am not even attempting to export this namespace (does this message crop up even if the namespace is not exposed?). Is there any way to automatically remove all places where this would be triggered? it seems like a reasonable default. Another: WARNING: osg::FieldContainer & osg::FieldContainer::operator=(osg::FieldContainer const & other) [member_operator] > "operator=" is not supported. See Boost.Python documentation: > http://www.boost.org/libs/python/doc/v2/operators.html#introduction. Another good one. If I expose a class and it has an op=, then I don't want to expose it. But is there a way to just make this the default and not make me go through and remove them all manually to prevent these warnings from being spit out? -Allen |