[geos-devel] GEOS C++ API deprecated? (was: PostGIS 2.5 what should be minimum requirements?)
mateusz at loskot.net
Sat Sep 30 12:26:42 PDT 2017
On 30 September 2017 at 20:47, Greg Troxel <gdt at lexort.com> wrote:
> Mateusz Loskot <mateusz at loskot.net> writes:
>>> There isn't agreement about whether it is a bug for packages to use the
>>> GEOS C++ API. If it really is a bug, GEOS is buggy for installing the
>> Please, can we stop this heresy?
>> I'm tired of explaining GEOS C++ API status.
> So do you agree with this, taken from the geos README (in 3.6.2):
> ### Using the C++ interface (discouraged)
> NB: The C++ interface should not be used directly; the GEOS project
> views it as a bug for another program to use the C++ interface or even
> to directly link against the C++ library.
> Or do you think something else?
No, I don't agree with this.
Moreover, this paragraph has no rights to be there or in any official
I'm very surprised Sandro allowed it in - I assume a merge in rush.
It sneaked in (unnoticed) via  as follow-up to this thread  on geos-devel
which had not received any response declaring C++ API as deprecated
or even no response that uses word 'deprecate'.
Sandro clearly stated, C++ API users are warned .
Five years later, I answered the same question :
"GEOS C++ API is not an internal API, but a public yet supported API
offered by GEOS."
and Sandro, as the project leader, had not arrived with any corrections.
Finally, even if GEOS C++ API was/is marked as deprecated, then I ask
where is the RFC, where is the PSC voting the motion,
where is the public announcement?
> It genuinely seems to me that there are multiple opinions out there.
It is not a matter of an opinion, but a fact.
Mateusz Loskot, http://mateusz.loskot.net
More information about the geos-devel