[pdal] Filter renaming and C# (stoopid swig parser)

[Michael P. Gerlek]

I've done both in the past, and my experience is that they're both wildly painful no matter what you do :-)

Plus I had this naïve hope that the swig work would help us for Python bindings too.

If I had it to do over again, maybe I'd do it different.... But actually the swig bindings really do work fine, except when you have to tweak the .i file and you've already forgotten everything you learned about SWIG from when you had to tweak it last time 6 months ago...

-mpg


> -----Original Message-----
> From: Mateusz Łoskot [mailto:mateusz at loskot.net]
> Sent: Monday, November 14, 2011 4:51 PM
> To: mpg at flaxen.com
> Cc: pdal at lists.osgeo.org
> Subject: Re: [pdal] Filter renaming and C# (stoopid swig parser)
> 
> On 15 November 2011 00:36, Michael P. Gerlek <mpg at flaxen.com> wrote:
> > The C# bindings are currently broken, due to some namespacing issues that are causing the swig c++ parser to wig out.
> 
> I'm just wondering, perhaps it would be easier and more native to
> Microsoft toolset
> world to bind to C# through C++/CLI. Couple references:
> 
> http://msdn.microsoft.com/en-us/magazine/cc163852.aspx
> http://blogs.msdn.com/b/jolson/archive/2007/11/22/managed-and-native-interop-c-or-c-cli.aspx
> 
> My gut feeling tells enabling a plain C++ library with .NET Common Type System
> is easier using C++/CLI .
> 
> Just my 5 cents.
> 
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> Charter Member of OSGeo, http://osgeo.org
> Member of ACCU, http://accu.org