I think that the best way of doing this, as Douglas Crockford (one of the biggests gurus of JavaScript) suggests in here is using the JSON native parser, as it is not only faster than the eval(), it’s also more secure. Native JSON parser is already available in: Firefox 3.5+ IE 8+ Opera 10.5+ Safari … Read more
This is all 100% standardized. C17 6.10.8.1: __DATE__ The date of translation of the preprocessing translation unit: a character string literal of the form “Mmm dd yyyy” … and the first character of dd is a space character if the value is less than 10. … __TIME__ The time of translation of the preprocessing translation … Read more
None of the other answers really explain why the compiler generates the code it does in your Godbolt link, so I thought I’d chip in. If you look at the generated code, you can see that: std::cout << ‘\n’; Compiles down to, in effect: const char c=”\n”; std::cout.operator<< (&c, 1); and to make this work, … Read more
Strings in .NET are reference types, so they are always on the heap (even when they are interned). You can verify this using a debugger such as WinDbg. If you have the class below class SomeType { public void Foo() { string s = “hello world”; Console.WriteLine(s); Console.WriteLine(“press enter”); Console.ReadLine(); } } And you call … Read more
why did not delphi give any error saying the length is beyond 255 for myExtremlyLongString? You have your answer a bit down in the text in section Long String (AnsiString). In current versions of Delphi, the string type is simply an alias for AnsiString, So string is not limited to 255 characters but a string … Read more
Is it constexpr char * const my_str = “hello”; No, because a string literal is not convertible to a pointer to char. (It used to be prior to C++11, but even then the conversion was deprecated). or const char * constexpr my_str = “hello”; No. constexpr cannot go there. This would be well formed: constexpr … Read more
This code is fine across all platforms. The string gets compiled into the binary as a static string literal. If you are on windows for example you can even open your .exe with notepad and search for the string itself. Since it is a static string literal scope does not matter. String pooling: One thing … Read more
Well … Sort of. The easiest is to just use the fact that adjacent string literals are concatenated by the compiler: const char *text = “This text is pretty long, but will be ” “concatenated into just a single string. ” “The disadvantage is that you have to quote ” “each part, and newlines must … Read more
The C++ Standard does not say where string literals should be stored. It does however guarantee that their lifetime is the lifetime of the program. Your code is therefore valid.
[Note: Originally, this was not meant to be a self-answered question; I just happened to find the answer myself while I was describing my attempts to investigate, and I thought it would have been nice to share it.] According to Annex C (2.14.5) of the C++11 Standard: The type of a string literal is changed … Read more