null-terminated

I sort of assumed that range based for loops would support C-style strings void print_C_str(const char* str) { for(char c : str) { cout << c; } } However this is not the case, the standard [stmt.ranged] (6.5.4) says that range-based-for works in one of 3 possibilities: The range is an array The range is a class with a callable begin and end method There is ADL reachable in an associated namespace (plus the std namespace) When I add begin and end functions for const char* in the global namespace I still get errors (from both VS12 and GCC 4.7). Is there a way to get range-based-for loops to work

Update turns out this is just another case of "c++ is not c blues" What I want const char hex[16] = "0123456789ABCDEF"; the only thing that works char hex[16] = "0123456789ABCDE"; hex[15] = "F"; are there any compiler options or something I can do to make strings not null terminated in the gcc compiler. so that I can make a(n) constant array No need for a compiler option, it's already non-NUL terminated. The standard says a NUL should only be added if it can fit, otherwise it would be an overflow. It may just be that the next byte in memory past your array is \0 § 6.7.8p14 An array of

How do I do the in-place equivalent of strstr() for a counted string (i.e. not null-terminated) in C? If you're afraid of O(m*n) behaviour - basically, you needn't, such cases don't occur naturally - here's a KMP implementation I had lying around which I've modified to take the length of the haystack. Also a wrapper. If you want to do repeated searches, write your own and reuse the borders array. No guarantees for bug-freeness, but it seems to still work. int *kmp_borders(char *needle, size_t nlen){ if (!needle) return NULL; int i, j, *borders = malloc((nlen+1)*sizeof(*borders)); if (!borders)

In C, when I initialize my array this way: char full_name[] = { 't', 'o', 'a', 'n' }; and print it with printf("%s", full_name); and run it with valgrind I got error Uninitialised value was create by stack allocation Why do that happen? Since %s format specifier expects a null-terminated string, the resulting behavior of your code is undefined. Your program is considered ill-formed, and can produce any output at all, produce no output, crash, and so on. To put this shortly, don't do that. This is not to say that all arrays of characters must be null-terminated: the rule applies only to arrays

So I'm wondering if command line parameters are always null terminated? Google seems to say yes, and compiling on GCC indicates this is the case, but can I guarantee this to always be true? int main(int argc, char** argv) { char *p; for(int cnt=1; cnt < argc; ++cnt) { p = argv[cnt]; printf("%d = [%s]\n", cnt, p); } return 0; } $ MyProgram -arg1 -arg2 -arg3 1 = -arg1 2 = -arg2 3 = -arg3 James McNellis Yes. The non-null pointers in the argv array point to C strings, which are by definition null terminated. The C Language Standard simply states that the array members "shall contain pointers to

Probably I'm just too dump for googling, but I always thought char arrays get only null terminated by an literal initialization ( char x[]="asdf"; ) and got a bit surprised when I saw that this seems not to be the case. int main() { char x[2]; printf("%d", x[2]); return 0; } Output: 0 Shouldn't an array declared as size=2*char actually get the size of 2 chars? Or am I doing something wrong here? I mean it isn't uncommon to use a char array as a simple char array and not as a string, or is it? You are accessing an uninitialized array outside its bounds. That's double undefined behavior ,