| | 1 | = GEOS RFC 6: Drop support for C++ API and stop shipping the header = |
| | 2 | |
| | 3 | This document proposes to drop the support of GEOS C++ API starting with GEOS 3.8 and to not ship the C++ Headers anymore |
| | 4 | |
| | 5 | ||RFC 6: ||C++11 Drop support for C++ API and stop shipping the header|| |
| | 6 | ||Author: ||Regina Obe || |
| | 7 | ||Contact:||lr@pcorp.us || |
| | 8 | ||Status: ||[https://lists.osgeo.org/pipermail/geos-devel/2017-October/thread.html#8050 In Discussion] || |
| | 9 | |
| | 10 | We should drop C++ API because we do not have the manpower to guarantee ABI compatiblity from version to version. |
| | 11 | Currently osm2pgsql (and before Osmium) were the only ones that use the GEOS C++ API. |
| | 12 | |
| | 13 | Sandro proposed perhaps just making it [https://lists.osgeo.org/pipermail/geos-devel/2017-October/008047.html more noisy]. It is my experience |
| | 14 | that most developers ignore noise. So if we can't support an API full-heartedly I'd just assume drop it. |
| | 15 | |
| | 16 | It causes all sorts of problems for users relying on the GEOS upstream and novice users will be burned when their code no longer works with newer GEOS. |
| | 17 | |
