Changes between Version 8 and Version 9 of RFC5

Timestamp:

Mar 29, 2017, 2:17:35 PM (7 years ago)

Author:

mloskot

Comment:

Final clean up

RFC5

@@ -30 +30 @@
 A social factor: since C++ programmers no longer enjoy C++98, allowing C++11 mode may increase potential for new contributions.
 
-== Release ==
-
-First release of C++11-enabled GEOS could be 3.7.0 or, perhaps, 4.0.0.
-
 == Compilers Landscape ==
 
@@ -56 +52 @@
 This proposal only requests agreement for the C++11 compilation mode.
 
-This proposal does not suggest any detailed roadmap of big refactoring committed in one go.
+If accepted, currently available build configurations (Autotools, CMake, NMake) will be updated to switch the compilation mode to C++11.
+
+This proposal does not suggest any detailed roadmap of big refactoring of the GEOS C++ codebase.
 
 The GEOS codebase is around 150 KLOC and given the available man-power to LOCs ratio, such one-step refactoring would not be feasible.
@@ -70 +68 @@
 Once accepted, first step will be to update the build configurations to require C++11-compliant compiler.
 
-
 == Issues ==
 
@@ -77 +74 @@
 * C++11 destructors, by default, have now the new exception specification of `nothrow(true)`. Destructors of GEOS classes should be reviewed and any that are allowed/expected to throw exceptions must be marked with `nothrow(false)`. Otherwise, any user of the existing GEOS codebase would find the program terminating whenever GEOS destructor throws an exception. Such review would be beneficial anyway.
 
+== Release ==
+
+First release of C++11-enabled GEOS could be 3.7.0 or, perhaps, 4.0.0.
+
 == References ==