On Feb 3, 2016, at 2:03 PM, Jonathan Wakely wrote:
> Yes, there are *dozens* of packages that fail to build due to "return
> false;" in a function that returns a pointer of some kind.
Wow, curious. Anyway, that removes my objection.
On 03/02/16 19:47 +0100, Jakub Jelinek wrote:
On Wed, Feb 03, 2016 at 10:42:37AM -0800, Mike Stump wrote:
On Feb 3, 2016, at 9:13 AM, David Malcolm wrote:
>> +pointer constants, so other constants such as false and
>> +(1 - 1) cannot be used where a null pointer is desired.
So, I’d leave this
On Wed, Feb 03, 2016 at 10:42:37AM -0800, Mike Stump wrote:
> On Feb 3, 2016, at 9:13 AM, David Malcolm wrote:
> >> +pointer constants, so other constants such as false and
> >> +(1 - 1) cannot be used where a null pointer is desired.
>
> So, I’d leave this out entirely. The subject is porting,
On Feb 3, 2016, at 9:13 AM, David Malcolm wrote:
>> +pointer constants, so other constants such as false and
>> +(1 - 1) cannot be used where a null pointer is desired.
So, I’d leave this out entirely. The subject is porting, not the fine detail
pedanticism only a language lawyer could love. W
On 03/02/16 12:13 -0500, David Malcolm wrote:
On Tue, 2016-02-02 at 20:36 +, Jonathan Wakely wrote:
I had some difficulty reading the new section; mostly due to the
leapfrogging of C++11 by the default (my immediate reaction was "why is
it talking about C++11 when the option says GNU++14?")
On Tue, 2016-02-02 at 20:36 +, Jonathan Wakely wrote:
I had some difficulty reading the new section; mostly due to the
leapfrogging of C++11 by the default (my immediate reaction was "why is
it talking about C++11 when the option says GNU++14?")
I'm attaching a patch which I hope clarifies it
This documents the most likely problems for C++ programs using GCC 6.
Committed to CVS.
Index: htdocs/gcc-6/porting_to.html
===
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-6/porting_to.html,v
retrieving revision 1.2
diff -u -r1.2 porting_
