Re: [C++-sig] Using C++ classes exposed by other modules

2010-10-19 Thread Nat Linden
On Thu, Oct 14, 2010 at 1:17 PM, Bryant Gipson wrote: C++: > > void mySlightlyHelpfulFunction(cppmodule::A &a) > { > ... > } > > Python: > a = mod.A() > myModule.mySlightlyHelpfulFunction(a) > myModule.mySlightlyHelpfulFunction(A) > did not match C++ signature: > mySlightlyHelpfulFunct

Re: [C++-sig] Using C++ classes exposed by other modules

2010-10-19 Thread Jim Bosch
On 10/19/2010 05:10 AM, Nat Linden wrote: On Thu, Oct 14, 2010 at 1:17 PM, Bryant Gipson mailto:gipso...@yahoo.com>> wrote: C++: void mySlightlyHelpfulFunction(cppmodule::A &a) { ... } Python: a = mod.A() myModule.mySlightlyHelpfulFunction(a) myModul

[C++-sig] boost::python + python3.1.2 throw

2010-10-19 Thread Neal Becker
Has behavior of c++ exception changed with boost::python + python3? I used to simply use throw from c++. Now I get: SystemError: initialization of ldpc_45 raised unreported exception I believe this exception was really: if (!fp) throw std::runtime_error ((boost::format ("fopen %1% failed")

Re: [C++-sig] boost::python + python3.1.2 throw

2010-10-19 Thread Neal Becker
Neal Becker wrote: > Has behavior of c++ exception changed with boost::python + python3? > > I used to simply use throw from c++. Now I get: > SystemError: initialization of ldpc_45 raised unreported exception > > I believe this exception was really: > if (!fp) > throw std::runtime_error