Re: Strange gcc warning...

[Joerg Sonnenberger <joerg%bec.de@localhost>]

On Sat, Aug 18, 2018 at 06:28:35PM +0700, Robert Elz wrote:
>     Date:        Sat, 18 Aug 2018 12:44:42 +0200
>     From:        Kamil Rytarowski <n54%gmx.com@localhost>
>     Message-ID:  <9a8d0076-72c3-8055-f386-5a3a389f1b4b%gmx.com@localhost>
> 
> 
>   | >        fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",  \
> 
>   | This is not a strange warning but an invalid C++ code.
> 
> If you had read my message you would have seen that that one was
> not the one to which the Subject was referring, the other report (that
> you ignored in this reply) was - this one I was just having a rant about,
> as (it seems to me anyway) that C is adopting more and more from C++
> (as strange as that is, given that C++ always was pretty disgusting)
> and that if this C++ issue turns into a C issue, it is going to be a real PITA.

Not true. It's just that GCC finally decided to ditch a lot of hackish
data structures and other junk and finally moved to C++. But they did it
in the worst possible way by forcing *.c files to be compiled as C++03.

Joerg