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

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



PUTC(3)                       1989			  PUTC(3)



NNAAMMEE
     putc, putchar, fputc, putw - put character or word on a
     stream

SSYYNNOOPPSSIISS
     ##iinncclluuddee <<ssttddiioo..hh>>

     iinntt ppuuttcc((cc,, ssttrreeaamm))
     cchhaarr cc;;
     FFIILLEE **ssttrreeaamm;;

     iinntt ppuuttcchhaarr((cc))

     iinntt ffppuuttcc((cc,, ssttrreeaamm))
     FFIILLEE **ssttrreeaamm;;

     iinntt ppuuttww((ww,, ssttrreeaamm))
     FFIILLEE **ssttrreeaamm;;

DDEESSCCRRIIPPTTIIOONN
     _P_u_t_c appends the character _c to the named output _s_t_r_e_a_m.  It
     returns the character written.

     _P_u_t_c_h_a_r(_c) is defined as _p_u_t_c(_c, ssttddoouutt).

     _F_p_u_t_c behaves like _p_u_t_c, but is a genuine function rather
     than a macro.

     _P_u_t_w appends word (that is, iinntt) _w to the output _s_t_r_e_a_m.  It
     returns the word written.	_P_u_t_w neither assumes nor causes
     special alignment in the file.

SSEEEE AALLSSOO
     fopen(3), fclose(3), getc(3), puts(3), printf(3), fread(3)

DDIIAAGGNNOOSSTTIICCSS
     These functions return the constant EEOOFF upon error.  Since
     this is a good integer, _f_e_r_r_o_r(3) should be used to detect
     _p_u_t_w errors.

BBUUGGSS
     Because it is implemented as a macro, _p_u_t_c treats a _s_t_r_e_a_m
     argument with side effects improperly.  In particular

     putc(c, *f++);

     doesn't work sensibly.

     Errors can occur long after the call to _p_u_t_c.






Printed 7/27/90               April				1