Re: [pygccxml-development] Two patches proposal

[Berserker <ber...@ho...>]

> I started to implement support for std::unordered_* and already found
> a first obstacle: gccxml. It is not able to handle C++0x code. I found
> this post: http://www.mail-archive.com/gc...@gc.../msg00462.html
> 
> So, in order Py++ and pygccxml support new containers, gccxml should
> support them first.
> 
> Tomorrow I will try to add support to boost::unordered containers.

Thanks, boost::unordered is what I need now :)
I have some custom containers that I need to expose too.
Actually I managed to compile this code:

boost::python::class_< std::map<std::string, int> >
("map_string_to_int")    
.def(boost::python::indexing::map_suite< std::map<std::string, int> >());

boost::python::class_< my_map<std::string, int> >
("my_map_string_to_int")    
.def(boost::python::indexing::map_suite< my_map<std::string, int> >());

but when I execute it an assert complains about an already registered
std::string to int mapped type, is there a workaround?
My question is (in reality) this: will there be the support to register simoultaneusly
the code I wrote in my previous post?

boost::python::class_< std::map<std::string, int> >
("map_string_to_int")    
.def(boost::python::indexing::map_suite< std::map<std::string, int> >());

boost::python::class_< boost::unordered_map<std::string, int> >
("unordered_map_string_to_int")    
.def(boost::python::indexing::map_suite< boost:unordered_map<std::string, int> >());

 		 	   		  
_________________________________________________________________
Sei bravo con le parole? Gioca su Typectionary
http://typectionary.it.msn.com/