This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Marking of functions with attributes like __wur


> > So, is this a good go for a policy:
> >
> > "This is useful for functions where not checking the result is either a
> > security problem or always a bug such as realloc.
> >
> > This flag might not be set if the check for failure can be done in other
> > ways, e.g. the return value of fwrite can be check with ferror as well.
> > Only apply it where in practice, a warning is far more likely to be a
> > helpful diagnostic than a false alarm."
> 
> No replies since a few days. Have we reached consensus to go ahead with 
> the above definition until we find a better one? ;)

The second paragraph seems to contradict the first.  I think the final
clause ("a warning far more likely...") is the real criterion and the
rest is just elucidation.


Thanks,
Roland


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]