On 04/07/2017 03:25 AM, Jonathan Wakely wrote:
This issue caused a lot of build failures during the GCC mass rebuilds
for Fedora, but isn't in the porting to guide yet.
Is this accurate and clear enough for casual readers?
Index: htdocs/gcc-7/porting_to.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-7/porting_to.html,v
retrieving revision 1.13
diff -u -r1.13 porting_to.html
--- htdocs/gcc-7/porting_to.html 6 Apr 2017 17:12:16 -0000 1.13
+++ htdocs/gcc-7/porting_to.html 7 Apr 2017 09:25:06 -0000
@@ -118,6 +118,39 @@
with GCC 7 and some are compiled with older releases.
</p>
+<h3 id="null-pointer-constants">Null pointer constants</h3>
+
+<p>
+When compiling as C++11 or later, GCC 7 follows the revised definition of a
+<em>null pointer constant</em>. This means conversions to pointers from other
+types of constant (such as character literals and boolean literals) will now
+be rejected.
+</p>
Nit pick: s/will now be rejected/are now rejected/
since "now" means we are describing GCC's current behavior, not future
behavior. :-)
-Sandra
