FazBrowse GitHub Viewer
|
Trending
|
URL:
|
Home
Tools:
[Download Repo ZIP]
[View Raw Code]
[Original HTTPS Page]
cpython/Python/mysnprintf.c at 3.13 · python/cpython · GitHub
Uh oh!
There was an error while loading.
Please reload this page
.
python
/
cpython
Public
Uh oh!
There was an error while loading.
Please reload this page
.
Notifications
You must be signed in to change notification settings
Fork
35.3k
Star
74.9k
Code
Issues
5k+
Pull requests
2.5k
Actions
Projects
Security and quality
0
Insights
Additional navigation options
Code
Issues
Pull requests
Actions
Projects
Security and quality
Insights
Expand file tree
Breadcrumbs
cpython
/
Python
/
mysnprintf.c
Copy path
More file actions
More file actions
Latest commit
History
History
History
80 lines (65 loc) · 2.49 KB
Breadcrumbs
cpython
/
Python
/
mysnprintf.c
Copy path
File metadata and controls
80 lines (65 loc) · 2.49 KB
Raw
Copy raw file
Download raw file
Open symbols panel
Edit and raw actions
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
#include
"Python.h"
/* snprintf() and vsnprintf() wrappers.
If the platform has vsnprintf, we use it, else we
emulate it in a half-hearted way. Even if the platform has it, we wrap
it because platforms differ in what vsnprintf does in case the buffer
is too small: C99 behavior is to return the number of characters that
would have been written had the buffer not been too small, and to set
the last byte of the buffer to \0. At least MS _vsnprintf returns a
negative value instead, and fills the entire buffer with non-\0 data.
Unlike C99, our wrappers do not support passing a null buffer.
The wrappers ensure that str[size-1] is always \0 upon return.
PyOS_snprintf and PyOS_vsnprintf never write more than size bytes
(including the trailing '\0') into str.
Return value (rv):
When 0 <= rv < size, the output conversion was unexceptional, and
rv characters were written to str (excluding a trailing \0 byte at
str[rv]).
When rv >= size, output conversion was truncated, and a buffer of
size rv+1 would have been needed to avoid truncation. str[size-1]
is \0 in this case.
When rv < 0, "something bad happened". str[size-1] is \0 in this
case too, but the rest of str is unreliable. It could be that
an error in format codes was detected by libc, or on platforms
with a non-C99 vsnprintf simply that the buffer wasn't big enough
to avoid truncation, or on platforms without any vsnprintf that
PyMem_Malloc couldn't obtain space for a temp buffer.
CAUTION: Unlike C99, str != NULL and size > 0 are required.
Also, size must be smaller than INT_MAX.
*/
int
PyOS_snprintf
(
char
*
str
,
size_t
size
,
const
char
*
format
, ...)
{
int
rc
;
va_list
va
;
va_start
(
va
,
format
);
rc
=
PyOS_vsnprintf
(
str
,
size
,
format
,
va
);
va_end
(
va
);
return
rc
;
}
int
PyOS_vsnprintf
(
char
*
str
,
size_t
size
,
const
char
*
format
,
va_list
va
)
{
assert
(
str
!=
NULL
);
assert
(
size
>
0
);
assert
(
size
<= (
INT_MAX
-
1
));
assert
(
format
!=
NULL
);
int
len
;
/* # bytes written, excluding \0 */
/* We take a size_t as input but return an int. Sanity check
* our input so that it won't cause an overflow in the
* vsnprintf return value. */
if
(
size
>
INT_MAX
-
1
) {
len
=
-666
;
goto
Done
;
}
#if
defined(
_MSC_VER
)
len
=
_vsnprintf
(
str
,
size
,
format
,
va
);
#else
len
=
vsnprintf
(
str
,
size
,
format
,
va
);
#endif
Done
:
if
(
size
>
0
) {
str
[
size
-
1
]
=
'\0'
;
}
return
len
;
}
Back
|
FazBrowse Home
|
New Git URL