Doc fix for OVERLOAD*_NAME macros

The documentation says the string-valued python function name goes
after the C++ function, but it actually goes before it.
This commit is contained in:
Jason Rhinelander 2016-08-29 16:58:59 -04:00
parent 7946715d02
commit 64830e3333

View File

@ -298,9 +298,10 @@ functions, and :func:`PYBIND11_OVERLOAD` should be used for functions which have
a default implementation. a default implementation.
There are also two alternate macros :func:`PYBIND11_OVERLOAD_PURE_NAME` and There are also two alternate macros :func:`PYBIND11_OVERLOAD_PURE_NAME` and
:func:`PYBIND11_OVERLOAD_NAME` which take a string-valued name argument :func:`PYBIND11_OVERLOAD_NAME` which take a string-valued name argument between
after the *Name of the function* slot. This is useful when the C++ and Python the *Parent class* and *Name of the function* slots. This is useful when the
versions of the function have different names, e.g. ``operator()`` vs ``__call__``. C++ and Python versions of the function have different names, e.g.
``operator()`` vs ``__call__``.
The binding code also needs a few minor adaptations (highlighted): The binding code also needs a few minor adaptations (highlighted):