[geos-devel] updating geos 3.5.0 source archive.

Mateusz Loskot mateusz at loskot.net
Tue Nov 10 01:50:57 PST 2015

On 10 November 2015 at 01:42, Jürgen E. <jef at norbit.de> wrote:
> On Sun, 08. Nov 2015 at 22:01:53 +0100, Rashad M wrote:
>> > IIRC, ossim said it will stick to c++api as long as there is one. I know
>> GEOS recommends to use C-API but it also provides c++. So I don't see that
>> ossim is going to move away.
> Why not?  Other projects have to.  I'd prefer to keep the C++ API out
> of the picture.


If I may, one correction: other projects do NOT have to, but they choose to.
GEOS C++ API is an official API perfectly supported and
recommended to use by GEOS users.

There is, however, cost involved. That is, GEOS does not promise C++ API/ABI
stability, so those who choose GEOS C++ API should be aware they may need
to update change their code more frequently.

So, I don't think it's a good idea to forbid the freedom of GEOS API choice,
especially if it is a choice between officially supported APIs.

Best regards,
Mateusz  Loskot, http://mateusz.loskot.net

More information about the geos-devel mailing list