https://en.wikipedia.org/wiki/C++11#New_string_literals Reproducible: Always Steps to Reproduce: 1. Type a raw string, for example: char const *myRawString = R"%:!#meow("Hello world!" )%:!#meow"; 2. Look at the syntax highlighting. 3. Submit bug report. Actual Results: Syntax highlighting is wrong. Expected Results: Syntax highlighting should somehow make it clear that it's equivalent to: char const *myRawString = "\"Hello world!\"\n";
confirmed, but needs to be fixed in the Kate C++ highlighting schema.
C++11 raw string literals are supported in C++11 (surprise) syntax highlighter
Could we unite the C++ and C++11 Highlighting? I think the C++11 constructs will become more and more important and should be on per default. Milian & Alex, could you perhaps crosscheck, if that is feasible? Would be bad to have some regressions in C++ HL and would be bad if we now start to add C++11 features again to C++ highlighting that are already done by Alex.
(In reply to comment #3) > Could we unite the C++ and C++11 Highlighting? there is nothing to "unite". C++11 highlighter can do everything C++ can plus few other features and "bug" fixes...
Then I would vote for replacing C++ with C++11, Milian, would that be OK for you too?
Sure, sounds good to me. Will need some promo to ensure people select qt4.xml where appropriate though as thats what cpp.xml did before.
Git commit b0b745047223cdd847e9bd7983f3ba415747e6d1 by Christoph Cullmann. Committed on 28/01/2014 at 08:53. Pushed by cullmann into branch 'master'. C++11 => C++ highlighting As C++-1y code is more and more common, that shall be the standard C++ highlighting M +345 -178 part/syntax/data/cpp.xml D +0 -496 part/syntax/data/cpp11.xml http://commits.kde.org/kate/b0b745047223cdd847e9bd7983f3ba415747e6d1
Done in ktexteditor.git, too. Fixed qt4.xml to refer to C++ hl, too (and renamed it to C++/Qt4)