This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/33067] Awkward long decimal expansion for double literal in error.
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 10 Oct 2011 12:45:56 +0000
- Subject: [Bug c++/33067] Awkward long decimal expansion for double literal in error.
- Auto-submitted: auto-generated
- References: <bug-33067-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33067
--- Comment #17 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2011-10-10 12:45:56 UTC ---
(In reply to comment #14)
> Frankly, I'm not convinced that before fixing the *whole* PR49152 we couldn't
> manage to find a way to print floating point constants in a more decent way.
> Maybe not easy, but not impossible.
I personally think that if the object of printing the constant is to recreate
the source code, but the source code won't match anyway, then it is better to
not print it at all. If the goal of printing is some other (debugging, dump
files, ...), then it may make sense.
Another issue is that if someone comes around a fixes PR49152, then your
testcase for printing floating point constants nicely would be broken. Has this
person to come up with a new testcase for this? delete the testcase? It just
makes PR49152 slightly harder to fix.