Hi Randolph,
I wish you and your work well, but I don't see how I can do this.
NodeCallback and NodeVisitor are exactly where I ran into problems with
osgswig--they are important, and hard to get right.
Actually I don't know if you saw my messages from last night, but it
works fine now. But
J-S,
I wish you and your work well, but I don't see how I can do this.
NodeCallback and NodeVisitor are exactly where I ran into problems
with osgswig--they are important, and hard to get right. As with
osgswig, I'd be testing your bindings, rather than concentrating on my
thesis work.
Thanks for the suggestion--I may give this a try.
Randolph
On Sep 8, 2009, at 12:27 PM, Roman Yakovenko wrote:
On Tue, Sep 8, 2009 at 9:35 PM, R Fritz
wrote:
I am working on an OpenSceneGraph/Python project and have had to
abandon the
OSG/SWIG tools--they are not developed enough for my pur
Nicolas Lelong wrote:
You may disambiguate by using a cast inside .def(), such as
.def("getA", (A*(B::*)())B::getA);
Whether that's actually more readable is arguable, however.
IMHO, this is quite dangerous as the explicit cast prevents the compiler
to give you a proper error if the signa
Jean-Sébastien Guay wrote:
> Hi Stefan,
>
>> This is not a wrapper function, but an alias. You create a new variable
>> 'B_getA1', and make this point to B::getA (the non-const version).
>> This works, since by means of the variable type you disambiguate, so
>> using that in the call to def() wor
You may disambiguate by using a cast inside .def(), such as
.def("getA", (A*(B::*)())B::getA);
Whether that's actually more readable is arguable, however.
IMHO, this is quite dangerous as the explicit cast prevents the compiler to
give you a proper error if the signature of B::getA changes
