Checking strtod errors portably is more complicated than the man page suggests
Standard C’s strtod error reporting depends on math_errhandling: overflow may be reported through errno or floating-point exceptions, and underflow need not be reported at all. Invalid input is a separate case; use endptr to tell whether conversion happened, rather than relying on errno.
The article also points out a libc difference that the Linux man page doesn’t explain: for invalid input, glibc leaves errno alone while musl sets EINVAL. In the 18-comment Lobsters thread, one reader lamented that C’s apparent simplicity keeps yielding obscure corners; much of the discussion wandered into language preferences rather than challenging the technical analysis.