Closed GoogleCodeExporter closed 9 years ago
I'll look into it.
Why hasn't this issue been reported earlier? Does the issue only appear when
you perform such language bindings, but not in regular C++ development?
Original comment by erwin.coumans
on 19 Feb 2014 at 6:56
Thanks.. I assume it hasn't been noticed earlier because the issues only show
up during template instantiation, which only happens if somebody attempts to
actually use one of the relevant methods with one of the problem types.
Unfortunately, since the bindings being produced with cppyy have no idea what
routines will or won't want to be used by any given Python program, they
attempt to instantiate everything by default, and thus trigger the issue.
I've actually run into similar issues with the "findBinarySearch",
"findLinearSearch", and "remove" methods on btAlignedObjectArray as well,
because they assume that the contained type will have "<", ">", or "=="
operators, which many don't. I've managed to work around this by explicitly
excluding specific cases of those methods one-by-one from the bindings (which
is ugly, but at least works).
Unfortunately this issue with the constructors is much harder to work around
because I can't currently figure out a way to exclude just certain constructors
from the binding (and copy constructors are "contagious" in C++, so even when I
can exclude them, they get pulled back in and instantiated anyway by the
(implicit) copy constructors of other classes which contain
btAlignedObjectArrays as members, and it's all just a big mess)..
Original comment by foogod@gmail.com
on 19 Feb 2014 at 10:55
moved to github tracker here:
https://github.com/bulletphysics/bullet3/issues/56
Original comment by erwin.coumans
on 30 Mar 2014 at 4:58
Original issue reported on code.google.com by
foogod@gmail.com
on 15 Jan 2014 at 12:47Attachments: