[C++-sig] Re: Boost.Python not resolving overloads
s_sourceforge at nedprod.com
Tue Sep 23 00:21:55 CEST 2003
-----BEGIN PGP SIGNED MESSAGE-----
On 20 Sep 2003 at 23:42, David Abrahams wrote:
> > Might it be an idea in the name of flexibility that boost.python
> > marks mixed static and non-static functions and tries matching the
> > static one first. If that fails, then it makes the first parameter
> > "self" and tries again.
> It *might* be an idea. If you can figure out how to make it work,
> I'll be glad to review your patch. From what I know about descriptors
> and how method binding works, though, I bet it's nontrivial.
<groan> I had an awful feeling you might say that.
Ok, tell me this: is function::call() the right place to alter? If
so, it would appear to me to be trivial - just insert the object
instance as the first parameter if all else fails.
As for adding knowledge if there are mixed static and non-static
methods, well, as I've said before in here I really don't understand
most of Boost.Python. I would imagine though that just altering the
parameter matching loop wouldn't cause any existing code to break -
so it should be okay?
Would I post a patch here, or to you directly? And is GNU diff format
-----BEGIN PGP SIGNATURE-----
Version: idw's PGP-Frontend 18.104.22.168 / 9-2003 + PGP 8.0.2
-----END PGP SIGNATURE-----
More information about the Cplusplus-sig