w.richert at gmx.net
Sat Mar 28 19:05:46 UTC 2009
Swig has conceptually no chance (at least none that I know of) to dynamically
bind template based class of static language. If that would be possible one
would have to ship its swig using project always with all C++/swig/py-binding
Maybe I have come too accustomed to the "type safety has to come with
unittesting"-idiom by programming too much Python ;-)
On Samstag 28 März 2009 08:33:45 you wrote:
> also sprach Willi Richert <w.richert at gmx.net> [2009.03.28.0004 +0100]:
> > It is needed so that bindings with dynamic typing (Python) don't
> > have to instantiate each possible dim x type combination. The
> > dimension is only specified once at the constructor.
> That change sacrifices all the type-safety of C++ though. Now all of
> a sudden, a 3D-tree is of the same type as a 4D-tree. I don't like
> it. There must be a better way for swig to handle this, isn't there?
> Anyway, I am not developing anymore, so feel free to ignore what
> I have to say...
More information about the libkdtree-devel