On Sat, 12 Jan 2019 16:45:46 +0100, Ingo Schwarze wrote: > I did not attempt to hunt down all offenders. > Would you regard that as a whorthwhile endeavour? > Note that would not only require considering bogus leftovers > in our code, but also considering what other systems might do. > > I just thought it made sense to remove misleading statements about > our own code, but not not without warning about related portability > issues while there.
I just thought that if we were going to mention this problem at all, then we should do so in strtod() as well. And since printf(3) and scanf(3) suffer from the same issue as wprintf(3) and wscanf(3) I see no reason to only include the warning in the wide versions. I'm not advocating that we try to hunt down all possible affected functions. Actually, I wish there was a single central place we could document this where people would see it, but I'm not sure there really is one. - todd
