On Sat, 2024-07-06 at 00:01 +0800, Xi Ruoyao wrote: > On Fri, 2024-07-05 at 17:53 +0200, Alejandro Colomar wrote: > > At least, I hope there's consensus that while current GCC doesn't warn > > about this, ideally it should, which means it should warn for valid uses > > of strtol(3), which means strtol(3) should be fixed, in all of ISO, > > POSIX, and glibc. > > It **shouldn't**. strtol will only violate restrict if it's wrongly > implemented, or something dumb is done like "strtol((const char*) &p, > &p, 0)". > > See my previous reply. Also even if we'll introduce an over-eager warning having many positives, there are still many possibilities besides changing the standard to satisfy such a warning. For example, g++ -Wdangling- reference has many false positives (IMO it's over-eager) so a no_dangling attribute has been added to allow suppressing it. -- Xi Ruoyao <xry111@xxxxxxxxxxx> School of Aerospace Science and Technology, Xidian University
