On 01/06/2014 01:00 PM, Daniel J Walsh wrote: > How is returning a ERRNO/ERROR for bad values hiding bugs from callers? We > are actually telling the callers what is bad. Not really. Stack trace is more informative than EINVAL, as the one will show you exactly where you failed and what the arguments were, whereas EINVAL could be a result of any of the arguments or a side effect elsewhere in the function. And the original functions that prompted this discussion have never allowed you to pass NULL as contexts. Would you add a NULL check inside of every string.h function in libc? _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
