Hello,
I want to expose to python following code:
typedef std::map ProbHaplotype;
typedef std::map ProbFenotype;
typedef std::map ProbGenotype;
(...)
std::ostream& operator<<(std::ostream& os, const ProbHaplotype& hapl);
std::ostream& operator<<(std::ostream& os, const ProbFenotype& fen);
st
2009/3/25 Michał Nowotka :
> Hello,
> I want to expose to python following code:
>
> typedef std::map ProbHaplotype;
>
> typedef std::map ProbFenotype;
>
> typedef std::map ProbGenotype;
>
> (...)
>
> std::ostream& operator<<(std::ostream& os, const ProbHaplotype& hapl);
>
> std::ostream& operator<
I'm wondering why the current map_indexing_suite is the way it is. Is
there any reason not to enhance it to support now standard methods like
keys(), values(), popitem() and the like?
-t
___
Cplusplus-sig mailing list
Cplusplus-sig@python.org
http://
Hello,
First of all I found that set of return value polices mention in
boost.python documentation
(http://www.boost.org/doc/libs/1_38_0/libs/python/doc/tutorial/doc/html/python/functions.html#python.call_policies):
* reference_existing_object
* copy_const_reference
* copy_non_const_r
2009/3/25 Michał Nowotka :
> Hello,
>
> First of all I found that set of return value polices mention in
> boost.python documentation
> (http://www.boost.org/doc/libs/1_38_0/libs/python/doc/tutorial/doc/html/python/functions.html#python.call_policies):
>
> * reference_existing_object
> * copy
And one more question - what about user-defined exceptions?
Suppose I have following code from library which I cannot modify:
namespace faif
{
class FaifException : public std::exception {
public:
FaifException(){}
virtual ~FaifException() throw() {
2009/3/25 Michał Nowotka :
> And one more question - what about user-defined exceptions?
> Suppose I have following code from library which I cannot modify:
>
> namespace faif
>
> {
>
>
> class FaifException : public std::exception {
>
> public:
>
> FaifException(){}
>
>
On 23 Mar 2009 at 11:42, Renato Araujo wrote:
> For more details about the problem, I found the correct header witch
> give me this problem, and isolate that with this:
>
> #include
> # include
> # include
>
> #pragma GCC visibility push(default)
> #include
> #pragma GCC visibility pop
>
>
> If you use SVN version, than you can "include" the classes.
Ok, so I've checked out svn repository and reinstalled pygccxmm and
py++ from pygccxml_dev and pyplusplus_dev but I still get same
warnings. Should I do something else to include these classes?
--
Regards
Michał Nowotka
