Changes between Version 6 and Version 7 of RFC6

Timestamp:

Oct 2, 2017, 5:55:24 PM (7 years ago)

Author:

robe

Comment:

--

RFC6

@@ -1 @@
-= GEOS RFC 6: Require explicit configure with  C++ API to use C++ API and ship c++ headers =
+= GEOS RFC 6: Require explicit configure to use the C++ API and ship c++ headers =
 
-||RFC 6:  ||Drop support for C++ API and stop shipping the header||
+||RFC 6:  ||Discourage use of C++ API requiring a configure switch to install the c++ headers||
 ||Author: ||Regina Obe        ||
 ||Contact:||lr@pcorp.us    ||
@@ -23 +23 @@
 I propose doing this in GEOS 3.7.0.
 
-The main purpose is to discourage the use of the C++ API because we do not have the manpower to guarantee ABI compatiblity from version to version and thus using  in an environment where
+The main purpose is to discourage the use of the C++ API because we do not have the manpower to guarantee ABI compatiblity from version to version and thus using it in an environment where
 the GEOS library is shared across many software is unsupported.
 
-Currently osm2pgsql (and before Osmium) are the only ones that use the GEOS C++ API and largely distributed in s shared linux environment. 
+Currently osm2pgsql (and before Osmium) are the only ones that use the GEOS C++ API and largely distributed in shared environment.