4.3BSD-Reno/share/man/cat3/strerror.0

Compare this file to the similar file:
Show the results in this format:




PERROR(3)		      1990			PERROR(3)



NNAAMMEE
     perror, strerror, sys_errlist, sys_nerr - system error mes-
     sages

SSYYNNOOPPSSIISS
     ppeerrrroorr((ssttrriinngg))
     cchhaarr **ssttrriinngg;;

     cchhaarr **
     ssttrreerrrroorr((eerrrrnnuumm))
     iinntt eerrrrnnuumm;;

     eexxtteerrnn iinntt eerrrrnnoo,, ssyyss__nneerrrr;;
     eexxtteerrnn cchhaarr **ssyyss__eerrrrlliisstt[[]];;

DDEESSCCRRIIPPTTIIOONN
     _P_e_r_r_o_r produces a short error message on the standard error
     file describing the last error encountered during a call to
     the system from a C program.  If _s_t_r_i_n_g is non-NULL, it is
     printed, followed by a colon, followed by a space, followed
     by the message and a new-line.  Otherwise, just the message
     and the new-line are printed.  Most usefully, the argument
     string is the name of the program which incurred the error.
     The error number is taken from the external variable _e_r_r_n_o
     (see _i_n_t_r_o(2)), which is set when errors occur but not
     cleared when non-erroneous calls are made.

     To simplify variant formatting of messages, the _s_t_r_e_r_r_o_r
     function returns a pointer to the error message string
     mapped to the error number _e_r_r_n_u_m.

     The message strings can be accessed directly using the
     external character array _s_y_s__e_r_r_l_i_s_t.  _S_y_s__n_e_r_r is the total
     number of messages in the array.  The use of these variables
     is deprecated; _s_t_r_e_r_r_o_r should be used instead.

SSEEEE AALLSSOO
     intro(2)

















Printed 7/27/90               June				1