2 .\" # Copyright (c) 2014, Juniper Networks, Inc.
3 .\" # All rights reserved.
4 .\" # This SOFTWARE is licensed under the LICENSE provided in the
5 .\" # ../Copyright file. By downloading, installing, copying, or
6 .\" # using the SOFTWARE, you agree to be bound by the terms of that
8 .\" # Phil Shafer, July 2014
14 .Nm xo_message , xo_message_c , xo_message_hc , xo_message_hcv
15 .Nd emit messages in multiple output styles
21 .Fn xo_message "const char *fmt" "..."
23 .Fn xo_message_e "const char *fmt" "..."
25 .Fn xo_message_c "int code" "const char *fmt" "..."
27 .Fn xo_message_hc "xo_handle_t *xop" "int code, const char *fmt" "..."
29 .Fn xo_message_hcv "xo_handle_t *xop" "int code" "const char *fmt" "va_list vap"
32 generates text message which lack any sort of structure.
33 These functions should not be used under normal conditions, since
34 they completely defeat the value of using libxo. They are provided
35 for scenarios when the output's content is genuinely unknown and
37 It is used in converting programs where err/warn where not used,
38 and error messages went to
44 allows backwards compatibility with that output, but does not put
45 the error in a useful form.
49 function generates output strings using the printf-style format string
50 and arguments provided.
51 If the format string does not end in a newline,
53 will appear a colon, a space, and the error associated with the current
56 .Nm xo_message_c behaves similarly for the value passed in the
65 .Nm xo_message_hcv accepts a va_list parameter of arguments.
72 library first appeared in
77 .An Phil Shafer Aq Mt phil@freebsd.org .