Mailman 3 June 2005 - Cplusplus-sig

Re: [C++-sig] Raw member and constructor functions
by Studious Apprentice June 6, 2005

June 6, 2005

Thanks a lot for this fast answer ! This looks like the way to go. The following code does compile but the result under python is unexpected : #include <boost/python.hpp> #include <boost/python/raw_function.hpp> using namespace boost::python; namespace { class X { public: object memberraw(const tuple& args, const dict& kw) { return make_tuple(args, kw); } }; object memberrawfwd(tuple raw, dict kw) { tuple arg = extract<tuple&>(raw.slice(1, _))(); return extract<X&>(raw[0])(). memberraw(arg, kw); } }; BOOST_PYTHON_MODULE(PythonTest) { class_<X>("X") .def("memberraw", raw_function(memberrawfwd)) ; } However the following results when run with Python : >>>a = X() >>>a.memberraw() Traceback (most recent call last): File "<stdin>", line 1, in ? TypeError: No registered converter was able to extract a C++ reference to type c lass boost::python::tuple from this Python object of type tuple >>> Any further help ? Thanks in advance, Marc -----Original Message----- From: c++-sig-bounces(a)python.org [mailto:c++-sig-bounces@python.org] On Behalf Of David Abrahams Sent: lundi 6 juin 2005 04:31 To: c++-sig(a)python.org Subject: Re: [C++-sig] Raw member and constructor functions "Studious Apprentice" <apprentice_99(a)hotmail.com> writes: >Hello ! > >I would like to use raw member functions and a raw constructor. However I >can only manage to have raw functions to work. > >The following code works : > >#include <boost/python.hpp> >#include <boost/python/raw_function.hpp> >using namespace boost::python; > >tuple raw(tuple args, dict kw) >{ > return make_tuple(args, kw); >} > >BOOST_PYTHON_MODULE(PythonTest) >{ > def("raw", raw_function(raw)); >} > >However this code does not compile with MSVC7.1 and results in "error >C2064: term does not evaluate to a function taking 2 arguments" : > >#include <boost/python.hpp> >#include <boost/python/raw_function.hpp> >using namespace boost::python; > >class X { >public: > object memberraw(tuple args, dict kw) > { > return object(); > } >}; > >BOOST_PYTHON_MODULE(PythonTest) >{ > class_<X>("X") > .def("memberraw", raw_function(&X::memberraw)) > ; >} As http://www.boost.org/libs/python/doc/v2/raw_function.html says, f(tuple(), dict()) must be well-formed where f is the argument to raw_function. That's clearly not the case here. This might work: tuple raw(tuple raw, dict kw) { extract<X&>(raw[0])().memberraw(raw.slice(1), kw); } BOOST_PYTHON_MODULE(PythonTest) { class_<X>("X") .def("memberraw", raw_function(raw)) ; } -- Dave Abrahams Boost Consulting www.boost-consulting.com _______________________________________________ C++-sig mailing list C++-sig(a)python.org http://mail.python.org/mailman/listinfo/c++-sig

2 1

Raw member and constructor functions
by Studious Apprentice June 6, 2005

June 6, 2005

Hello ! I would like to use raw member functions and a raw constructor. However I can only manage to have raw functions to work. The following code works : #include <boost/python.hpp> #include <boost/python/raw_function.hpp> using namespace boost::python; tuple raw(tuple args, dict kw) { return make_tuple(args, kw); } BOOST_PYTHON_MODULE(PythonTest) { def("raw", raw_function(raw)); } However this code does not compile with MSVC7.1 and results in "error C2064: term does not evaluate to a function taking 2 arguments" : #include <boost/python.hpp> #include <boost/python/raw_function.hpp> using namespace boost::python; class X { public: object memberraw(tuple args, dict kw) { return object(); } }; BOOST_PYTHON_MODULE(PythonTest) { class_<X>("X") .def("memberraw", raw_function(&X::memberraw)) ; } Anyone would have an idea of how to get this working ? Thanks in advance, Marc

2 1

Re: [C++-sig] _POSIX_C_SOURCE redefinition warning with python 2.3and boost-1.31.0
by aashish＠iastate.edu June 3, 2005

June 3, 2005

Thanks Dave. Here is what I am getting on my console when I am trying to compile Boost. On googling I found that I am getting this warning because, of the importance of include order for Python header files. Should I ignore these warnings? or what I can do to get rid of these warnings ? Also due to unfamiliarity with CVS , I have to ask this rather stupid question. When you say Revision_1_31_0 does it mean it is a tag or branch in CVS ? I believe in Boost RC_n_n_n stands for release version and there is a separate tag Version_n_n_n. Thanks in advance. ~Ashish /usr/local/include/python2.3/pyconfig.h:856:1: warning: "_POSIX_C_SOURCE" redefined In file included from /usr/include/limits.h:26, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/limits.h:122, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/syslimits.h:7, from /usr/lib/gcc/i386-redhat-linux/3.4.3/include/limits.h:11, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/detail/wrap_python.hpp:27, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/detail/prefix.hpp:13, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/type_id.hpp:9, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/boost/python/converter/registry.hpp:8, from /home/software/vrjuggler/cvs_version/VRJ_2_0_ALPHA_4_BRANCH/juggler_deps/source/boost/libs/python/build/../src/converter/registry.cpp:6: /usr/include/features.h:150:1: warning: this is the location of the previous definition

5 5

custom smart pointer, vector_indexing_suite typeerror
by Scott McKay June 2, 2005

June 2, 2005

Is the following possible or am I doing something wrongly? I have a custom smart pointer, and an abstract base class that is wrapped specifying smart_ptr<X> as the HeldType, as I want to treat the object as if it's automatically wrapped with a smart_ptr. I then have a std::vector<smart_ptr<X>> exposed using the vector_indexing_suite with proxying turned off. Basically something along these lines... struct X_Wrapper: X { X_Wrapper(PyObject* py_self_): X(), py_self(py_self_) {} X& run() { return call_method< X& >(py_self, "run"); } } class_< X, X_Wrapper, boost::noncopyable, smart_ptr< X > >("X", init<>()) .def("run", pure_virtual(&X::run), return_self<>()) ; class_< std::vector< smart_ptr<X> > > ( "vector_X" ) .def( vector_indexing_suite< std::vector< smart_ptr<X> >, true >() ) ; Then in the python code I want to implement the X interface and add the python object that does so to the vector. class testX( X ): def run( self ): print "run" return self tester = testX() vector = vector_X() vector.append( tester ) Doing so leads to a type error in the append (from the base_append of the vector_indexing_suite). The object type is a 'testX', which I thought would be held as a smart_ptr<X> under the covers and hence would be convertible, but I guess that isn't the case. As the vector takes a non-const I thought it was necessary to use the HeldType rather than register_ptr_to_python. Is there a way to make this work? I'm not sure I have everything setup correctly though, so perhaps I'm missing a piece. Thanks for any help. Scott

2 3

Re: [C++-sig] _POSIX_C_SOURCE redefinition warning with python 2.3and boost-1.31.0
by aashish＠iastate.edu June 2, 2005

June 2, 2005

Hi, I am using one of the library which uses Boost. When I was trying to compile boost on my linux (fedora core 3) machine I was getting warnings about POSIX_C_SOURCE redefinition. I found this post http://lists.boost.org/MailArchives/boost/msg61875.php and I believe that I need to check out cvs version but not exactly sure which branch I have to check out (for verison 1.31.0). I have to use boost 1.31.0 to make this library work (an older version). My system is: Fedora core 3 python 2.3.5 boost 1.31.0 Thanks for your help. ~Regards, Ashish ----------------------------------------------- Aashish Chaudhary Technical Programmer, PRISM Email: ashish_cy(a)yahoo.com Ph: (480) 275-0755 -----------------------------------------------

2 1

Pyste's AllFromHeader()
by Niall Douglas June 1, 2005

June 1, 2005

How's that function looking now in pyste? It is fully working yet? I was strongly thinking of finishing off TnFOX's python bindings and for that we'll need AllFromHeader() working, or at least 98% working. Cheers, Niall

2 1