[pygccxml-development] Handling of enum value as default for parameter
Brought to you by:
mbaas,
roman_yakovenko
From: Patrick H. <pat...@pr...> - 2008-06-25 16:35:53
|
I have run into a case where Py++ is generating C++ code that does not compile, and I am trying to determine if the problem lies with GCC-XML or Py++. Code demonstrating what I am working with is attached. What happens is that Py++ creates code for Y::setValue() similar to the following: Y_exposer.def("setValue", &Y::setValue, (bp::arg("v") = (int)(V1))); The use of X::V1 requires scoping in order to compile, but this is not happening. This is occurring with GCC-XML built from CVS HEAD sources as of yesterday and Py++ and PyGCCXML r1348. The relevant XML is shown below: <Method id="_151" name="setValue" returns="_134" context="_124" access="public" mangled="_ZN1Y8setValueEi" demangled="Y::setValue(int)" location="f1:10" file="f1" line="10" extern="1"> <Argument name="v" type="_129" location="f1:10" file="f1" line="10" default="V1"/> </Method> Should Py++ be resolving the scope of X::V1, or should GCC-XML do that up front? -Patrick -- Patrick L. Hartling Senior Software Engineer, Priority 5 http://www.priority5.com/ |