View Bug Activity | Format For Printing
we hit a neat little error with some code when including error.h and using -std=c99 ... the question is whether this is a feature :) take for example the attached code ... when built with -std=c99, __STRICT_ANSI__ is defined by gcc which causes error.h to macro away the gcc __attribute__ extension since gcc doesnt consider __attribute__ to ever be defined perhaps a better idea would be to use __error_attribute__ inside of the header so that it doesnt pollute the namespace of the code that includes it ... patch attached
Created an attachment (id=1078) glibc-error-header-updates.patch
__STRICT_ANSI__ is nonsense. If you want to write a strict ANSI C program stop using non-ANSI code from the system. That flag must go, fix the real reason instead of working around it.
if it's such nonsense, then why not just drop it from error.h ? if error.h is a non-ansi header then there's no point in checking for ansi in it
Stop reopening bugs. The file is used elsewhere and I don't make any unnecesary changes.