An analysis of error handling in C’s strtod family shows that converting an invalid string can leave errno at zero in glibc and set it to EINVAL in musl. To determine whether any numeric input was consumed, check whether endptr equals the start of the input. Underflow reporting in standard C depends on the implementation and does not provide complete portability. The POSIX specification checked directly requires ERANGE for range errors but makes EINVAL optional for conversion failure. Robust checks should not depend solely on either the return value or errno.