When I am dictator...

[venta]

...there will be a POSIX error code:

EGONEWRONG

For those cases where, like, I dunno, something just went wrong.

Comments

[thegreenman.livejournal.com]

Do we have an EUNKNOWN defined in our errno.h?

:)

[wechsler.livejournal.com]

I thought that was already a standard?

[venta.livejournal.com]

<checks>

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.

[pm215]

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 :-()

[onebyone.livejournal.com]

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.