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: [PATCH] ENOATTR and EDOOFUS


Linux only knows ENODATA, and kFreeBSD only knows ENOATTR.  So I think it's no
big deal if we just define ENODATA as an alias for ENOATTR in our sysdeps.

EDOOFUS seems to be a funny way of telling the programmer that per did something
unsupported by the API.  There's a long discussion about this errno code pissing
off Apple Darwin developers which pretty much clarifies it:

  http://lists.freebsd.org/pipermail/freebsd-hackers/2003-May/000791.html

Looks like EGREGIOUS makes the fit:

  @comment errno.h
  @comment GNU: You really blew it this time
  @deftypevr Macro int EGREGIOUS
  @comment errno 103 @c DO NOT REMOVE
  You did @strong{what}?
  @end deftypevr

So I'll add it as an alias in our sysdeps, too.

Thanks for the tips!

-- 
Robert Millan


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