On Monday 12 October 2009 08:47:22 troy d. straszheim wrote:
> >>boost::function bf0(fobj);
> >
> >
> > Why do you need to use boost::function here? Shouldn't the type be
> > deduced automatically?
> >
>
> Note that the .def() of the various boost::function objects work without
> requiring
Ravi wrote:
On Sunday 11 October 2009 19:44:29 troy d. straszheim wrote:
Why is the overloaded get_signature not picked up when it is declared
after the inclusion of the headers?
I'm not sure why it isn't picked up.
Does that mean that you can reproduce the problem I pointed out?
Yes I ca
On Sunday 11 October 2009 19:44:29 troy d. straszheim wrote:
> > Why is the overloaded get_signature not picked up when it is declared
> > after the inclusion of the headers?
>
> I'm not sure why it isn't picked up.
Does that mean that you can reproduce the problem I pointed out?
> I've been wo
Ravi wrote:
[snip]
In order to use a function object in place of a free function, one must
specialize/overload
boost::python::detail::get_signature
which, for some reason, does not account for function objects. Here's a very
simple example that works:
[snip]
However, note that the over
Hello,
If a free function 'func' has X* as its first argument, then, boost.python
allows it to be bound to a member function on the python side, i.e., the
following is legal:
void func( X* x, arg1_t arg ) { ... }
class_( "X" ).def( "func", &func );
In order to use a function object in plac
