Mailman 3 November 2006 - Cplusplus-sig

Base class defined in other header file not included in bp::bases<>
by Haridev, Meghana Sept. 14, 2008

Sept. 14, 2008

Hi Folks, I'm having some trouble generating boost-python wrapper code using pyplusplus for a derived class which has one of its base classes defined in another file. Simple scenario: mydir/ other.hpp: class baseB{ }; hierarchy.hpp: #include "other.hpp" class baseA{ }; class derivedC: public baseA, public baseB{ }; generate_code.py: import os from pyplusplus import module_builder mb = module_builder.module_builder_t( files=['hierarchy.hpp'] ) mb.build_code_creator( module_name='inherit' ) mb.code_creator.user_defined_directories.append( os.path.abspath('.') ) mb.write_module('boost_hierarchy.cpp') ------------------------------------------------------------------------ ------------------------------------------------- Generated code (boost_hierarchy.cpp) looks like this: // This file has been generated by pyplusplus. #include "boost/python.hpp" #include "hierarchy.hpp" namespace bp = boost::python; BOOST_PYTHON_MODULE(inherit){ bp::class_< baseA >( "baseA" ); bp::class_< derivedC, bp::bases< baseA > >( "derivedC" ); } How can I get pyplusplus to add 'baseB' to bp::bases<> for 'derivedC' class when 'baseB' class is defined in another file (present in the same directory or different directory)? When I move the definition of 'baseB' class to hierarchy.hpp, boost wrapper for 'derivedC' is correctly generated as: bp::class_< derivedC, bp::bases< baseA, baseB > >( "derivedC" ); Thanks, -Meghana.

3 9

'iteritems', 'iterkeys' and 'itervalues' in dict
by Nindi Singh April 11, 2008

April 11, 2008

Apolgies for not putting the subject line in my last email. In the Boost.Python dict class there are methods 'iteritems', 'iterkeys' and 'itervalues' all returning objects. How exactly are you supposed to use these objects (iterators) ? ___________________________________________________________ Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

2 1

C++ singleton
by Emmanuel Taurel Oct. 31, 2007

Oct. 31, 2007

Hello everybody, I am actually writing an interface to python for an existing C++ library using Boost. This library has a C++ singleton class. This class has only one constructor (with arguments) which is "protected" because it's a singleton. I am not able to build a Boost interface to this class because the compiler complains that the constructor I have given to Boost in the class_xxx constructor argument is not public (which is true) ! Therefore, my question is simple : How is it possible to interface such a class with only one constructor which is protected and a static method to create/access the object ? Thank's very much for your answer. Sincerely Emmanuel Taurel (etaurel(a)cells.es) PS : By the way, is there a searchable archive of this mailing list ?

4 3

Supplying a Python base class when wrapping a C++ class...
by Alex Mohr April 19, 2007

April 19, 2007

I'd like to wrap a C++ class and have the generated python wrapper class derive from a Python class. I know I can use bases<> to have my wrapped class derive from the class objects associated with the C++ types I specify in bases<>, but in this instance, I want to derive my wrapper class from a Python class that was not generated by boost.python. From looking at the code, it seems like it would be some work to add this capability. (Is anyone working on something like this?) As a workaround, does anyone know a way that I could perhaps hack this in after the Python class is created? That is, can I change the Python base classes of a Python class at runtime? Thanks, Alex

5 7

boost::langbinding?
by anders langlands Dec. 7, 2006

Dec. 7, 2006

Whatever happened to boost::langbinding? Is the project completely dead in the water? It seemed like a pretty good idea to have one library to handle binding to all your favourite 'scripting languages' A

2 1

Extending Python with not-basic-c++
by David Sveningsson Dec. 3, 2006

Dec. 3, 2006

Hi, I have a working C++ game. To make it easier to extend/control/whatever some kind of scripting support is required. I know Python isn't really a scripting language but it seems like the best choice. I should also note that my knowledge of python is very limited. I heard that embedding python isn't a good way so I'm about to extend python with my functionality. At first I would like to just replace my game loop from C++ to python. It's basically a class with a method that keeps looping until the game is finished. But this class and all other classes inherits from a common 'object' class. And all memory is allocated through a memory manager. Also, the object class is dependent on a couple of other classes. And circular dependencies is not uncommon. It is not possible to loose this coupling. When compiling a class module for python it says undefined symbol 'a class method here'. So I include that class-objectfile when I compile the module. Eventfully it works but I cant do like this. Can someone give me a few directions? I don't really understand how to do this.

3 8

compile error in iterator
by Kelly Burkhart Dec. 1, 2006

Dec. 1, 2006

I have a GzipFile class which exposes a gzipped file as a python file. I have written an iterator over this class which I use to iterate over an instance of this class. I'm using 1.33.1 and my code compiles cleanly and works on Linux g++ 3.3.5. I am now trying to build on Windows using msvc.net (cl 13.10.6030). This compiler complains that bost::python::objects::iterator_range<NextPolicies,Iterator>::next is not accessible (full compiler complaint below). Does anyone have a solution, or hint to how I can go about fixing this? Thank you in advance for any assistance. This code reproduces the problem: <begin> #include <boost/python.hpp> #include <boost/iterator/iterator_facade.hpp> #include <vector> #include <string> using namespace boost::python; //-------------------------------------------------------------------------------------------------- // class ItTstIterator : public boost::iterator_facade< ItTstIterator, std::string, boost::forward_traversal_tag, std::string > { public: ItTstIterator( std::vector<std::string>::iterator it ) : it_(it) {} virtual ~ItTstIterator() {} private: friend class boost::iterator_core_access; void increment() { ++it_; } bool equal( const ItTstIterator &it ) const { return it_ == it.it_; } std::string dereference() const { return *it_; } private: std::vector<std::string>::iterator it_; }; //-------------------------------------------------------------------------------------------------- class ItTst { public: typedef ItTstIterator iterator; ItTst() { vec_.push_back("one");vec_.push_back("two");vec_.push_back("three"); } ~ItTst() {} // For iteration ItTstIterator begin() { return ItTstIterator( vec_.begin() ); } ItTstIterator end() { return ItTstIterator( vec_.end() ); } private: std::vector< std::string > vec_; }; void wrapPyIter() { class_<ItTst>("ItTst", init<>() ) .def("__iter__", iterator<ItTst>()) ; } <end> And here is the full compiler complaint: cl -c -nologo -GX -GR -Zc:forScope -wd4101 -wd4290 -wd4100 -wd4189 -DWIN32 -Zi -Od -D_DEBUG -DFD_SETSIZE=512 -MDd -Zi -Od -D_DEBUG -DFD_SETSIZE=512 -MDd -DBOOST_SIGNALS_NAMESPACE=tb_signals -D__x86__ -D__NT__ -D__OSVERSION__=5 -D__WIN32__ -GR -EHsc -W3 -w34100 -w34189 -DWIN32 -DQT_LARGEFILE_SUPPORT -DCOMPILE_DL=1 -DQT_DLL -DQT_PLUGIN -DQT_QT3SUPPORT_LIB -DQT3_SUPPORT -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_THREAD_SUPPORT -D_WIN32_WINNT=0x0500 -DFD_SETSIZE=512 -DNOMINMAX -I"C:/Qt/4.2.1/include/QtCore" -I"C:/Qt/4.2.1/include/QtCore" -I"C:/Qt/4.2.1/include/QtNetwork" -I"C:/Qt/4.2.1/include/QtNetwork" -I"C:/Qt/4.2.1/include/QtGui" -I"C:/Qt/4.2.1/include/QtGui" -I"C:/Qt/4.2.1/include/QtXml" -I"C:/Qt/4.2.1/include/QtXml" -I"C:/Qt/4.2.1/include/Qt3Support" -I"C:/Qt/4.2.1/include/Qt3Support" -I"C:/Qt/4.2.1/include" -I"..\Common" -I"..\libtbut" -I"C:/Qt/4.2.1/include/ActiveQt" -I"moc" -I"..\libtbut" -I"ui" -I"C:/postgresql\src\interfaces\libpq" -I"C:/postgresql\src\include" -I"C:/Python25/include" -I"C:/Boost/include/boost-1_33_1" -I"c:\omni\omniORB-4.0.3\include" -I"c:\Qt\4.2.1\mkspecs\win32-msvc.net" -Fodebug\ @c:\DOCUME~1\kelly\LOCALS~1\Temp\nm99.tmp wrap_py_iter.cpp C:/Boost\include\boost-1_33_1\boost\detail\compressed_pair.hpp(347) : error C2247: 'boost::python::objects::iterator_range<NextPolicies,Iterator>::next' not accessible because 'boost::details::compressed_pair_imp<T1,T2,Version>' uses 'private' to inherit from 'boost::python::objects::iterator_range<NextPolicies,Iterator>::next' with [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const ] and [ T1=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, T2=boost::python::return_value_policy<boost::python::return_by_value>, Version=3 ] and [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(51) : see declaration of 'boost::python::objects::iterator_range<NextPolicies,Iterator>::next' with [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(51) : see declaration of 'boost::python::objects::iterator_range<NextPolicies,Iterator>::next' with [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const ] C:/Boost\include\boost-1_33_1\boost\python\detail\caller.hpp(212) : see reference to class template instantiation 'boost::compressed_pair<T1,T2>' being compiled with [ T1=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, T2=boost::python::return_value_policy<boost::python::return_by_value> ] C:/Boost\include\boost-1_33_1\boost\python\detail\caller.hpp(145) : see reference to class template instantiation 'boost::python::detail::caller_arity<1>::impl<F,Policies,Sig>' being compiled with [ F=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, Policies=boost::python::return_value_policy<boost::python::return_by_value>, Sig=boost::mpl::vector2<result_type,range_ &> ] C:/Boost\include\boost-1_33_1\boost\python\make_function.hpp(37) : see reference to class template instantiation 'boost::python::detail::caller<F,CallPolicies,Sig>' being compiled with [ F=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, CallPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Sig=boost::mpl::vector2<result_type,range_ &> ] C:/Boost\include\boost-1_33_1\boost\python\make_function.hpp(89) : see reference to function template instantiation 'boost::python::api::object boost::python::detail::make_function_aux<F,CallPolicies,Signature>(F,const CallPolicies &,const Sig &)' being compiled with [ F=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, CallPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Signature=boost::mpl::vector2<result_type,range_ &>, Sig=boost::mpl::vector2<result_type,range_ &> ] C:/Boost\include\boost-1_33_1\boost\python\make_function.hpp(129) : see reference to function template instantiation 'boost::python::api::object boost::python::detail::make_function_dispatch<F,CallPolicies,KeywordsOrSignature>(F,const CallPolicies &,const Signature &,boost::mpl::false_)' being compiled with [ F=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, CallPolicies=boost::python::return_value_policy<boost::python::return_by_value>, KeywordsOrSignature=boost::mpl::vector2<result_type,range_ &>, Signature=boost::mpl::vector2<result_type,range_ &> ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(137) : see reference to function template instantiation 'boost::python::api::object boost::python::make_function<boost::python::objects::iterator_range<NextPolicies,Iterator>::next,NextPolicies,boost::mpl::vector2<T0,T1>>(F,const CallPolicies &,const KeywordsOrSignature &)' being compiled with [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const, T0=result_type, T1=range_ &, F=boost::python::objects::iterator_range<boost::python::return_value_policy<boost::python::return_by_value>,iterator_const>::next, CallPolicies=boost::python::return_value_policy<boost::python::return_by_value>, KeywordsOrSignature=boost::mpl::vector2<result_type,range_ &> ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(163) : see reference to function template instantiation 'boost::python::api::object boost::python::objects::detail::demand_iterator_class<Iterator,boost::python::return_value_policy<ResultConverterGenerator>>(const char *,Iterator *,const NextPolicies &)' being compiled with [ Iterator=const iterator_const, ResultConverterGenerator=boost::python::return_by_value, NextPolicies=boost::python::return_value_policy<boost::python::return_by_value> ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(161) : while compiling class-template member function 'boost::python::objects::iterator_range<NextPolicies,Iterator> boost::python::objects::detail::py_iter_<Target,Iterator,Accessor1,Accessor2,NextPolicies>::operator ()(boost::python::back_reference<T>) const' with [ NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Iterator=iterator_const, Target=ItTst, Accessor1=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, Accessor2=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, T=ItTst & ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(187) : see reference to class template instantiation 'boost::python::objects::detail::py_iter_<Target,Iterator,Accessor1,Accessor2,NextPolicies>' being compiled with [ Target=ItTst, Iterator=iterator_const, Accessor1=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, Accessor2=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, NextPolicies=boost::python::return_value_policy<boost::python::return_by_value> ] C:/Boost\include\boost-1_33_1\boost\python\object\iterator.hpp(239) : see reference to function template instantiation 'boost::python::api::object boost::python::objects::detail::make_iterator_function<Target,T,NextPolicies,Accessor1,Accessor2>(const Accessor1 &,const Accessor2 &,const NextPolicies &,Iterator &(__cdecl *)(void),boost::type<Target> *,int)' being compiled with [ Target=ItTst, T=const iterator_const, NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Accessor1=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, Accessor2=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, Iterator=const iterator_const ] C:/Boost\include\boost-1_33_1\boost\python\iterator.hpp(39) : see reference to function template instantiation 'boost::python::api::object boost::python::objects::make_iterator_function<Target,NextPolicies,boost::_bi::protected_bind_t<F>,boost::_bi::protected_bind_t<F>>(const Accessor1 &,const Accessor2 &,const NextPolicies &,boost::type<T> *)' being compiled with [ Target=ItTst, NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, F=boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>, Accessor1=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, Accessor2=boost::_bi::protected_bind_t<boost::_bi::bind_t<boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator,boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &),boost::_bi::list1<boost::_bi::list_av_1<boost::arg<1>>::B1>>>, T=ItTst ] C:/Boost\include\boost-1_33_1\boost\python\iterator.hpp(96) : see reference to function template instantiation 'boost::python::api::object boost::python::detail::make_iterator<T,boost::python::detail::iterators_impl<const_>::apply<T>::iterator(__cdecl *)(T &),boost::python::detail::iterators_impl<const_>::apply<T>::iterator(__cdecl *)(T &),boost::python::return_value_policy<ResultConverterGenerator>>(Accessor1,Accessor2,NextPolicies,Target &(__cdecl *)(void))' being compiled with [ T=ItTst, const_=false, ResultConverterGenerator=boost::python::return_by_value, Accessor1=boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &), Accessor2=boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &), NextPolicies=boost::python::return_value_policy<boost::python::return_by_value>, Target=ItTst ] C:/Boost\include\boost-1_33_1\boost\python\iterator.hpp(120) : see reference to function template instantiation 'boost::python::api::object boost::python::range<NextPolicies,boost::python::detail::iterators_impl<const_>::apply<T>::iterator(__cdecl *)(T &),boost::python::detail::iterators_impl<const_>::apply<T>::iterator(__cdecl *)(T &)>(Accessor1,Accessor2,NextPolicies *)' being compiled with [ NextPolicies=boost::python::objects::default_iterator_call_policies, const_=false, T=ItTst, Accessor1=boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &), Accessor2=boost::python::detail::iterators_impl<false>::apply<ItTst>::iterator (__cdecl *)(ItTst &) ] C:/Boost\include\boost-1_33_1\boost\python\iterator.hpp(116) : while compiling class-template member function 'boost::python::iterator<Container>::iterator(void)' with [ Container=ItTst ] wrap_py_iter.cpp(48) : see reference to class template instantiation 'boost::python::iterator<Container>' being compiled with [ Container=ItTst ] NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. NMAKE : fatal error U1077: '"c:\Program Files\Microsoft Visual Studio .NET 2003\VC7\BIN\nmake.exe"' : return code '0x2' Stop.

2 4

py++ and std::bitset
by Kirill Lapshin Nov. 30, 2006

Nov. 30, 2006

Roman, Currently py++ (or, rather pygccxml) complains about std::bitset. It is a mere warning, and does not affect me -- I am not exposing any bitsets to python yet. Still I am a bit worrying that I might have such a need in future. It might very well be that this warning is really harmless in this particular case, and can be ignored. Could you verify my analysis? I am using gccxml from CVS (reasonably recent, though not the latest) built on cygwin, cygwin gcc 3.4.4, Py++ and pygccxml 0.8.2. The problem arises from _Base_bitset<size_t _Nw> that has member _WordT _M_w[_Nw]. Gccxml reports that max for this array is (_Nw-1) which pygccxml does not recognize (it expects a number). _Base_bitset is a private base of std::bitset. I am getting warning: UserWarning: unable to find out array size from expression "(_Nw - 1)" I suppose that won't affect exposing bitset since it is a member of private base, which I don't really have (and can't) expose anyways. Is it so? Can something be done on pygccxml to support templated arrays, and effectively remove this warning? Regards, Kirill

2 1

Multiple modules in a file
by David Sveningsson Nov. 28, 2006

Nov. 28, 2006

Hi, I am quite new at extending python with c++. I am using the boost libraries on gnu/linux. I have many classes (with inheritance) that I would like to expose to python. Is there some way to have many python modules in one file? Like, core.so contains a string class and a memory class. I tried just compiling everything as a shared library and importing into python with "import core.string" but then I get the error "ImportError: dynamic module does not define init function (initcore)" Im not really sure what that means.

3 3

Re: [C++-sig] Wrapping a base class' method
by Ralf W. Grosse-Kunstleve Nov. 28, 2006

Nov. 28, 2006

Write a thin wrapper and .add_property that, e.g. (untested) int get_base_i_directly(my_class const& self) { return self.get_base_i(); } ... .add_property("basei", make_function(get_base_i_directly)) This way Boost.Python only "sees" my_class in the signature. ----- Original Message ---- From: "bernhard.maeder(a)zkb.ch" <bernhard.maeder(a)zkb.ch> To: c++-sig(a)python.org Sent: Sunday, November 19, 2006 11:30:28 PM Subject: [C++-sig] Wrapping a base class' method Hello all I'm trying to export some base class' methods with the derived class directly. See the following code: // ----------------------------------------------------- #include <boost/python.hpp> struct my_base_class { int const & get_base_i() const { return i_; } int i_; }; struct my_class : my_base_class { int const & get_i() const { return i_; } int i_; }; using namespace boost::python; BOOST_PYTHON_MODULE(_test) { class_<my_class>("MyClass") .add_property("i", make_function(&my_class::get_i, return_value_policy<copy_const_reference>())) .add_property("basei", make_function(&my_class::get_base_i, return_value_policy<copy_const_reference>())) ; } // ----------------------------------------------------- Now python throws the following at me: h[ 1] >>> from _test import * h[ 1] >>> MyClass().basei Traceback (most recent call last): File "<stdin>", line 1, in ? Boost.Python.ArgumentError: Python argument types in None.None(MyClass) did not match C++ signature: None(my_base_class {lvalue}) So, my question is: Am I not supposed to do this at all? The same seems to work flawlessly when returning by value instead of by reference.... Thanks for your input Bernhard ___________________________________________________________________ Disclaimer: Diese Mitteilung ist nur fuer die Empfaengerin / den Empfaenger bestimmt. Fuer den Fall, dass sie von nichtberechtigten Personen empfangen wird, bitten wir diese hoeflich, die Mitteilung an die ZKB zurueckzusenden und anschliessend die Mitteilung mit allen Anhaengen sowie allfaellige Kopien zu vernichten bzw. zu loeschen. Der Gebrauch der Information ist verboten. This message is intended only for the named recipient and may contain confidential or privileged information. If you have received it in error, please advise the sender by return e-mail and delete this message and any attachments. Any unauthorised use or dissemination of this information is strictly prohibited. _______________________________________________ C++-sig mailing list C++-sig(a)python.org http://mail.python.org/mailman/listinfo/c++-sig ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com

2 1