public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/51397] New: static_assert message formatting
@ 2011-12-03 22:07 dave@boost-consulting.com
  2011-12-04  0:42 ` [Bug c++/51397] " redi at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: dave@boost-consulting.com @ 2011-12-03 22:07 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51397

             Bug #: 51397
           Summary: static_assert message formatting
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dave@boost-consulting.com


I just noticed that GCC can be overly-helpful ;-) when formatting a
static assertion message:

    static_assert('X' != '\130',"'X' has the wrong value");

gives me

    error: static assertion failed: "\'X\' has the wrong value"

I suggest that GCC should drop the surrounding quotes and not try to
escape any characters in the message.  Otherwise, things like

    #define static_assert_(x) static_assert(x, #x)
    static_assert_('X' != '\130')

turn out quite badly.

The point of this facility is, after all, to help programmers report legible
errors!


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2011-12-31 17:31 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-12-03 22:07 [Bug c++/51397] New: static_assert message formatting dave@boost-consulting.com
2011-12-04  0:42 ` [Bug c++/51397] " redi at gcc dot gnu.org
2011-12-31 11:41 ` paolo.carlini at oracle dot com
2011-12-31 12:23 ` paolo.carlini at oracle dot com
2011-12-31 17:31 ` paolo at gcc dot gnu.org
2011-12-31 17:58 ` paolo.carlini at oracle dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).