As I recall our process is we don't guarantee ABI or API portability of the C++ API we have (at least not on minor versions), micro we try to.
That said – if it's not exposed in the C-API, +1 for rip away lah dee dah. Less is more. From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of Paul Ramsey Sent: Wednesday, December 12, 2018 5:54 PM To: GEOS Development List <geos-devel@lists.osgeo.org> Subject: [geos-devel] Deprecation / Removal We're c++11, and the deprecated keyword is c++14. Just porting away, lah dee dah, and came across this one. https://github.com/locationtech/jts/commit/95f19c41741a5261c324f038f355549cab8be5a8 I'm tempted to just rip MCPointInRing right out of the code base, it's hardly used anywhere, and it's incredibly internal, so it's unlikely that anyone external is using it. And yet... Anyways, we don't have a policy per se, I would imagine, but maybe there's some historical process to draw upon? P
_______________________________________________ geos-devel mailing list geos-devel@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/geos-devel
