2004-06-08 15:52:54 -03:00
|
|
|
/* -*- Mode: C; c-file-style: "python" -*- */
|
|
|
|
|
|
|
|
#include <Python.h>
|
|
|
|
#include <locale.h>
|
|
|
|
|
|
|
|
/**
|
|
|
|
* PyOS_ascii_strtod:
|
|
|
|
* @nptr: the string to convert to a numeric value.
|
|
|
|
* @endptr: if non-%NULL, it returns the character after
|
|
|
|
* the last character used in the conversion.
|
|
|
|
*
|
|
|
|
* Converts a string to a #gdouble value.
|
|
|
|
* This function behaves like the standard strtod() function
|
|
|
|
* does in the C locale. It does this without actually
|
|
|
|
* changing the current locale, since that would not be
|
|
|
|
* thread-safe.
|
|
|
|
*
|
|
|
|
* This function is typically used when reading configuration
|
|
|
|
* files or other non-user input that should be locale independent.
|
|
|
|
* To handle input from the user you should normally use the
|
|
|
|
* locale-sensitive system strtod() function.
|
|
|
|
*
|
|
|
|
* If the correct value would cause overflow, plus or minus %HUGE_VAL
|
|
|
|
* is returned (according to the sign of the value), and %ERANGE is
|
|
|
|
* stored in %errno. If the correct value would cause underflow,
|
|
|
|
* zero is returned and %ERANGE is stored in %errno.
|
2006-05-29 11:28:05 -03:00
|
|
|
* If memory allocation fails, %ENOMEM is stored in %errno.
|
2004-06-08 15:52:54 -03:00
|
|
|
*
|
|
|
|
* This function resets %errno before calling strtod() so that
|
|
|
|
* you can reliably detect overflow and underflow.
|
|
|
|
*
|
|
|
|
* Return value: the #gdouble value.
|
|
|
|
**/
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
|
|
|
/*
|
|
|
|
Use system strtod; since strtod is locale aware, we may
|
|
|
|
have to first fix the decimal separator.
|
|
|
|
|
|
|
|
Note that unlike _Py_dg_strtod, the system strtod may not always give
|
|
|
|
correctly rounded results.
|
|
|
|
*/
|
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
double
|
2005-12-18 01:03:17 -04:00
|
|
|
PyOS_ascii_strtod(const char *nptr, char **endptr)
|
2004-06-08 15:52:54 -03:00
|
|
|
{
|
|
|
|
char *fail_pos;
|
2005-12-18 01:37:36 -04:00
|
|
|
double val = -1.0;
|
2004-06-08 15:52:54 -03:00
|
|
|
struct lconv *locale_data;
|
|
|
|
const char *decimal_point;
|
2006-01-07 21:03:36 -04:00
|
|
|
size_t decimal_point_len;
|
2004-06-08 15:52:54 -03:00
|
|
|
const char *p, *decimal_point_pos;
|
|
|
|
const char *end = NULL; /* Silence gcc */
|
2008-01-04 20:59:59 -04:00
|
|
|
const char *digits_pos = NULL;
|
|
|
|
int negate = 0;
|
2004-06-08 15:52:54 -03:00
|
|
|
|
|
|
|
assert(nptr != NULL);
|
|
|
|
|
|
|
|
fail_pos = NULL;
|
|
|
|
|
|
|
|
locale_data = localeconv();
|
|
|
|
decimal_point = locale_data->decimal_point;
|
|
|
|
decimal_point_len = strlen(decimal_point);
|
|
|
|
|
|
|
|
assert(decimal_point_len != 0);
|
|
|
|
|
|
|
|
decimal_point_pos = NULL;
|
2008-01-04 20:59:59 -04:00
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
/* Set errno to zero, so that we can distinguish zero results
|
|
|
|
and underflows */
|
|
|
|
errno = 0;
|
|
|
|
|
2008-01-04 20:59:59 -04:00
|
|
|
/* We process any leading whitespace and the optional sign manually,
|
|
|
|
then pass the remainder to the system strtod. This ensures that
|
|
|
|
the result of an underflow has the correct sign. (bug #1725) */
|
|
|
|
|
|
|
|
p = nptr;
|
|
|
|
/* Skip leading space */
|
2009-04-27 16:04:37 -03:00
|
|
|
while (Py_ISSPACE(*p))
|
2008-01-04 20:59:59 -04:00
|
|
|
p++;
|
|
|
|
|
|
|
|
/* Process leading sign, if present */
|
|
|
|
if (*p == '-') {
|
|
|
|
negate = 1;
|
|
|
|
p++;
|
2009-04-26 13:04:05 -03:00
|
|
|
}
|
|
|
|
else if (*p == '+') {
|
2008-01-04 20:59:59 -04:00
|
|
|
p++;
|
|
|
|
}
|
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
/* Parse infinities and nans */
|
|
|
|
if (*p == 'i' || *p == 'I') {
|
|
|
|
if (PyOS_strnicmp(p, "inf", 3) == 0) {
|
|
|
|
val = Py_HUGE_VAL;
|
|
|
|
if (PyOS_strnicmp(p+3, "inity", 5) == 0)
|
|
|
|
fail_pos = (char *)p+8;
|
|
|
|
else
|
|
|
|
fail_pos = (char *)p+3;
|
|
|
|
goto got_val;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
goto invalid_string;
|
2008-01-04 20:59:59 -04:00
|
|
|
}
|
2009-04-26 13:04:05 -03:00
|
|
|
#ifdef Py_NAN
|
|
|
|
if (*p == 'n' || *p == 'N') {
|
|
|
|
if (PyOS_strnicmp(p, "nan", 3) == 0) {
|
|
|
|
val = Py_NAN;
|
|
|
|
fail_pos = (char *)p+3;
|
|
|
|
goto got_val;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
goto invalid_string;
|
|
|
|
}
|
|
|
|
#endif
|
2008-01-04 20:59:59 -04:00
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
/* Some platform strtods accept hex floats; Python shouldn't (at the
|
|
|
|
moment), so we check explicitly for strings starting with '0x'. */
|
|
|
|
if (*p == '0' && (*(p+1) == 'x' || *(p+1) == 'X'))
|
|
|
|
goto invalid_string;
|
|
|
|
|
|
|
|
/* Check that what's left begins with a digit or decimal point */
|
2009-04-27 16:04:37 -03:00
|
|
|
if (!Py_ISDIGIT(*p) && *p != '.')
|
2009-04-26 13:04:05 -03:00
|
|
|
goto invalid_string;
|
|
|
|
|
|
|
|
digits_pos = p;
|
|
|
|
if (decimal_point[0] != '.' ||
|
2004-06-08 15:52:54 -03:00
|
|
|
decimal_point[1] != 0)
|
|
|
|
{
|
2009-04-26 13:04:05 -03:00
|
|
|
/* Look for a '.' in the input; if present, it'll need to be
|
|
|
|
swapped for the current locale's decimal point before we
|
|
|
|
call strtod. On the other hand, if we find the current
|
|
|
|
locale's decimal point then the input is invalid. */
|
2009-04-27 16:04:37 -03:00
|
|
|
while (Py_ISDIGIT(*p))
|
2005-12-18 01:03:17 -04:00
|
|
|
p++;
|
|
|
|
|
|
|
|
if (*p == '.')
|
2004-06-08 15:52:54 -03:00
|
|
|
{
|
2005-12-18 01:03:17 -04:00
|
|
|
decimal_point_pos = p++;
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
/* locate end of number */
|
2009-04-27 16:04:37 -03:00
|
|
|
while (Py_ISDIGIT(*p))
|
2004-06-08 15:52:54 -03:00
|
|
|
p++;
|
|
|
|
|
2005-12-18 01:03:17 -04:00
|
|
|
if (*p == 'e' || *p == 'E')
|
|
|
|
p++;
|
|
|
|
if (*p == '+' || *p == '-')
|
|
|
|
p++;
|
2009-04-27 16:04:37 -03:00
|
|
|
while (Py_ISDIGIT(*p))
|
2004-06-08 15:52:54 -03:00
|
|
|
p++;
|
2005-12-18 01:03:17 -04:00
|
|
|
end = p;
|
2004-06-08 15:52:54 -03:00
|
|
|
}
|
2006-07-03 09:19:50 -03:00
|
|
|
else if (strncmp(p, decimal_point, decimal_point_len) == 0)
|
|
|
|
/* Python bug #1417699 */
|
2009-04-26 13:04:05 -03:00
|
|
|
goto invalid_string;
|
2008-03-17 09:14:29 -03:00
|
|
|
/* For the other cases, we need not convert the decimal
|
|
|
|
point */
|
2004-06-08 15:52:54 -03:00
|
|
|
}
|
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
if (decimal_point_pos) {
|
2004-06-08 15:52:54 -03:00
|
|
|
char *copy, *c;
|
2009-04-26 13:04:05 -03:00
|
|
|
/* Create a copy of the input, with the '.' converted to the
|
|
|
|
locale-specific decimal point */
|
2008-01-04 20:59:59 -04:00
|
|
|
copy = (char *)PyMem_MALLOC(end - digits_pos +
|
|
|
|
1 + decimal_point_len);
|
2006-05-29 11:28:05 -03:00
|
|
|
if (copy == NULL) {
|
|
|
|
if (endptr)
|
2006-05-29 11:33:55 -03:00
|
|
|
*endptr = (char *)nptr;
|
2006-05-29 11:28:05 -03:00
|
|
|
errno = ENOMEM;
|
|
|
|
return val;
|
|
|
|
}
|
2004-06-08 15:52:54 -03:00
|
|
|
|
|
|
|
c = copy;
|
2008-01-04 20:59:59 -04:00
|
|
|
memcpy(c, digits_pos, decimal_point_pos - digits_pos);
|
|
|
|
c += decimal_point_pos - digits_pos;
|
2004-06-08 15:52:54 -03:00
|
|
|
memcpy(c, decimal_point, decimal_point_len);
|
|
|
|
c += decimal_point_len;
|
2008-03-17 09:14:29 -03:00
|
|
|
memcpy(c, decimal_point_pos + 1,
|
|
|
|
end - (decimal_point_pos + 1));
|
2004-06-08 15:52:54 -03:00
|
|
|
c += end - (decimal_point_pos + 1);
|
|
|
|
*c = 0;
|
|
|
|
|
|
|
|
val = strtod(copy, &fail_pos);
|
|
|
|
|
|
|
|
if (fail_pos)
|
|
|
|
{
|
|
|
|
if (fail_pos > decimal_point_pos)
|
2008-01-04 20:59:59 -04:00
|
|
|
fail_pos = (char *)digits_pos +
|
|
|
|
(fail_pos - copy) -
|
|
|
|
(decimal_point_len - 1);
|
2004-06-08 15:52:54 -03:00
|
|
|
else
|
2008-01-04 20:59:59 -04:00
|
|
|
fail_pos = (char *)digits_pos +
|
|
|
|
(fail_pos - copy);
|
2004-06-08 15:52:54 -03:00
|
|
|
}
|
|
|
|
|
2006-05-25 17:44:08 -03:00
|
|
|
PyMem_FREE(copy);
|
2004-06-08 15:52:54 -03:00
|
|
|
|
|
|
|
}
|
2005-12-18 01:03:17 -04:00
|
|
|
else {
|
2008-01-04 20:59:59 -04:00
|
|
|
val = strtod(digits_pos, &fail_pos);
|
2005-12-18 01:03:17 -04:00
|
|
|
}
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2008-01-04 20:59:59 -04:00
|
|
|
if (fail_pos == digits_pos)
|
2009-04-26 13:04:05 -03:00
|
|
|
goto invalid_string;
|
2008-01-04 20:59:59 -04:00
|
|
|
|
2009-04-26 13:04:05 -03:00
|
|
|
got_val:
|
2008-01-04 20:59:59 -04:00
|
|
|
if (negate && fail_pos != nptr)
|
|
|
|
val = -val;
|
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
if (endptr)
|
|
|
|
*endptr = fail_pos;
|
|
|
|
|
|
|
|
return val;
|
2009-04-26 13:04:05 -03:00
|
|
|
|
|
|
|
invalid_string:
|
|
|
|
if (endptr)
|
|
|
|
*endptr = (char*)nptr;
|
|
|
|
errno = EINVAL;
|
|
|
|
return -1.0;
|
2004-06-08 15:52:54 -03:00
|
|
|
}
|
|
|
|
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
double
|
|
|
|
PyOS_ascii_atof(const char *nptr)
|
|
|
|
{
|
|
|
|
return PyOS_ascii_strtod(nptr, NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2008-04-29 22:09:30 -03:00
|
|
|
/* Given a string that may have a decimal point in the current
|
|
|
|
locale, change it back to a dot. Since the string cannot get
|
|
|
|
longer, no need for a maximum buffer size parameter. */
|
|
|
|
Py_LOCAL_INLINE(void)
|
|
|
|
change_decimal_from_locale_to_dot(char* buffer)
|
|
|
|
{
|
|
|
|
struct lconv *locale_data = localeconv();
|
|
|
|
const char *decimal_point = locale_data->decimal_point;
|
|
|
|
|
|
|
|
if (decimal_point[0] != '.' || decimal_point[1] != 0) {
|
|
|
|
size_t decimal_point_len = strlen(decimal_point);
|
|
|
|
|
|
|
|
if (*buffer == '+' || *buffer == '-')
|
|
|
|
buffer++;
|
2009-04-27 16:04:37 -03:00
|
|
|
while (Py_ISDIGIT(*buffer))
|
2008-04-29 22:09:30 -03:00
|
|
|
buffer++;
|
|
|
|
if (strncmp(buffer, decimal_point, decimal_point_len) == 0) {
|
|
|
|
*buffer = '.';
|
|
|
|
buffer++;
|
|
|
|
if (decimal_point_len > 1) {
|
|
|
|
/* buffer needs to get smaller */
|
|
|
|
size_t rest_len = strlen(buffer +
|
|
|
|
(decimal_point_len - 1));
|
|
|
|
memmove(buffer,
|
|
|
|
buffer + (decimal_point_len - 1),
|
|
|
|
rest_len);
|
|
|
|
buffer[rest_len] = 0;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
Py_LOCAL_INLINE(void)
|
|
|
|
ensure_sign(char* buffer, size_t buf_size)
|
|
|
|
{
|
2009-04-28 04:33:09 -03:00
|
|
|
size_t len;
|
2009-04-25 18:40:15 -03:00
|
|
|
|
|
|
|
if (buffer[0] == '-')
|
|
|
|
/* Already have a sign. */
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Include the trailing 0 byte. */
|
|
|
|
len = strlen(buffer)+1;
|
|
|
|
if (len >= buf_size+1)
|
|
|
|
/* No room for the sign, don't do anything. */
|
|
|
|
return;
|
|
|
|
|
|
|
|
memmove(buffer+1, buffer, len);
|
|
|
|
buffer[0] = '+';
|
|
|
|
}
|
|
|
|
|
2008-02-20 19:34:22 -04:00
|
|
|
/* From the C99 standard, section 7.19.6:
|
|
|
|
The exponent always contains at least two digits, and only as many more digits
|
|
|
|
as necessary to represent the exponent.
|
|
|
|
*/
|
|
|
|
#define MIN_EXPONENT_DIGITS 2
|
|
|
|
|
2008-04-29 22:09:30 -03:00
|
|
|
/* Ensure that any exponent, if present, is at least MIN_EXPONENT_DIGITS
|
|
|
|
in length. */
|
|
|
|
Py_LOCAL_INLINE(void)
|
2009-04-26 16:54:55 -03:00
|
|
|
ensure_minimum_exponent_length(char* buffer, size_t buf_size)
|
2008-04-29 22:09:30 -03:00
|
|
|
{
|
|
|
|
char *p = strpbrk(buffer, "eE");
|
|
|
|
if (p && (*(p + 1) == '-' || *(p + 1) == '+')) {
|
|
|
|
char *start = p + 2;
|
|
|
|
int exponent_digit_cnt = 0;
|
|
|
|
int leading_zero_cnt = 0;
|
|
|
|
int in_leading_zeros = 1;
|
|
|
|
int significant_digit_cnt;
|
|
|
|
|
|
|
|
/* Skip over the exponent and the sign. */
|
|
|
|
p += 2;
|
|
|
|
|
|
|
|
/* Find the end of the exponent, keeping track of leading
|
|
|
|
zeros. */
|
2009-04-27 16:04:37 -03:00
|
|
|
while (*p && Py_ISDIGIT(*p)) {
|
2008-04-29 22:09:30 -03:00
|
|
|
if (in_leading_zeros && *p == '0')
|
|
|
|
++leading_zero_cnt;
|
|
|
|
if (*p != '0')
|
|
|
|
in_leading_zeros = 0;
|
|
|
|
++p;
|
|
|
|
++exponent_digit_cnt;
|
|
|
|
}
|
|
|
|
|
|
|
|
significant_digit_cnt = exponent_digit_cnt - leading_zero_cnt;
|
|
|
|
if (exponent_digit_cnt == MIN_EXPONENT_DIGITS) {
|
|
|
|
/* If there are 2 exactly digits, we're done,
|
|
|
|
regardless of what they contain */
|
|
|
|
}
|
|
|
|
else if (exponent_digit_cnt > MIN_EXPONENT_DIGITS) {
|
|
|
|
int extra_zeros_cnt;
|
|
|
|
|
|
|
|
/* There are more than 2 digits in the exponent. See
|
|
|
|
if we can delete some of the leading zeros */
|
|
|
|
if (significant_digit_cnt < MIN_EXPONENT_DIGITS)
|
|
|
|
significant_digit_cnt = MIN_EXPONENT_DIGITS;
|
|
|
|
extra_zeros_cnt = exponent_digit_cnt -
|
|
|
|
significant_digit_cnt;
|
|
|
|
|
|
|
|
/* Delete extra_zeros_cnt worth of characters from the
|
|
|
|
front of the exponent */
|
|
|
|
assert(extra_zeros_cnt >= 0);
|
|
|
|
|
|
|
|
/* Add one to significant_digit_cnt to copy the
|
|
|
|
trailing 0 byte, thus setting the length */
|
|
|
|
memmove(start,
|
|
|
|
start + extra_zeros_cnt,
|
|
|
|
significant_digit_cnt + 1);
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
/* If there are fewer than 2 digits, add zeros
|
|
|
|
until there are 2, if there's enough room */
|
|
|
|
int zeros = MIN_EXPONENT_DIGITS - exponent_digit_cnt;
|
|
|
|
if (start + zeros + exponent_digit_cnt + 1
|
|
|
|
< buffer + buf_size) {
|
|
|
|
memmove(start + zeros, start,
|
|
|
|
exponent_digit_cnt + 1);
|
|
|
|
memset(start, '0', zeros);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
/* Ensure that buffer has a decimal point in it. The decimal point will not
|
|
|
|
be in the current locale, it will always be '.'. Don't add a decimal if an
|
|
|
|
exponent is present. */
|
2008-04-29 22:09:30 -03:00
|
|
|
Py_LOCAL_INLINE(void)
|
|
|
|
ensure_decimal_point(char* buffer, size_t buf_size)
|
|
|
|
{
|
|
|
|
int insert_count = 0;
|
|
|
|
char* chars_to_insert;
|
|
|
|
|
|
|
|
/* search for the first non-digit character */
|
|
|
|
char *p = buffer;
|
2008-07-18 21:24:05 -03:00
|
|
|
if (*p == '-' || *p == '+')
|
|
|
|
/* Skip leading sign, if present. I think this could only
|
|
|
|
ever be '-', but it can't hurt to check for both. */
|
|
|
|
++p;
|
2009-04-27 16:04:37 -03:00
|
|
|
while (*p && Py_ISDIGIT(*p))
|
2008-04-29 22:09:30 -03:00
|
|
|
++p;
|
|
|
|
|
|
|
|
if (*p == '.') {
|
2009-04-27 16:04:37 -03:00
|
|
|
if (Py_ISDIGIT(*(p+1))) {
|
2008-04-29 22:09:30 -03:00
|
|
|
/* Nothing to do, we already have a decimal
|
|
|
|
point and a digit after it */
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
/* We have a decimal point, but no following
|
|
|
|
digit. Insert a zero after the decimal. */
|
|
|
|
++p;
|
|
|
|
chars_to_insert = "0";
|
|
|
|
insert_count = 1;
|
|
|
|
}
|
|
|
|
}
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
else if (!(*p == 'e' || *p == 'E')) {
|
|
|
|
/* Don't add ".0" if we have an exponent. */
|
2008-04-29 22:09:30 -03:00
|
|
|
chars_to_insert = ".0";
|
|
|
|
insert_count = 2;
|
|
|
|
}
|
|
|
|
if (insert_count) {
|
|
|
|
size_t buf_len = strlen(buffer);
|
|
|
|
if (buf_len + insert_count + 1 >= buf_size) {
|
|
|
|
/* If there is not enough room in the buffer
|
|
|
|
for the additional text, just skip it. It's
|
|
|
|
not worth generating an error over. */
|
|
|
|
}
|
|
|
|
else {
|
|
|
|
memmove(p + insert_count, p,
|
|
|
|
buffer + strlen(buffer) - p + 1);
|
|
|
|
memcpy(p, chars_to_insert, insert_count);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2008-02-20 19:34:22 -04:00
|
|
|
/* see FORMATBUFLEN in unicodeobject.c */
|
|
|
|
#define FLOAT_FORMATBUFLEN 120
|
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
/**
|
2009-04-25 18:40:15 -03:00
|
|
|
* _PyOS_ascii_formatd:
|
2004-06-08 15:52:54 -03:00
|
|
|
* @buffer: A buffer to place the resulting string in
|
2008-03-17 08:01:01 -03:00
|
|
|
* @buf_size: The length of the buffer.
|
2004-06-08 15:52:54 -03:00
|
|
|
* @format: The printf()-style format to use for the
|
|
|
|
* code to use for converting.
|
|
|
|
* @d: The #gdouble to convert
|
|
|
|
*
|
|
|
|
* Converts a #gdouble to a string, using the '.' as
|
|
|
|
* decimal point. To format the number you pass in
|
|
|
|
* a printf()-style format string. Allowed conversion
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
* specifiers are 'e', 'E', 'f', 'F', 'g', 'G', and 'Z'.
|
2004-06-08 15:52:54 -03:00
|
|
|
*
|
2008-03-17 08:01:01 -03:00
|
|
|
* 'Z' is the same as 'g', except it always has a decimal and
|
|
|
|
* at least one digit after the decimal.
|
2008-02-20 19:34:22 -04:00
|
|
|
*
|
2004-06-08 15:52:54 -03:00
|
|
|
* Return value: The pointer to the buffer with the converted string.
|
|
|
|
**/
|
2009-04-25 18:40:15 -03:00
|
|
|
/* DEPRECATED, will be deleted in 2.8 and 3.2 */
|
|
|
|
PyAPI_FUNC(char *)
|
2004-06-08 15:52:54 -03:00
|
|
|
PyOS_ascii_formatd(char *buffer,
|
2008-03-17 08:01:01 -03:00
|
|
|
size_t buf_size,
|
2004-06-08 15:52:54 -03:00
|
|
|
const char *format,
|
|
|
|
double d)
|
|
|
|
{
|
|
|
|
char format_char;
|
2008-02-20 19:34:22 -04:00
|
|
|
size_t format_len = strlen(format);
|
|
|
|
|
2008-03-17 08:01:01 -03:00
|
|
|
/* Issue 2264: code 'Z' requires copying the format. 'Z' is 'g', but
|
|
|
|
also with at least one character past the decimal. */
|
2008-02-20 19:34:22 -04:00
|
|
|
char tmp_format[FLOAT_FORMATBUFLEN];
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
if (PyErr_WarnEx(PyExc_DeprecationWarning,
|
|
|
|
"PyOS_ascii_formatd is deprecated, "
|
|
|
|
"use PyOS_double_to_string instead", 1) < 0)
|
|
|
|
return NULL;
|
|
|
|
|
2008-02-20 19:34:22 -04:00
|
|
|
/* The last character in the format string must be the format char */
|
|
|
|
format_char = format[format_len - 1];
|
2004-06-08 15:52:54 -03:00
|
|
|
|
|
|
|
if (format[0] != '%')
|
|
|
|
return NULL;
|
|
|
|
|
2008-02-20 19:34:22 -04:00
|
|
|
/* I'm not sure why this test is here. It's ensuring that the format
|
|
|
|
string after the first character doesn't have a single quote, a
|
|
|
|
lowercase l, or a percent. This is the reverse of the commented-out
|
|
|
|
test about 10 lines ago. */
|
2004-06-08 15:52:54 -03:00
|
|
|
if (strpbrk(format + 1, "'l%"))
|
|
|
|
return NULL;
|
|
|
|
|
2008-03-17 08:01:01 -03:00
|
|
|
/* Also curious about this function is that it accepts format strings
|
|
|
|
like "%xg", which are invalid for floats. In general, the
|
|
|
|
interface to this function is not very good, but changing it is
|
|
|
|
difficult because it's a public API. */
|
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
if (!(format_char == 'e' || format_char == 'E' ||
|
|
|
|
format_char == 'f' || format_char == 'F' ||
|
2008-02-20 19:34:22 -04:00
|
|
|
format_char == 'g' || format_char == 'G' ||
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
format_char == 'Z'))
|
2004-06-08 15:52:54 -03:00
|
|
|
return NULL;
|
|
|
|
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
/* Map 'Z' format_char to 'g', by copying the format string and
|
2008-03-17 08:01:01 -03:00
|
|
|
replacing the final char with a 'g' */
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
if (format_char == 'Z') {
|
2008-02-20 19:34:22 -04:00
|
|
|
if (format_len + 1 >= sizeof(tmp_format)) {
|
|
|
|
/* The format won't fit in our copy. Error out. In
|
2008-03-17 09:14:29 -03:00
|
|
|
practice, this will never happen and will be
|
|
|
|
detected by returning NULL */
|
2008-02-20 19:34:22 -04:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
strcpy(tmp_format, format);
|
|
|
|
tmp_format[format_len - 1] = 'g';
|
|
|
|
format = tmp_format;
|
|
|
|
}
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2008-03-17 08:01:01 -03:00
|
|
|
|
2008-02-20 19:34:22 -04:00
|
|
|
/* Have PyOS_snprintf do the hard work */
|
2008-03-17 08:01:01 -03:00
|
|
|
PyOS_snprintf(buffer, buf_size, format, d);
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2008-04-29 22:09:30 -03:00
|
|
|
/* Do various fixups on the return string */
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2008-04-29 22:09:30 -03:00
|
|
|
/* Get the current locale, and find the decimal point string.
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
Convert that string back to a dot. */
|
|
|
|
change_decimal_from_locale_to_dot(buffer);
|
2008-02-20 19:34:22 -04:00
|
|
|
|
|
|
|
/* If an exponent exists, ensure that the exponent is at least
|
|
|
|
MIN_EXPONENT_DIGITS digits, providing the buffer is large enough
|
|
|
|
for the extra zeros. Also, if there are more than
|
|
|
|
MIN_EXPONENT_DIGITS, remove as many zeros as possible until we get
|
|
|
|
back to MIN_EXPONENT_DIGITS */
|
2009-04-26 16:54:55 -03:00
|
|
|
ensure_minimum_exponent_length(buffer, buf_size);
|
2004-06-08 15:52:54 -03:00
|
|
|
|
2008-03-17 08:01:01 -03:00
|
|
|
/* If format_char is 'Z', make sure we have at least one character
|
|
|
|
after the decimal point (and make sure we have a decimal point). */
|
2008-04-29 22:09:30 -03:00
|
|
|
if (format_char == 'Z')
|
|
|
|
ensure_decimal_point(buffer, buf_size);
|
2008-03-17 08:01:01 -03:00
|
|
|
|
2004-06-08 15:52:54 -03:00
|
|
|
return buffer;
|
|
|
|
}
|
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
PyAPI_FUNC(void)
|
|
|
|
_PyOS_double_to_string(char *buf, size_t buf_len, double val,
|
|
|
|
char format_code, int precision,
|
|
|
|
int flags, int *ptype)
|
2004-06-08 15:52:54 -03:00
|
|
|
{
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
char format[32];
|
|
|
|
int t;
|
|
|
|
int upper = 0;
|
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
if (buf_len < 1) {
|
|
|
|
assert(0);
|
|
|
|
/* There's no way to signal this error. Just return. */
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
buf[0] = 0;
|
|
|
|
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
/* Validate format_code, and map upper and lower case */
|
|
|
|
switch (format_code) {
|
|
|
|
case 'e': /* exponent */
|
|
|
|
case 'f': /* fixed */
|
|
|
|
case 'g': /* general */
|
|
|
|
break;
|
|
|
|
case 'E':
|
|
|
|
upper = 1;
|
|
|
|
format_code = 'e';
|
|
|
|
break;
|
|
|
|
case 'F':
|
|
|
|
upper = 1;
|
|
|
|
format_code = 'f';
|
|
|
|
break;
|
|
|
|
case 'G':
|
|
|
|
upper = 1;
|
|
|
|
format_code = 'g';
|
|
|
|
break;
|
|
|
|
case 'r': /* repr format */
|
|
|
|
/* Supplied precision is unused, must be 0. */
|
2009-04-25 18:40:15 -03:00
|
|
|
if (precision != 0)
|
|
|
|
return;
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
precision = 17;
|
|
|
|
format_code = 'g';
|
|
|
|
break;
|
|
|
|
case 's': /* str format */
|
|
|
|
/* Supplied precision is unused, must be 0. */
|
2009-04-25 18:40:15 -03:00
|
|
|
if (precision != 0)
|
|
|
|
return;
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
precision = 12;
|
|
|
|
format_code = 'g';
|
|
|
|
break;
|
|
|
|
default:
|
2009-04-25 18:40:15 -03:00
|
|
|
assert(0);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Check for buf too small to fit "-inf". Other buffer too small
|
|
|
|
conditions are dealt with when converting or formatting finite
|
|
|
|
numbers. */
|
|
|
|
if (buf_len < 5) {
|
|
|
|
assert(0);
|
|
|
|
return;
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Handle nan and inf. */
|
|
|
|
if (Py_IS_NAN(val)) {
|
|
|
|
strcpy(buf, "nan");
|
|
|
|
t = Py_DTST_NAN;
|
|
|
|
} else if (Py_IS_INFINITY(val)) {
|
|
|
|
if (copysign(1., val) == 1.)
|
|
|
|
strcpy(buf, "inf");
|
|
|
|
else
|
|
|
|
strcpy(buf, "-inf");
|
|
|
|
t = Py_DTST_INFINITE;
|
|
|
|
} else {
|
|
|
|
t = Py_DTST_FINITE;
|
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* Build the format string. */
|
|
|
|
PyOS_snprintf(format, sizeof(format), "%%%s.%i%c",
|
|
|
|
(flags & Py_DTSF_ALT ? "#" : ""), precision,
|
|
|
|
format_code);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* Have PyOS_snprintf do the hard work. */
|
|
|
|
PyOS_snprintf(buf, buf_len, format, val);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* Do various fixups on the return string */
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* Get the current locale, and find the decimal point string.
|
|
|
|
Convert that string back to a dot. */
|
|
|
|
change_decimal_from_locale_to_dot(buf);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* If an exponent exists, ensure that the exponent is at least
|
|
|
|
MIN_EXPONENT_DIGITS digits, providing the buffer is large
|
|
|
|
enough for the extra zeros. Also, if there are more than
|
|
|
|
MIN_EXPONENT_DIGITS, remove as many zeros as possible until
|
|
|
|
we get back to MIN_EXPONENT_DIGITS */
|
2009-04-26 16:54:55 -03:00
|
|
|
ensure_minimum_exponent_length(buf, buf_len);
|
2009-04-25 18:40:15 -03:00
|
|
|
|
|
|
|
/* Possibly make sure we have at least one character after the
|
|
|
|
decimal point (and make sure we have a decimal point). */
|
|
|
|
if (flags & Py_DTSF_ADD_DOT_0)
|
|
|
|
ensure_decimal_point(buf, buf_len);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
}
|
|
|
|
|
2009-04-25 18:40:15 -03:00
|
|
|
/* Add the sign if asked and the result isn't negative. */
|
2009-04-24 09:46:53 -03:00
|
|
|
if (flags & Py_DTSF_SIGN && buf[0] != '-')
|
2009-04-25 18:40:15 -03:00
|
|
|
ensure_sign(buf, buf_len);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
|
|
|
if (upper) {
|
|
|
|
/* Convert to upper case. */
|
2009-04-25 18:40:15 -03:00
|
|
|
char *p;
|
|
|
|
for (p = buf; *p; p++)
|
|
|
|
*p = toupper(*p);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (ptype)
|
|
|
|
*ptype = t;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
PyAPI_FUNC(char *) PyOS_double_to_string(double val,
|
|
|
|
char format_code,
|
|
|
|
int precision,
|
|
|
|
int flags,
|
|
|
|
int *ptype)
|
|
|
|
{
|
|
|
|
char buf[128];
|
|
|
|
Py_ssize_t len;
|
|
|
|
char *result;
|
|
|
|
|
|
|
|
_PyOS_double_to_string(buf, sizeof(buf), val, format_code, precision,
|
|
|
|
flags, ptype);
|
|
|
|
len = strlen(buf);
|
|
|
|
if (len == 0) {
|
|
|
|
PyErr_BadInternalCall();
|
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Add 1 for the trailing 0 byte. */
|
|
|
|
result = PyMem_Malloc(len + 1);
|
|
|
|
if (result == NULL) {
|
|
|
|
PyErr_NoMemory();
|
|
|
|
return NULL;
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
}
|
2009-04-25 18:40:15 -03:00
|
|
|
strcpy(result, buf);
|
Backport of some of the work in r71665 to trunk. This reworks much of
int, long, and float __format__(), and it keeps their implementation
in sync with py3k.
Also added PyOS_double_to_string. This is the "fallback" version
that's also available in trunk, and should be kept in sync with that
code. I'll add an issue to document PyOS_double_to_string in the C
API.
There are many internal cleanups. Externally visible changes include:
- Implement PEP 378, Format Specifier for Thousands Separator, for
floats, ints, and longs.
- Issue #5515: 'n' formatting for ints, longs, and floats handles
leading zero formatting poorly.
- Issue #5772: For float.__format__, don't add a trailing ".0" if
we're using no type code and we have an exponent.
2009-04-22 10:29:05 -03:00
|
|
|
|
|
|
|
return result;
|
2004-06-08 15:52:54 -03:00
|
|
|
}
|