[Bug libstdc++/81122] New: parsing f stopped after '0' when reading std::hexfloat >> f;

2017-06-18 Thread koh...@t-online.de
normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: koh...@t-online.de Target Milestone: --- Created attachment 41578 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41578=edit commented example showing the effect An

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

2018-01-26 Thread koh...@t-online.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #8 from Heinz Kohl <koh...@t-online.de> --- o.k., it looks like a flawy definition. First of all, it would be nice, if you would refer my error message to the right instance. It's unclear, what's to do in the meantime. An idea

[Bug libstdc++/81122] [DR 2381] parsing f stopped after '0' when reading std::hexfloat >> f;

2018-01-27 Thread koh...@t-online.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81122 --- Comment #13 from Heinz Kohl <koh...@t-online.de> --- O.k., but following your arguments I'd expect 0xb as result for my second example 0xb.3590da0e2a06736p-3 (attachment 41578), but it's giving 0, also stopping at 'x' and not at '.'