Re: #41: implement ATF_REQUIRE_ERRNO

["atf trac notification" <nobody%julipedia.org@localhost>]

#41: implement ATF_REQUIRE_ERRNO
---------------------------+------------------------------------------------
  Reporter:  pooka@...     |       Owner:  jmmv    
      Type:  enhancement   |      Status:  reopened
  Priority:  minor         |   Milestone:          
 Component:  MISC          |     Version:          
Resolution:                |    Keywords:          
---------------------------+------------------------------------------------

Comment (by Garrett Cooper <gcooper@...>):

 There's a problem with this request; not all functions fail in the same
 way ... in particular compare the pthread family of functions (which
 return errno) vs many native syscalls. Furthermore, compare some fcntl-
 like syscalls vs other syscalls.

 One size fits all solutions may not be a wise idea in this case, so I
 think that the problem statement needs to be better defined, because the
 above request is too loose.

 FWIW, there's also a TEST macro in LTP, which tests for non-zero status,
 and sets an appropriate set of global variables for errnos and return
 codes, respectively. It was a good idea, but has been mostly abandoned
 because it's too difficult to define a success and failure in a universal
 manner, so I think that we need to be careful with what's implemented in
 ATF to not repeat the mistakes that others have made.

-- 
Ticket URL: <http://www.julipedia.org/projects/atf/trac/ticket/41#comment:3>
Automated Testing Framework <http://www.NetBSD.org/~jmmv/atf/>
Automated Testing Framework