Re: should scanf be getting built supporting hexadecimal float

2021-04-19 Thread Corinna Vinschen via Cygwin
On Apr 19 19:53, Corinna Vinschen via Cygwin wrote: > On Apr 19 09:17, Brian Inglis wrote: > > On 2021-04-19 09:07, Brian Inglis wrote: > > > On 2021-04-18 22:09, Keith Thompson via Cygwin wrote: > > > > The *scanf() functions don't handle hexadecimal floating-point input > > > > (for example "0x1p

Re: should scanf be getting built supporting hexadecimal float

2021-04-19 Thread Corinna Vinschen via Cygwin
On Apr 19 09:17, Brian Inglis wrote: > On 2021-04-19 09:07, Brian Inglis wrote: > > On 2021-04-18 22:09, Keith Thompson via Cygwin wrote: > > > The *scanf() functions don't handle hexadecimal floating-point input > > > (for example "0x1p+0" representing 1.0). > > > On Cygwin, the output (compiled w

Re: should scanf be getting built supporting hexadecimal float

2021-04-19 Thread Brian Inglis
On 2021-04-19 09:07, Brian Inglis wrote: On 2021-04-18 22:09, Keith Thompson via Cygwin wrote: The *scanf() functions don't handle hexadecimal floating-point input (for example "0x1p+0" representing 1.0). On Cygwin, the output (compiled with gcc or clang) is: sscanf returned 1, x = 0 (expected 1