string-literals

This is valid, because a constexpr expression is allowed to take the value of "a glvalue of literal type that refers to a non-volatile object defined with constexpr, or that refers to a sub-object of such an object" (§5.19/2): constexpr char str[] = "hello, world"; constexpr char e = str[1]; However, it would seem that string literals do not fit this description: constexpr char e = "hello, world"[1]; // error: literal is not constexpr 2.14.5/8 describes the type of string literals: Ordinary string literals and UTF-8 string literals are also referred to as narrow string literals. A narrow

Does GCC 4.7 on Linux/x86_64 have a default character encoding by which it validates and decodes the contents of string literals in C source files? Is this configurable? Further, when linking the string data from string literals into the data section of the output does it have a default execution character encoding? Is this configurable? In any configuration is it possible to have a source character encoding that differs from the execution character encoding? (That is will gcc ever transcode between character encodings?) Christian Stieber I don't know how well these options actually work (not

In c# and ruby and many other languages you can denote a string as to not need escaping. in c# its like this string s = @"\whatever\this\is"; the results are when printed \whatever\this\is my question is, is this supported in any form in javascript? Peter Bailey Short answer: No Long answer: Noooooooooooooooooooooooooo Pointy I don't know what you're getting at, but one way to get around the problem of escaping (etc) is use a trick that John Resig seems to like a lot. You include <script> blocks in a page, but give them a "type" like "text/plain" to make sure that the browser doesn't hand them

How can I encode the Unicode character U+0048 (H), say, in a PowerShell string? In C# I would just do this: "\u0048" , but that doesn't appear to work in PowerShell. Shay Levy Replace '\u' with '0x' and cast it to System.Char: PS > [char]0x0048 H You can also use the "$()" syntax to embed a Unicode character into a string: PS > "Acme$([char]0x2122) Company" AcmeT Company Where T is PowerShell's representation of the character for non-registered trademarks. According to the documentation, PowerShell Core 6.0 adds support with this escape sequence: PS> "`u{0048}" H see https://docs.microsoft.com

I'm working in a C, and C++ program. We used to be compiling without the make-strings-writable option. But that was getting a bunch of warnings, so I turned it off. Then I got a whole bunch of errors of the form "Cannot convert const char* to char* in argmuent 3 of function foo". So, I went through and made a whole lot of changes to fix those. However, today, the program CRASHED because the literal "" was getting passed into a function that was expecting a char*, and was setting the 0th character to 0. It wasn't doing anything bad, just trying to edit a constant, and crashing. My question is,

I'm a c++ newbie (just oldschool c). My son asked for help with this and I'm unable to explain it. If he had asked me "how do I compare strings" I would have told him to use strcmp(), but that isn't what is confusing me. Here is what he asked: int main() { cout << ("A"< "Z"); } will print 1 int main() { cout << ("Z"< "A"); } will also print 1, but int main() { cout << ("Z"< "A"); cout << ("A"< "Z"); } will then print 10. Individually both cout statements print 1, but executed in a row I get a different answer? You are comparing memory addresses. Apparently your compiler places the string