[geos-devel] Using C instead of C++ api in library used by QGis plugin?

[Frank Warmerdam]

Folks,

When we talk about the c api being more stable it includes things like c
calls being safer between compiler version and implementations.  That is
abi compatibility rather than at the source level.

The above also applies to gdal.

Best regards,
 On Mar 10, 2013 12:01 PM, "Peter Körner" <osm-lists at mazdermind.de> wrote:

> Hi
>
> > Should I use GEOS C or C++ api in my library? I read that C
>
>> api is recommended because of it is more stable. But when I tried to
>> use it, I'm missing some functionality.
>>
>
> That's what they say. The question is: how stable is "stable" for you?
> I'm using the C++ API in my Code for about 1.5 years now and geos changed
> every now an then a class or method name, switched some parameters around
> or moved something into another namespace.
>
> None of these changes created more then half an hour of work on my side.
> If you plan is to deploy your code onto a customers appliance, you'd be
> better of using the C api, but for a hobby project or a small business
> application, the C++ has proven to be stable enough for me.
>
> Regards, Peter
>
> ______________________________**_________________
> geos-devel mailing list
> geos-devel at lists.osgeo.org
> http://lists.osgeo.org/**mailman/listinfo/geos-devel<http://lists.osgeo.org/mailman/listinfo/geos-devel>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geos-devel/attachments/20130310/2e800a74/attachment.html>