1 .\" Copyright (c) 1999 Andries Brouwer (aeb@cwi.nl)
3 .\" Earlier versions of this page influenced the present text.
4 .\" It was derived from a Berkeley page with version
5 .\" @(#)printf.3 6.14 (Berkeley) 7/30/91
6 .\" converted for Linux by faith@cs.unc.edu, updated by
7 .\" Helmut.Geyer@iwr.uni-heidelberg.de, agulbra@troll.no and Bruno Haible.
9 .\" %%%LICENSE_START(GPLv2+_DOC_FULL)
10 .\" This is free documentation; you can redistribute it and/or
11 .\" modify it under the terms of the GNU General Public License as
12 .\" published by the Free Software Foundation; either version 2 of
13 .\" the License, or (at your option) any later version.
15 .\" The GNU General Public License's references to "object code"
16 .\" and "executables" are to be interpreted as the output of any
17 .\" document formatting or typesetting system, including
18 .\" intermediate and printed output.
20 .\" This manual is distributed in the hope that it will be useful,
21 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
22 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
23 .\" GNU General Public License for more details.
25 .\" You should have received a copy of the GNU General Public
26 .\" License along with this manual; if not, see
27 .\" <http://www.gnu.org/licenses/>.
30 .\" 1999-11-25 aeb - Rewritten, using SUSv2 and C99.
31 .\" 2000-07-26 jsm28@hermes.cam.ac.uk - three small fixes
32 .\" 2000-10-16 jsm28@hermes.cam.ac.uk - more fixes
34 .TH PRINTF 3 2016-12-12 "GNU" "Linux Programmer's Manual"
36 printf, fprintf, dprintf, sprintf, snprintf, vprintf, vfprintf, vdprintf,
37 vsprintf, vsnprintf \- formatted output conversion
41 .BI "int printf(const char *" format ", ...);"
43 .BI "int fprintf(FILE *" stream ", const char *" format ", ...);"
45 .BI "int dprintf(int " fd ", const char *" format ", ...);"
47 .BI "int sprintf(char *" str ", const char *" format ", ...);"
49 .BI "int snprintf(char *" str ", size_t " size ", const char *" format ", ...);"
51 .B #include <stdarg.h>
53 .BI "int vprintf(const char *" format ", va_list " ap );
55 .BI "int vfprintf(FILE *" stream ", const char *" format ", va_list " ap );
57 .BI "int vdprintf(int " fd ", const char *" format ", va_list " ap );
59 .BI "int vsprintf(char *" str ", const char *" format ", va_list " ap );
61 .BI "int vsnprintf(char *" str ", size_t " size ", const char *" format \
65 Feature Test Macro Requirements for glibc (see
66 .BR feature_test_macros (7)):
73 _XOPEN_SOURCE\ >=\ 500 || _ISOC99_SOURCE ||
74 || /* Glibc versions <= 2.19: */ _BSD_SOURCE
83 _POSIX_C_SOURCE\ >=\ 200809L
93 family produce output according to a
102 the standard output stream;
106 write output to the given output
113 write to the character string
120 except that it outputs to a file descriptor,
132 bytes (including the terminating null byte (\(aq\e0\(aq)) to
141 are equivalent to the functions
147 respectively, except that they are called with a
149 instead of a variable number of arguments.
150 These functions do not call the
153 Because they invoke the
157 is undefined after the call.
161 All of these functions write the output under the control of a
163 string that specifies how subsequent arguments (or arguments accessed via
164 the variable-length argument facilities of
166 are converted for output.
168 C99 and POSIX.1-2001 specify that the results are undefined if a call to
174 would cause copying to take place between objects that overlap
175 (e.g., if the target string array and one of the supplied input arguments
176 refer to the same buffer).
178 .SS Format of the format string
179 The format string is a character string, beginning and ending
180 in its initial shift state, if any.
181 The format string is composed of zero or more directives: ordinary
184 which are copied unchanged to the output stream;
185 and conversion specifications, each of which results in fetching zero or
186 more subsequent arguments.
187 Each conversion specification is introduced by
191 .IR "conversion specifier" .
192 In between there may be (in this order) zero or more
199 .IR "length modifier" .
201 The arguments must correspond properly (after type promotion) with the
202 conversion specifier.
203 By default, the arguments are used in the order
204 given, where each \(aq*\(aq (see
208 below) and each conversion specifier asks for the next
209 argument (and it is an error if insufficiently many arguments are given).
210 One can also specify explicitly which argument is taken,
211 at each place where an argument is required, by writing "%m$" instead
212 of \(aq%\(aq and "*m$" instead of \(aq*\(aq,
213 where the decimal integer \fIm\fP denotes
214 the position in the argument list of the desired argument, indexed starting
220 printf("%*d", width, num);
228 printf("%2$*1$d", width, num);
233 The second style allows repeated references to the
235 The C99 standard does not include the style using \(aq$\(aq,
236 which comes from the Single UNIX Specification.
238 \(aq$\(aq is used, it must be used throughout for all conversions taking an
239 argument and all width and precision arguments, but it may be mixed
240 with "%%" formats, which do not consume an argument.
242 gaps in the numbers of arguments specified using \(aq$\(aq; for example, if
243 arguments 1 and 3 are specified, argument 2 must also be specified
244 somewhere in the format string.
246 For some numeric conversions a radix character ("decimal point") or
247 thousands' grouping character is used.
248 The actual character used
255 uses \(aq.\(aq as radix character, and does not have a grouping character.
260 printf("%\(aq.2f", 1234567.89);
264 results in "1234567.89" in the POSIX locale, in "1234567,89" in the
265 nl_NL locale, and in "1.234.567,89" in the da_DK locale.
267 The character % is followed by zero or more of the following flags:
270 The value should be converted to an "alternate form".
273 conversions, the first character of the output string is made zero
274 (by prefixing a 0 if it was not zero already).
279 conversions, a nonzero result has the string "0x" (or "0X" for
281 conversions) prepended to it.
292 conversions, the result will always contain a decimal point, even if no
293 digits follow it (normally, a decimal point appears in the results of those
294 conversions only if a digit follows).
299 conversions, trailing zeros are not removed from the result as they would
301 For other conversions, the result is undefined.
304 The value should be zero padded.
321 conversions, the converted value is padded on the left with zeros rather
327 flags both appear, the
330 If a precision is given with a numeric conversion
341 For other conversions, the behavior is undefined.
344 The converted value is to be left adjusted on the field boundary.
345 (The default is right justification.)
346 The converted value is padded on the right with blanks, rather
347 than on the left with blanks or zeros.
355 (a space) A blank should be left before a positive number
356 (or empty string) produced by a signed conversion.
359 A sign (+ or \-) should always be placed before a number produced by a signed
361 By default, a sign is used only for negative numbers.
364 overrides a space if both are used.
366 The five flag characters above are defined in the C99 standard.
367 The Single UNIX Specification specifies one further flag character.
370 For decimal conversion
378 the output is to be grouped with thousands' grouping characters
379 if the locale information indicates any.
382 Note that many versions of
384 cannot parse this option and will issue a warning.
386 include \fI%\(aqF\fP, but SUSv3 added it.)
388 glibc 2.2 adds one further flag character.
391 For decimal integer conversion
395 the output uses the locale's alternative output digits, if any.
396 For example, since glibc 2.2.3 this will give Arabic-Indic digits
397 in the Persian ("fa_IR") locale.
398 .\" outdigits keyword in locale file
400 An optional decimal digit string (with nonzero first digit) specifying
401 a minimum field width.
402 If the converted value has fewer characters
403 than the field width, it will be padded with spaces on the left
404 (or right, if the left-adjustment flag has been given).
405 Instead of a decimal digit string one may write "*" or "*m$"
406 (for some decimal integer \fIm\fP) to specify that the field width
407 is given in the next argument, or in the \fIm\fP-th argument, respectively,
408 which must be of type
410 A negative field width is taken as a \(aq\-\(aq flag followed by a
411 positive field width.
412 In no case does a nonexistent or small field width cause truncation of a
413 field; if the result of a conversion is wider than the field width, the
414 field is expanded to contain the conversion result.
416 An optional precision, in the form of a period (\(aq.\(aq) followed by an
417 optional decimal digit string.
418 Instead of a decimal digit string one may write "*" or "*m$"
419 (for some decimal integer \fIm\fP) to specify that the precision
420 is given in the next argument, or in the \fIm\fP-th argument, respectively,
421 which must be of type
423 If the precision is given as just \(aq.\(aq, the precision is taken to
425 A negative precision is taken as if the precision were omitted.
426 This gives the minimum number of digits to appear for
434 conversions, the number of digits to appear after the radix character for
442 conversions, the maximum number of significant digits for
446 conversions, or the maximum number of characters to be printed from a
453 Here, "integer conversion" stands for
464 A following integer conversion corresponds to a
468 argument, or a following
470 conversion corresponds to a pointer to a
475 A following integer conversion corresponds to a
478 .I unsigned short int
479 argument, or a following
481 conversion corresponds to a pointer to a
486 (ell) A following integer conversion corresponds to a
490 argument, or a following
492 conversion corresponds to a pointer to a
494 argument, or a following
496 conversion corresponds to a
498 argument, or a following
500 conversion corresponds to a pointer to
506 A following integer conversion corresponds to a
509 .I unsigned long long int
510 argument, or a following
512 conversion corresponds to a pointer to a
519 This is a nonstandard extension, derived from BSD;
520 avoid its use in new code.
533 conversion corresponds to a
536 (C99 allows %LF, but SUSv2 does not.)
539 A following integer conversion corresponds to an
543 argument, or a following
545 conversion corresponds to a pointer to an
550 A following integer conversion corresponds to a
554 argument, or a following
556 conversion corresponds to a pointer to a
561 A nonstandard synonym for
563 that predates the appearance of
565 Do not use in new code.
568 A following integer conversion corresponds to a
570 argument, or a following
572 conversion corresponds to a pointer to a
576 SUSv3 specifies all of the above,
577 except for those modifiers explicitly noted as being nonstandard extensions.
578 SUSv2 specified only the length modifiers
607 As a nonstandard extension, the GNU implementations treats
611 as synonyms, so that one can, for example, write
613 (as a synonym for the standards-compliant
617 (as a synonym for the standards compliant
619 Such usage is nonportable.
621 .SS Conversion specifiers
622 A character that specifies the type of conversion to be applied.
623 The conversion specifiers and their meanings are:
628 argument is converted to signed decimal notation.
629 The precision, if any, gives the minimum number of digits
630 that must appear; if the converted value requires fewer digits, it is
631 padded on the left with zeros.
632 The default precision is 1.
633 When 0 is printed with an explicit precision 0, the output is empty.
635 .BR o ", " u ", " x ", " X
638 argument is converted to unsigned octal
642 or unsigned hexadecimal
651 conversions; the letters
656 The precision, if any, gives the minimum number of digits
657 that must appear; if the converted value requires fewer digits, it is
658 padded on the left with zeros.
659 The default precision is 1.
660 When 0 is printed with an explicit precision 0, the output is empty.
665 argument is rounded and converted in the style
666 .RB [\-]d \&. ddd e \(+-dd
667 where there is one digit before the decimal-point character and the number
668 of digits after it is equal to the precision; if the precision is missing,
669 it is taken as 6; if the precision is zero, no decimal-point character
673 conversion uses the letter
677 to introduce the exponent.
678 The exponent always contains at least two
679 digits; if the value is zero, the exponent is 00.
684 argument is rounded and converted to decimal notation in the style
686 where the number of digits after the decimal-point character is equal to
687 the precision specification.
688 If the precision is missing, it is taken as
689 6; if the precision is explicitly zero, no decimal-point character appears.
690 If a decimal point appears, at least one digit appears before it.
692 (SUSv2 does not know about
694 and says that character string representations for infinity and NaN
695 may be made available.
696 SUSv3 adds a specification for
698 The C99 standard specifies "[\-]inf" or "[\-]infinity"
699 for infinity, and a string starting with "nan" for NaN, in the case of
701 conversion, and "[\-]INF" or "[\-]INFINITY" or "NAN" in the case of
708 argument is converted in style
719 The precision specifies the number of significant digits.
720 If the precision is missing, 6 digits are given; if the precision is zero,
724 is used if the exponent from its conversion is less than \-4 or greater
725 than or equal to the precision.
726 Trailing zeros are removed from the
727 fractional part of the result; a decimal point appears only if it is
728 followed by at least one digit.
731 (C99; not in SUSv2, but added in SUSv3)
736 argument is converted to hexadecimal notation (using the letters abcdef)
738 .RB [\-] 0x h \&. hhhh p \(+-;
741 conversion the prefix
743 the letters ABCDEF, and the exponent separator
746 There is one hexadecimal digit before the decimal point,
747 and the number of digits after it is equal to the precision.
748 The default precision suffices for an exact representation of the value
749 if an exact representation in base 2 exists
750 and otherwise is sufficiently large to distinguish values of type
752 The digit before the decimal point is unspecified for nonnormalized
753 numbers, and nonzero but otherwise unspecified for normalized numbers.
758 modifier is present, the
760 argument is converted to an
761 .IR "unsigned char" ,
762 and the resulting character is written.
765 modifier is present, the
767 (wide character) argument is converted to a multibyte sequence by a call
770 function, with a conversion state starting in the initial state, and the
771 resulting multibyte string is written.
776 modifier is present: the
778 argument is expected to be a pointer to an array of character type (pointer
780 Characters from the array are written up to (but not
781 including) a terminating null byte (\(aq\\0\(aq);
782 if a precision is specified, no more than the number specified
784 If a precision is given, no null byte need be present;
785 if the precision is not specified, or is greater than the size of the
786 array, the array must contain a terminating null byte.
790 modifier is present: the
791 .I "const wchar_t\ *"
792 argument is expected to be a pointer to an array of wide characters.
793 Wide characters from the array are converted to multibyte characters
794 (each by a call to the
796 function, with a conversion state starting in the initial state before
797 the first wide character), up to and including a terminating null
799 The resulting multibyte characters are written up to
800 (but not including) the terminating null byte.
802 specified, no more bytes than the number specified are written, but
803 no partial multibyte characters are written.
804 Note that the precision
805 determines the number of
807 written, not the number of
810 .IR "screen positions" .
811 The array must contain a terminating null wide character, unless a
812 precision is given and it is so small that the number of bytes written
813 exceeds it before the end of the array is reached.
816 (Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
822 (Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
830 pointer argument is printed in hexadecimal (as if by
836 The number of characters written so far is stored into the integer
837 pointed to by the corresponding argument.
838 That argument shall be an
840 or variant whose size matches the (optionally)
841 supplied integer length modifier.
842 No argument is converted.
843 (This specifier is not supported by the bionic C library.)
844 The behavior is undefined if the conversion specification includes
845 any flags, a field width, or a precision.
848 (Glibc extension; supported by uClibc and musl.)
850 .IR strerror(errno) .
851 No argument is required.
854 A \(aq%\(aq is written.
855 No argument is converted.
856 The complete conversion
857 specification is \(aq%%\(aq.
859 Upon successful return, these functions return the number of characters
860 printed (excluding the null byte used to end output to strings).
866 do not write more than
868 bytes (including the terminating null byte (\(aq\e0\(aq)).
869 If the output was truncated due to this limit, then the return value
870 is the number of characters (excluding the terminating null byte)
871 which would have been written to the final string if enough space
873 Thus, a return value of
875 or more means that the output was truncated.
876 (See also below under NOTES.)
878 If an output error is encountered, a negative value is returned.
880 For an explanation of the terms used in this section, see
886 Interface Attribute Value
899 T} Thread safety MT-Safe locale
909 POSIX.1-2001, POSIX.1-2008, C89, C99.
913 POSIX.1-2001, POSIX.1-2008, C99.
919 functions were originally GNU extensions that were later standardized
922 Concerning the return value of
924 SUSv2 and C99 contradict each other: when
928 then SUSv2 stipulates an unspecified return value less than 1,
931 to be NULL in this case, and gives the return value (as always)
932 as the number of characters that would have been written in case
933 the output string has been large enough.
934 POSIX.1-2001 and later align their specification of
938 .\" Linux libc4 knows about the five C standard flags.
939 .\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
940 .\" and the conversions
941 .\" \fBc\fP, \fBd\fP, \fBe\fP, \fBE\fP, \fBf\fP, \fBF\fP,
942 .\" \fBg\fP, \fBG\fP, \fBi\fP, \fBn\fP, \fBo\fP, \fBp\fP,
943 .\" \fBs\fP, \fBu\fP, \fBx\fP, and \fBX\fP,
944 .\" where \fBF\fP is a synonym for \fBf\fP.
945 .\" Additionally, it accepts \fBD\fP, \fBO\fP, and \fBU\fP as synonyms
946 .\" for \fBld\fP, \fBlo\fP, and \fBlu\fP.
947 .\" (This is bad, and caused serious bugs later, when
948 .\" support for \fB%D\fP disappeared.)
949 .\" No locale-dependent radix character,
950 .\" no thousands' separator, no NaN or infinity, no "%m$" and "*m$".
952 .\" Linux libc5 knows about the five C standard flags and the \(aq flag,
953 .\" locale, "%m$" and "*m$".
954 .\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
955 .\" \fBZ\fP, and \fBq\fP, but accepts \fBL\fP and \fBq\fP
956 .\" both for \fIlong double\fP and for \fIlong long int\fP (this is a bug).
957 .\" It no longer recognizes \fBF\fP, \fBD\fP, \fBO\fP, and \fBU\fP,
958 .\" but adds the conversion character
961 .\" .IR strerror(errno) .
963 .\" glibc 2.0 adds conversion characters \fBC\fP and \fBS\fP.
965 glibc 2.1 adds length modifiers \fBhh\fP, \fBj\fP, \fBt\fP, and \fBz\fP
966 and conversion characters \fBa\fP and \fBA\fP.
968 glibc 2.2 adds the conversion character \fBF\fP with C99 semantics,
969 and the flag character \fBI\fP.
971 Some programs imprudently rely on code such as the following
973 sprintf(buf, "%s some further text", buf);
977 However, the standards explicitly note that the results are undefined
978 if source and destination buffers overlap when calling
984 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=7075
985 Depending on the version of
987 used, and the compiler options employed, calls such as the above will
989 produce the expected results.
991 The glibc implementation of the functions
995 conforms to the C99 standard, that is, behaves as described above,
996 since glibc version 2.1.
997 Until glibc 2.0.6, they would return \-1
998 when the output was truncated.
1000 .\" UNIX V7 defines the three routines
1004 .\" and has the flag \-, the width or precision *, the length modifier l,
1005 .\" and the conversions doxfegcsu, and also D,O,U,X as synonyms for ld,lo,lu,lx.
1006 .\" This is still true for 2.9.1BSD, but 2.10BSD has the flags
1007 .\" #, + and <space> and no longer mentions D,O,U,X.
1010 .\" .BR vfprintf (),
1011 .\" .BR vsprintf (),
1012 .\" and warns not to use D,O,U,X.
1013 .\" 4.3BSD Reno has the flag 0, the length modifiers h and L,
1014 .\" and the conversions n, p, E, G, X (with current meaning)
1015 .\" and deprecates D,O,U.
1016 .\" 4.4BSD introduces the functions
1019 .\" .BR vsnprintf (),
1020 .\" and the length modifier q.
1021 .\" FreeBSD also has functions
1024 .\" .BR vasprintf (),
1025 .\" that allocate a buffer large enough for
1027 .\" In glibc there are functions
1031 .\" that print to a file descriptor instead of a stream.
1037 assume an arbitrarily long string, callers must be careful not to overflow
1038 the actual space; this is often impossible to assure.
1039 Note that the length
1040 of the strings produced is locale-dependent and difficult to predict.
1050 .\" Linux libc4.[45] does not have a
1051 .\" .BR snprintf (),
1052 .\" but provides a libbsd that contains an
1056 .\" that is, one that ignores the
1059 .\" Thus, the use of
1061 .\" with early libc4 leads to serious security problems.
1065 often indicates a bug, since
1067 may contain a % character.
1070 comes from untrusted user input, it may contain \fB%n\fP, causing the
1072 call to write to memory and creating a security hole.
1074 .\" Some floating-point conversions under early libc4
1075 .\" caused memory leaks.
1079 to five decimal places:
1085 fprintf(stdout, "pi = %.5f\en", 4 * atan(1.0));
1089 To print a date and time in the form "Sunday, July 3, 10:02",
1094 are pointers to strings:
1099 fprintf(stdout, "%s, %s %d, %.2d:%.2d\en",
1100 weekday, month, day, hour, min);
1104 Many countries use the day-month-year order.
1105 Hence, an internationalized version must be able to print
1106 the arguments in an order specified by the format:
1111 fprintf(stdout, format,
1112 weekday, month, day, hour, min);
1118 depends on locale, and may permute the arguments.
1123 "%1$s, %3$d. %2$s, %4$d:%5$.2d\en"
1127 one might obtain "Sonntag, 3. Juli, 10:02".
1129 To allocate a sufficiently large string and print into it
1130 (code correct for both glibc 2.0 and glibc 2.1):
1138 make_message(const char *fmt, ...)
1144 /* Determine required size */
1147 size = vsnprintf(p, size, fmt, ap);
1153 size++; /* For '\\0' */
1159 size = vsnprintf(p, size, fmt, ap);
1171 If truncation occurs in glibc versions prior to 2.0.6, this is treated as an
1172 error instead of being handled gracefully.