Lines Matching full:which

12 @c run ``tex com_err.texinfo'' which will load in texinfo.tex,
88 a library and associated utilities which allows a more uniform way for
138 deal with a number of libraries, each of which can use a different
145 needed to determine which table to look at.  Sometimes no text messages are
146 supplied at all, and the programmer must supply them at any point at which
166 error codes accidentally returned before making the table known, which is
173 Error codes themselves are 32 bit (signed) integers, of which the high
174 order 24 bits are an identifier of which error table the error code is
178 on systems which support wider values.
192 Any variable which is to contain an error code should be declared @t{long}.
194 requires that @t{long} variables be at least 32 bits; any system which does
244 (@samp{discuss_err.h}) which contains definitions of the numerical values
245 of the error codes defined in the error table, and a C source file which
247 included in the source of a module which wishes to reference the error
249 to a program which wishes to use the printed forms of the error codes.
254 Any source file which uses the routines supplied with or produced by the
256 contains declarations and definitions which may be needed on some systems.
273 routine, some combination of routines which form the core of the library
299 left to circumstances which render @code{com_err} (below) unusable.
319 which may be used by higher-level variadic functions (functions which
332 be used in daemons (to use a routine which calls @cite{syslog(3)}), or
333 in a window system application (which could pop up a dialogue box).
335 If a program is to be used in an environment in which simply printing
337 daemon program which runs without a terminal attached),
339 The following is an example of an error handler which uses @cite{syslog(3)}
392 any event, any invariant which the library assumes must be maintained.
401 Library routines which can fail should be set up to return an error
407 Routines which use the first style of interface can be used from
425 A caller which fails to check the return status is in error.  It is
426 possible to look for code which ignores error returns by using lint;
427 look for error messages of the form ``foobar returns value which is
428 sometimes ignored'' or ``foobar returns value which is always
437 library routine which makes a ``connect'' system call to make a network
442 Cleanup which is typically necessary may include, but not be limited
443 to, freeing allocated memory which will not be needed any more,
445 descriptors, or otherwise undoing anything which the procedure did up
446 to this point.  When there are a lot of things which can go wrong, it
447 is generally good to write one block of error-handling code which is
451 open, which eventually causes the process to run out of file
527 for getting us started with ``discuss,'' for which this package was