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 2021-03-22 "GNU" "Linux Programmer's Manual"
36 printf, fprintf, dprintf, sprintf, snprintf, vprintf, vfprintf, vdprintf,
37 vsprintf, vsnprintf \- formatted output conversion
42 .BI "int printf(const char *restrict " format ", ...);"
43 .BI "int fprintf(FILE *restrict " stream ,
44 .BI " const char *restrict " format ", ...);"
45 .BI "int dprintf(int " fd ,
46 .BI " const char *restrict " format ", ...);"
47 .BI "int sprintf(char *restrict " str ,
48 .BI " const char *restrict " format ", ...);"
49 .BI "int snprintf(char *restrict " str ", size_t " size ,
50 .BI " const char *restrict " format ", ...);"
52 .B #include <stdarg.h>
54 .BI "int vprintf(const char *restrict " format ", va_list " ap );
55 .BI "int vfprintf(FILE *restrict " stream ,
56 .BI " const char *restrict " format ", va_list " ap );
57 .BI "int vdprintf(int " fd ,
58 .BI " const char *restrict " format ", va_list " ap );
59 .BI "int vsprintf(char *restrict " str ,
60 .BI " const char *restrict " format ", va_list " ap );
61 .BI "int vsnprintf(char *restrict " str ", size_t " size ,
62 .BI " const char *restrict " format ", va_list " ap );
66 Feature Test Macro Requirements for glibc (see
67 .BR feature_test_macros (7)):
73 _XOPEN_SOURCE >= 500 || _ISOC99_SOURCE
74 || /* Glibc <= 2.19: */ _BSD_SOURCE
81 _POSIX_C_SOURCE >= 200809L
88 family produce output according to a
97 the standard output stream;
101 write output to the given output
108 write to the character string
115 except that it outputs to a file descriptor,
127 bytes (including the terminating null byte (\(aq\e0\(aq)) to
136 are equivalent to the functions
142 respectively, except that they are called with a
144 instead of a variable number of arguments.
145 These functions do not call the
148 Because they invoke the
152 is undefined after the call.
156 All of these functions write the output under the control of a
158 string that specifies how subsequent arguments (or arguments accessed via
159 the variable-length argument facilities of
161 are converted for output.
163 C99 and POSIX.1-2001 specify that the results are undefined if a call to
169 would cause copying to take place between objects that overlap
170 (e.g., if the target string array and one of the supplied input arguments
171 refer to the same buffer).
173 .SS Format of the format string
174 The format string is a character string, beginning and ending
175 in its initial shift state, if any.
176 The format string is composed of zero or more directives: ordinary
179 which are copied unchanged to the output stream;
180 and conversion specifications, each of which results in fetching zero or
181 more subsequent arguments.
182 Each conversion specification is introduced by
186 .IR "conversion specifier" .
187 In between there may be (in this order) zero or more
194 .IR "length modifier" .
196 The overall syntax of a conversion specification is:
200 %[$][flags][width][.precision][length modifier]conversion
204 The arguments must correspond properly (after type promotion) with the
205 conversion specifier.
206 By default, the arguments are used in the order
207 given, where each \(aq*\(aq (see
211 below) and each conversion specifier asks for the next
212 argument (and it is an error if insufficiently many arguments are given).
213 One can also specify explicitly which argument is taken,
214 at each place where an argument is required, by writing "%m$" instead
215 of \(aq%\(aq and "*m$" instead of \(aq*\(aq,
216 where the decimal integer \fIm\fP denotes
217 the position in the argument list of the desired argument, indexed starting
223 printf("%*d", width, num);
231 printf("%2$*1$d", width, num);
236 The second style allows repeated references to the
238 The C99 standard does not include the style using \(aq$\(aq,
239 which comes from the Single UNIX Specification.
241 \(aq$\(aq is used, it must be used throughout for all conversions taking an
242 argument and all width and precision arguments, but it may be mixed
243 with "%%" formats, which do not consume an argument.
245 gaps in the numbers of arguments specified using \(aq$\(aq; for example, if
246 arguments 1 and 3 are specified, argument 2 must also be specified
247 somewhere in the format string.
249 For some numeric conversions a radix character ("decimal point") or
250 thousands' grouping character is used.
251 The actual character used
258 uses \(aq.\(aq as radix character, and does not have a grouping character.
263 printf("%\(aq.2f", 1234567.89);
267 results in "1234567.89" in the POSIX locale, in "1234567,89" in the
268 nl_NL locale, and in "1.234.567,89" in the da_DK locale.
270 The character % is followed by zero or more of the following flags:
273 The value should be converted to an "alternate form".
276 conversions, the first character of the output string is made zero
277 (by prefixing a 0 if it was not zero already).
282 conversions, a nonzero result has the string "0x" (or "0X" for
284 conversions) prepended to it.
295 conversions, the result will always contain a decimal point, even if no
296 digits follow it (normally, a decimal point appears in the results of those
297 conversions only if a digit follows).
302 conversions, trailing zeros are not removed from the result as they would
304 For other conversions, the result is undefined.
307 The value should be zero padded.
324 conversions, the converted value is padded on the left with zeros rather
330 flags both appear, the
333 If a precision is given with a numeric conversion
344 For other conversions, the behavior is undefined.
347 The converted value is to be left adjusted on the field boundary.
348 (The default is right justification.)
349 The converted value is padded on the right with blanks, rather
350 than on the left with blanks or zeros.
358 (a space) A blank should be left before a positive number
359 (or empty string) produced by a signed conversion.
362 A sign (+ or \-) should always be placed before a number produced by a signed
364 By default, a sign is used only for negative numbers.
367 overrides a space if both are used.
369 The five flag characters above are defined in the C99 standard.
370 The Single UNIX Specification specifies one further flag character.
373 For decimal conversion
381 the output is to be grouped with thousands' grouping characters
382 if the locale information indicates any.
385 Note that many versions of
387 cannot parse this option and will issue a warning.
389 include \fI%\(aqF\fP, but SUSv3 added it.)
391 glibc 2.2 adds one further flag character.
394 For decimal integer conversion
398 the output uses the locale's alternative output digits, if any.
399 For example, since glibc 2.2.3 this will give Arabic-Indic digits
400 in the Persian ("fa_IR") locale.
401 .\" outdigits keyword in locale file
403 An optional decimal digit string (with nonzero first digit) specifying
404 a minimum field width.
405 If the converted value has fewer characters
406 than the field width, it will be padded with spaces on the left
407 (or right, if the left-adjustment flag has been given).
408 Instead of a decimal digit string one may write "*" or "*m$"
409 (for some decimal integer \fIm\fP) to specify that the field width
410 is given in the next argument, or in the \fIm\fP-th argument, respectively,
411 which must be of type
413 A negative field width is taken as a \(aq\-\(aq flag followed by a
414 positive field width.
415 In no case does a nonexistent or small field width cause truncation of a
416 field; if the result of a conversion is wider than the field width, the
417 field is expanded to contain the conversion result.
419 An optional precision, in the form of a period (\(aq.\(aq) followed by an
420 optional decimal digit string.
421 Instead of a decimal digit string one may write "*" or "*m$"
422 (for some decimal integer \fIm\fP) to specify that the precision
423 is given in the next argument, or in the \fIm\fP-th argument, respectively,
424 which must be of type
426 If the precision is given as just \(aq.\(aq, the precision is taken to
428 A negative precision is taken as if the precision were omitted.
429 This gives the minimum number of digits to appear for
437 conversions, the number of digits to appear after the radix character for
445 conversions, the maximum number of significant digits for
449 conversions, or the maximum number of characters to be printed from a
456 Here, "integer conversion" stands for
467 A following integer conversion corresponds to a
471 argument, or a following
473 conversion corresponds to a pointer to a
478 A following integer conversion corresponds to a
482 argument, or a following
484 conversion corresponds to a pointer to a
489 (ell) A following integer conversion corresponds to a
493 argument, or a following
495 conversion corresponds to a pointer to a
497 argument, or a following
499 conversion corresponds to a
501 argument, or a following
503 conversion corresponds to a pointer to
509 A following integer conversion corresponds to a
512 .I unsigned long long
513 argument, or a following
515 conversion corresponds to a pointer to a
522 This is a nonstandard extension, derived from BSD;
523 avoid its use in new code.
536 conversion corresponds to a
539 (C99 allows %LF, but SUSv2 does not.)
542 A following integer conversion corresponds to an
546 argument, or a following
548 conversion corresponds to a pointer to an
553 A following integer conversion corresponds to a
557 argument, or a following
559 conversion corresponds to a pointer to a
564 A nonstandard synonym for
566 that predates the appearance of
568 Do not use in new code.
571 A following integer conversion corresponds to a
573 argument, or a following
575 conversion corresponds to a pointer to a
579 SUSv3 specifies all of the above,
580 except for those modifiers explicitly noted as being nonstandard extensions.
581 SUSv2 specified only the length modifiers
610 As a nonstandard extension, the GNU implementations treats
614 as synonyms, so that one can, for example, write
616 (as a synonym for the standards-compliant
620 (as a synonym for the standards compliant
622 Such usage is nonportable.
624 .SS Conversion specifiers
625 A character that specifies the type of conversion to be applied.
626 The conversion specifiers and their meanings are:
631 argument is converted to signed decimal notation.
632 The precision, if any, gives the minimum number of digits
633 that must appear; if the converted value requires fewer digits, it is
634 padded on the left with zeros.
635 The default precision is 1.
636 When 0 is printed with an explicit precision 0, the output is empty.
638 .BR o ", " u ", " x ", " X
641 argument is converted to unsigned octal
645 or unsigned hexadecimal
654 conversions; the letters
659 The precision, if any, gives the minimum number of digits
660 that must appear; if the converted value requires fewer digits, it is
661 padded on the left with zeros.
662 The default precision is 1.
663 When 0 is printed with an explicit precision 0, the output is empty.
668 argument is rounded and converted in the style
669 .RB [\-]d \&. ddd e \(+-dd
670 where there is one digit (which is nonzero if the argument is nonzero)
671 before the decimal-point character and the number
672 of digits after it is equal to the precision; if the precision is missing,
673 it is taken as 6; if the precision is zero, no decimal-point character
677 conversion uses the letter
681 to introduce the exponent.
682 The exponent always contains at least two
683 digits; if the value is zero, the exponent is 00.
688 argument is rounded and converted to decimal notation in the style
690 where the number of digits after the decimal-point character is equal to
691 the precision specification.
692 If the precision is missing, it is taken as
693 6; if the precision is explicitly zero, no decimal-point character appears.
694 If a decimal point appears, at least one digit appears before it.
696 (SUSv2 does not know about
698 and says that character string representations for infinity and NaN
699 may be made available.
700 SUSv3 adds a specification for
702 The C99 standard specifies "[\-]inf" or "[\-]infinity"
703 for infinity, and a string starting with "nan" for NaN, in the case of
705 conversion, and "[\-]INF" or "[\-]INFINITY" or "NAN" in the case of
712 argument is converted in style
723 The precision specifies the number of significant digits.
724 If the precision is missing, 6 digits are given; if the precision is zero,
728 is used if the exponent from its conversion is less than \-4 or greater
729 than or equal to the precision.
730 Trailing zeros are removed from the
731 fractional part of the result; a decimal point appears only if it is
732 followed by at least one digit.
735 (C99; not in SUSv2, but added in SUSv3)
740 argument is converted to hexadecimal notation (using the letters abcdef)
742 .RB [\-] 0x h \&. hhhh p \(+-d;
745 conversion the prefix
747 the letters ABCDEF, and the exponent separator
750 There is one hexadecimal digit before the decimal point,
751 and the number of digits after it is equal to the precision.
752 The default precision suffices for an exact representation of the value
753 if an exact representation in base 2 exists
754 and otherwise is sufficiently large to distinguish values of type
756 The digit before the decimal point is unspecified for nonnormalized
757 numbers, and nonzero but otherwise unspecified for normalized numbers.
758 The exponent always contains at least one
759 digit; if the value is zero, the exponent is 0.
764 modifier is present, the
766 argument is converted to an
767 .IR "unsigned char" ,
768 and the resulting character is written.
771 modifier is present, the
773 (wide character) argument is converted to a multibyte sequence by a call
776 function, with a conversion state starting in the initial state, and the
777 resulting multibyte string is written.
782 modifier is present: the
784 argument is expected to be a pointer to an array of character type (pointer
786 Characters from the array are written up to (but not
787 including) a terminating null byte (\(aq\e0\(aq);
788 if a precision is specified, no more than the number specified
790 If a precision is given, no null byte need be present;
791 if the precision is not specified, or is greater than the size of the
792 array, the array must contain a terminating null byte.
796 modifier is present: the
797 .I "const wchar_t\ *"
798 argument is expected to be a pointer to an array of wide characters.
799 Wide characters from the array are converted to multibyte characters
800 (each by a call to the
802 function, with a conversion state starting in the initial state before
803 the first wide character), up to and including a terminating null
805 The resulting multibyte characters are written up to
806 (but not including) the terminating null byte.
808 specified, no more bytes than the number specified are written, but
809 no partial multibyte characters are written.
810 Note that the precision
811 determines the number of
813 written, not the number of
816 .IR "screen positions" .
817 The array must contain a terminating null wide character, unless a
818 precision is given and it is so small that the number of bytes written
819 exceeds it before the end of the array is reached.
822 (Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
828 (Not in C99 or C11, but in SUSv2, SUSv3, and SUSv4.)
836 pointer argument is printed in hexadecimal (as if by
842 The number of characters written so far is stored into the integer
843 pointed to by the corresponding argument.
844 That argument shall be an
846 or variant whose size matches the (optionally)
847 supplied integer length modifier.
848 No argument is converted.
849 (This specifier is not supported by the bionic C library.)
850 The behavior is undefined if the conversion specification includes
851 any flags, a field width, or a precision.
854 (Glibc extension; supported by uClibc and musl.)
856 .IR strerror(errno) .
857 No argument is required.
860 A \(aq%\(aq is written.
861 No argument is converted.
862 The complete conversion
863 specification is \(aq%%\(aq.
865 Upon successful return, these functions return the number of characters
866 printed (excluding the null byte used to end output to strings).
872 do not write more than
874 bytes (including the terminating null byte (\(aq\e0\(aq)).
875 If the output was truncated due to this limit, then the return value
876 is the number of characters (excluding the terminating null byte)
877 which would have been written to the final string if enough space
879 Thus, a return value of
881 or more means that the output was truncated.
882 (See also below under NOTES.)
884 If an output error is encountered, a negative value is returned.
886 For an explanation of the terms used in this section, see
894 Interface Attribute Value
904 T} Thread safety MT-Safe locale
916 POSIX.1-2001, POSIX.1-2008, C89, C99.
920 POSIX.1-2001, POSIX.1-2008, C99.
926 functions were originally GNU extensions that were later standardized
929 Concerning the return value of
931 SUSv2 and C99 contradict each other: when
935 then SUSv2 stipulates an unspecified return value less than 1,
938 to be NULL in this case, and gives the return value (as always)
939 as the number of characters that would have been written in case
940 the output string has been large enough.
941 POSIX.1-2001 and later align their specification of
945 .\" Linux libc4 knows about the five C standard flags.
946 .\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
947 .\" and the conversions
948 .\" \fBc\fP, \fBd\fP, \fBe\fP, \fBE\fP, \fBf\fP, \fBF\fP,
949 .\" \fBg\fP, \fBG\fP, \fBi\fP, \fBn\fP, \fBo\fP, \fBp\fP,
950 .\" \fBs\fP, \fBu\fP, \fBx\fP, and \fBX\fP,
951 .\" where \fBF\fP is a synonym for \fBf\fP.
952 .\" Additionally, it accepts \fBD\fP, \fBO\fP, and \fBU\fP as synonyms
953 .\" for \fBld\fP, \fBlo\fP, and \fBlu\fP.
954 .\" (This is bad, and caused serious bugs later, when
955 .\" support for \fB%D\fP disappeared.)
956 .\" No locale-dependent radix character,
957 .\" no thousands' separator, no NaN or infinity, no "%m$" and "*m$".
959 .\" Linux libc5 knows about the five C standard flags and the \(aq flag,
960 .\" locale, "%m$" and "*m$".
961 .\" It knows about the length modifiers \fBh\fP, \fBl\fP, \fBL\fP,
962 .\" \fBZ\fP, and \fBq\fP, but accepts \fBL\fP and \fBq\fP
963 .\" both for \fIlong double\fP and for \fIlong long\fP (this is a bug).
964 .\" It no longer recognizes \fBF\fP, \fBD\fP, \fBO\fP, and \fBU\fP,
965 .\" but adds the conversion character
968 .\" .IR strerror(errno) .
970 .\" glibc 2.0 adds conversion characters \fBC\fP and \fBS\fP.
972 glibc 2.1 adds length modifiers \fBhh\fP, \fBj\fP, \fBt\fP, and \fBz\fP
973 and conversion characters \fBa\fP and \fBA\fP.
975 glibc 2.2 adds the conversion character \fBF\fP with C99 semantics,
976 and the flag character \fBI\fP.
978 Some programs imprudently rely on code such as the following
980 sprintf(buf, "%s some further text", buf);
984 However, the standards explicitly note that the results are undefined
985 if source and destination buffers overlap when calling
991 .\" http://sourceware.org/bugzilla/show_bug.cgi?id=7075
992 Depending on the version of
994 used, and the compiler options employed, calls such as the above will
996 produce the expected results.
998 The glibc implementation of the functions
1002 conforms to the C99 standard, that is, behaves as described above,
1003 since glibc version 2.1.
1004 Until glibc 2.0.6, they would return \-1
1005 when the output was truncated.
1007 .\" UNIX V7 defines the three routines
1011 .\" and has the flag \-, the width or precision *, the length modifier l,
1012 .\" and the conversions doxfegcsu, and also D,O,U,X as synonyms for ld,lo,lu,lx.
1013 .\" This is still true for 2.9.1BSD, but 2.10BSD has the flags
1014 .\" #, + and <space> and no longer mentions D,O,U,X.
1017 .\" .BR vfprintf (),
1018 .\" .BR vsprintf (),
1019 .\" and warns not to use D,O,U,X.
1020 .\" 4.3BSD Reno has the flag 0, the length modifiers h and L,
1021 .\" and the conversions n, p, E, G, X (with current meaning)
1022 .\" and deprecates D,O,U.
1023 .\" 4.4BSD introduces the functions
1026 .\" .BR vsnprintf (),
1027 .\" and the length modifier q.
1028 .\" FreeBSD also has functions
1031 .\" .BR vasprintf (),
1032 .\" that allocate a buffer large enough for
1034 .\" In glibc there are functions
1038 .\" that print to a file descriptor instead of a stream.
1044 assume an arbitrarily long string, callers must be careful not to overflow
1045 the actual space; this is often impossible to assure.
1046 Note that the length
1047 of the strings produced is locale-dependent and difficult to predict.
1057 .\" Linux libc4.[45] does not have a
1058 .\" .BR snprintf (),
1059 .\" but provides a libbsd that contains an
1063 .\" that is, one that ignores the
1066 .\" Thus, the use of
1068 .\" with early libc4 leads to serious security problems.
1072 often indicates a bug, since
1074 may contain a % character.
1077 comes from untrusted user input, it may contain \fB%n\fP, causing the
1079 call to write to memory and creating a security hole.
1081 .\" Some floating-point conversions under early libc4
1082 .\" caused memory leaks.
1086 to five decimal places:
1092 fprintf(stdout, "pi = %.5f\en", 4 * atan(1.0));
1096 To print a date and time in the form "Sunday, July 3, 10:02",
1101 are pointers to strings:
1106 fprintf(stdout, "%s, %s %d, %.2d:%.2d\en",
1107 weekday, month, day, hour, min);
1111 Many countries use the day-month-year order.
1112 Hence, an internationalized version must be able to print
1113 the arguments in an order specified by the format:
1118 fprintf(stdout, format,
1119 weekday, month, day, hour, min);
1125 depends on locale, and may permute the arguments.
1130 "%1$s, %3$d. %2$s, %4$d:%5$.2d\en"
1134 one might obtain "Sonntag, 3. Juli, 10:02".
1136 To allocate a sufficiently large string and print into it
1137 (code correct for both glibc 2.0 and glibc 2.1):
1145 make_message(const char *fmt, ...)
1152 /* Determine required size. */
1155 n = vsnprintf(p, size, fmt, ap);
1161 size = (size_t) n + 1; /* One extra byte for \(aq\e0\(aq */
1167 n = vsnprintf(p, size, fmt, ap);
1179 If truncation occurs in glibc versions prior to 2.0.6, this is treated as an
1180 error instead of being handled gracefully.