On 5 January 2012 18:24, Tom de Vries wrote:
> On 05/01/12 18:40, Jonathan Wakely wrote:
>> On 5 January 2012 16:33, Marc Glisse wrote:
>>> On Thu, 5 Jan 2012, Joseph S. Myers wrote:
>>>
If the final C++11 still requires gets in , despite it being
removed in C11, that's probably also a bu
On 05/01/12 18:40, Jonathan Wakely wrote:
> On 5 January 2012 16:33, Marc Glisse wrote:
>> On Thu, 5 Jan 2012, Joseph S. Myers wrote:
>>
>>> If the final C++11 still requires gets in , despite it being
>>> removed in C11, that's probably also a bug in C++11. (At least the most
>>> recent draft I h
On 5 January 2012 16:33, Marc Glisse wrote:
> On Thu, 5 Jan 2012, Joseph S. Myers wrote:
>
>> If the final C++11 still requires gets in , despite it being
>> removed in C11, that's probably also a bug in C++11. (At least the most
>> recent draft I have to hand still has gets in .)
>
>
> It still h
On Thu, 5 Jan 2012, Marc Glisse wrote:
Do you have any suggestion on what libstdc++ can do when faced with C
libraries that will randomly declare gets or not depending on flags? It would
need knowledge of these exact flags so it can provide a replacement exactly
when it isn't declared (or at l
On Thu, 5 Jan 2012, Joseph S. Myers wrote:
On Thu, 5 Jan 2012, Tom de Vries wrote:
My hunch is that this recent glibc change causes/triggers the error:
...
[BZ #13528]
* libio/stdio.h: Do not declare gets for ISO C11 and _GNU_SOURCE.
...
I see this both on ARM and MIPS.
Shoul
On Thu, 5 Jan 2012, Tom de Vries wrote:
> My hunch is that this recent glibc change causes/triggers the error:
> ...
> [BZ #13528]
> * libio/stdio.h: Do not declare gets for ISO C11 and _GNU_SOURCE.
> ...
>
> I see this both on ARM and MIPS.
>
> Should I file this as a problem in gcc
/cstdio:118:11:
error: '::gets' has not been declared
...
My hunch is that this recent glibc change causes/triggers the error:
...
[BZ #13528]
* libio/stdio.h: Do not declare gets for ISO C11 and _GNU_SOURCE.
...
I see this both on ARM and MIPS.
Should I file this as a
