Python bindings -noproxy flag

Hello,

why is the -noproxy flag passed to SWIG when building the python
bindings? This forces SWIG not to build shadow classes for structs.

I think that pointers and accessor functions are not something that
python programmers want to get involved with, not even when they are
using bindings to a C API. SWIG already has the feature of building
classes which can even be subclassed to add new functionality. Why
aren't we using that feature?

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 8 00:21:59 2003