This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/45399] [C++0x] Warning for \0 in raw strings
- 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: Wed, 15 Jun 2011 18:40:57 +0000
- Subject: [Bug c++/45399] [C++0x] Warning for \0 in raw strings
- Auto-submitted: auto-generated
- References: <bug-45399-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45399
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #9 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2011-06-15 18:40:40 UTC ---
(In reply to comment #8)
> No objection I think. Alternatively there could be a switch to control this
> warning.
Or both. I wish clang published a list of their warning options, so we can keep
compatibility.
According to this:
https://llvm.org/viewvc/llvm-project/cfe/trunk/include/clang/Basic/DiagnosticKinds.def?revision=39294&view=markup&sortby=rev&pathrev=63060
They have three different warnings for this but I am not sure if the options
are called -Wnull-in-char, -Wnull-in-string, and -Wnull-in-file.