pybind11/example/example5.ref

Rabbit is a parrot
Rabbit is a parrot
Polly is a parrot
Polly is a parrot
Molly is a dog
Molly is a dog
Woof!
The following error is expected: Incompatible function arguments. The following argument types are supported:
    1. (example.Dog) -> NoneType
    Invoked with: <example.Pet object at 0>
Callback function 1 called!
False
Callback function 2 called : Hello, x, True, 5
5
Callback function 2 called : Hello, from, partial, object
False
Callback function 3 called : Partial object with one argument
False
func(43) = 44
func(43) = 44
func(number=43) = 44
Payload constructor
Payload copy constructor
Payload move constructor
Payload destructor
Payload destructor
Payload destructor
argument matches dummy_function
eval(1) = 2
roundtrip..
argument matches dummy_function
eval(1) = 2
could not convert to a function pointer.
eval(1) = 3
could not convert to a function pointer.
All OK!
could not convert to a function pointer.
All OK!
general cleanup of the codebase - new pybind11::base<> attribute to indicate a subclass relationship - unified infrastructure for parsing variadic arguments in class_ and cpp_function - use 'handle' and 'object' more consistently everywhere 2016-01-17 21:36:44 +00:00			`Rabbit is a parrot`
			`Rabbit is a parrot`
			`Polly is a parrot`
avoid C++ -> Python -> C++ overheads when passing around function objects 2016-07-10 08:13:18 +00:00			`Polly is a parrot`
			`Molly is a dog`
general cleanup of the codebase - new pybind11::base<> attribute to indicate a subclass relationship - unified infrastructure for parsing variadic arguments in class_ and cpp_function - use 'handle' and 'object' more consistently everywhere 2016-01-17 21:36:44 +00:00			`Molly is a dog`
avoid C++ -> Python -> C++ overheads when passing around function objects 2016-07-10 08:13:18 +00:00			`Woof!`
general cleanup of the codebase - new pybind11::base<> attribute to indicate a subclass relationship - unified infrastructure for parsing variadic arguments in class_ and cpp_function - use 'handle' and 'object' more consistently everywhere 2016-01-17 21:36:44 +00:00			`The following error is expected: Incompatible function arguments. The following argument types are supported:`
			`1. (example.Dog) -> NoneType`
avoid C++ -> Python -> C++ overheads when passing around function objects 2016-07-10 08:13:18 +00:00			`Invoked with: <example.Pet object at 0>`
general cleanup of the codebase - new pybind11::base<> attribute to indicate a subclass relationship - unified infrastructure for parsing variadic arguments in class_ and cpp_function - use 'handle' and 'object' more consistently everywhere 2016-01-17 21:36:44 +00:00			`Callback function 1 called!`
			`False`
			`Callback function 2 called : Hello, x, True, 5`
			`5`
Better testing for callable python functions 2016-03-10 21:31:38 +00:00			`Callback function 2 called : Hello, from, partial, object`
			`False`
			`Callback function 3 called : Partial object with one argument`
			`False`
general cleanup of the codebase - new pybind11::base<> attribute to indicate a subclass relationship - unified infrastructure for parsing variadic arguments in class_ and cpp_function - use 'handle' and 'object' more consistently everywhere 2016-01-17 21:36:44 +00:00			`func(43) = 44`
avoid C++ -> Python -> C++ overheads when passing around function objects 2016-07-10 08:13:18 +00:00			`func(43) = 44`
Add callback examples with named parameters 2016-06-16 18:19:15 +00:00			`func(number=43) = 44`
avoid C++ -> Python -> C++ overheads when passing around function objects 2016-07-10 08:13:18 +00:00			`Payload constructor`
			`Payload copy constructor`
			`Payload move constructor`
			`Payload destructor`
			`Payload destructor`
			`Payload destructor`
			`argument matches dummy_function`
			`eval(1) = 2`
			`roundtrip..`
			`argument matches dummy_function`
			`eval(1) = 2`
			`could not convert to a function pointer.`
			`eval(1) = 3`
			`could not convert to a function pointer.`
			`All OK!`
			`could not convert to a function pointer.`
			`All OK!`