Of course, you could also use const char *r[] = ... and completely avoid the problem of using an array size.
--
Mats
Of course, you could also use const char *r[] = ... and completely avoid the problem of using an array size.
--
Mats
Compilers can produce warnings - make the compiler programmers happy: Use them!
Please don't PM me for help - and no, I don't do help over instant messengers.
I could, except arrays of pointers still confuse me lol, I know how they work, but find it difficult to think about when programming logic with them.
On the issue of oversizing arrays slightly when declaring them, sometimes that can be an issue, for instance in a program Im doing which returns the max, min, median, mode, ect from a set of data if you make the array too big the extra elements will either contain some trash integer (probably large) which throws the max function out, or if you initialize them all to 0 then it ruins the min function. Leaving the size unspecified is probably a good idea, like iMalc suggested.
