tests/printf.err

2,34: value not completely converted
0xABCDEF12345678901: Number out of range
15.1: value not completely converted
fix raw_string_to_scalar_type locale handling Fixes #3334 2016-08-29 20:11:40 -07:00			`2,34: value not completely converted`
use a consistent ERANGE message The previous change neglected to consider that numbers too large for the long long datatype will result in calling strerror(ERANGE) whose return value can vary depending on the platform. Which breaks the unit test. 2017-02-20 18:43:13 -08:00			`0xABCDEF12345678901: Number out of range`
printf: Don't die on incomplete conversions POSIX dictates here that incomplete conversions, like in printf %d\n 15.2 or printf %d 14g are still printed along with any error. This seems alright, as it allows users to silence stderr to accept incomplete conversions. This commit implements it, but what's a bit weird is the ordering between stdout and stderr, causing the error to be printed _after_, like 15 14 15.1: value not completely converted 14,2: value not completely converted but that seems like a general issue with how we buffer the streams. (I know that nonfatal_error is a copy of most of fatal_error - I tried differently, and va_* is weird) Fixes #5532. 2019-03-17 16:33:58 +01:00			`15.1: value not completely converted`