A little bit of constexpr, sprinkled with some TMP and a topping of indices gives me this: #include <array> template<unsigned… Is> struct seq{}; template<unsigned N, unsigned… Is> struct gen_seq : gen_seq<N-1, N-1, Is…>{}; template<unsigned… Is> struct gen_seq<0, Is…> : seq<Is…>{}; template<unsigned N1, unsigned… I1, unsigned N2, unsigned… I2> constexpr std::array<char const, N1+N2-1> concat(char const (&a1)[N1], … Read more
you can use always: ‘C:/mydir’ this works both in linux and windows. Other posibility is ‘C:\\mydir’ if you have problems with some names you can also try raw string literals: r’C:\mydir’ however best practice is to use the os.path module functions that always select the correct configuration for your OS: os.path.join(mydir, myfile) From python 3.4 … Read more
A string consists of a quote mark ” followed by zero or more of either an escaped anything \\. or a non-quote character, non-backslash character [^”\\] and finally a terminating quote ” Put it all together, and you’ve got \”(\\.|[^”\\])*\” The delimiting quotes are escaped because they are Flex meta-characters.
Sure, it’s the easy way to make your code look good: char *someGlobalString = “very long ” “so broken ” “onto multiple ” “lines”; The best reason, though, is for weird printf formats, like type forcing: uint64_t num = 5; printf(“Here is a number: %”PRIX64″, what do you think of that?”, num); There are a … Read more
Check the documentation for strcmp. Hint: it doesn’t return a boolean value. ETA: == doesn’t work in general because cstr1 == cstr2 compares pointers, so that comparison will only be true if cstr1 and cstr2 point to the same memory location, even if they happen to both refer to strings that are lexicographically equal. What … Read more
The presented code snippet does not change the string literals themselves. It only changes the values stored in the pointer fruit. You can imagine these lines char* fruit = “banana”; fruit = “apple”; the following way char unnamed_static_array_banana[] = { ‘b’, ‘a’, ‘n’, ‘a’, ‘n’, ‘a’, ‘\0’ }; char *fruit = &unnamed_static_array_banana[0]; char unnamed_static_array_apple[] = … Read more
Your compiler ultimately operates on things called translation units, informally called source files. Within these translation units, you identify different entities: objects, functions, etc. The linkers job is to connect these units together, and part of that process is merging identities. Identifiers have linkage†: internal linkage means that the entity named in that translation unit … Read more
Initializing a char array with a string literal that is larger than it is fine in C, but wrong in C++. That explains the difference in behavior between gcc and VC++. You would get no error if you compiled the same as a C file with VC++. And you would get an error if you … Read more
Lifetime elision infers that the full type of fn get_str(s: &str) -> &str is fn get_str<‘a>(s: &’a str) -> &’a str which basically means that the return value of get_str has to be valid as long as s is valid. The actual type of the string literal “Hello world” is &’static str, which means that … Read more
The C/C++ preprocessor acts in units of tokens, and a string literal is a single token. As such, you can’t intervene in the middle of a string literal like that. You could preprocess script.py into something like: “some code\n” “some more code that will be appended\n” and #include that, however. Or you can use xxd … Read more