Re: ENOATTR vs ENODATA

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

> There is a choice to be made about returing ENOATTR or ENODATA [...]

> In order to get the broader compatibility, I suggest patching our
> errno.h to define ENOATTR as ENODATA.  Opinions?

As a code author, I don't like this.

A similar situation already exists with EAGAIN and EWOULDBLOCK: some
systems define only one, some only the other, some both with different
values, and some both with the same value (often one in terms of the
other).

The last of these is rather annoying, because it means that a simple

#ifdef EAGAIN
        case EAGAIN:
#endif
#ifdef EWOULDBLOCK
        case EWOULDBLOCK:
#endif

produces a compile-time error.  So, my opinion would be to prefer one
of the other alternatives.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B