http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49347
--- Comment #2 from Török Edwin <edwintorok at gmail dot com> 2011-06-09 18:29:22 UTC --- (In reply to comment #1) > (In reply to comment #0) > > > > Don't know where the #define to __restrict on __cplusplus comes from, but > > it is > > wrong. > > No, it's correct, see > http://gcc.gnu.org/onlinedocs/gcc/Restricted-Pointers.html > > > The bug is that G++ can't parse __restrict in an array parameter: > > extern int f( char *const envp[__restrict] ); > > The C front end accepts this, but not the C++ one. Is that planned to be fixed for the next release? If not then as a workaround that fix-includes header could #define _RESTRICY_KYWD to empty.
