I only want one meaningless error code. I've called a function, it failed, it didn't tell me why. Now I want to return failure, but I have to retun ESOMETHING, and none of them fit...
It's not defined by POSIX and Linux doesn't seem to have it. (I see that POSIX does define EOPNOTSUPP, though, which probably originates in some idiot not knowing about the existence of ENOTSUP. Since it's now enshrined in a standard as a distinct errno I don't suppose it will go away now :-()
That's just because of the rule that at least 50% of errnos must be specific to sockets and thus of no use to anyone else. Maybe they needed to make up the numbers.
AVE room culture is a little different. If I could have only one new ERRNO it would have to be:
ENOCLUE - The user has done something so mind-numbingly stupid that I don't care what the spec implies should happen, I'm going to return failure because they deserve it.
no subject
no subject
no subject
:)
no subject
no subject
We don't seem to have it, no. But then we aren't POSIX compliant either. Though I might investigate why we don't have EUNKNOWN, it sounds useful.
no subject
It's not defined by POSIX and Linux doesn't seem to have it. (I see that POSIX does define EOPNOTSUPP, though, which probably originates in some idiot not knowing about the existence of ENOTSUP. Since it's now enshrined in a standard as a distinct errno I don't suppose it will go away now :-()
no subject
That's just because of the rule that at least 50% of errnos must be specific to sockets and thus of no use to anyone else. Maybe they needed to make up the numbers.
no subject
A Fine Plan
Re: A Fine Plan
It gets used a lot in our room, usually followed by Dan suggesting we start lobbying for the inclusion of EGONRONAY.
Re: A Fine Plan
ENOCLUE - The user has done something so mind-numbingly stupid that I don't care what the spec implies should happen, I'm going to return failure because they deserve it.
And even spoiled the women's chats
http://www.livejournal.com/users/steer/78706.html