On Wed, Feb 04 2015, Christopher Li <sparse@xxxxxxxxxxx> wrote: > On Wed, Feb 4, 2015 at 12:58 AM, Rasmus Villemoes > <linux@xxxxxxxxxxxxxxxxxx> wrote: >> On Wed, Feb 04 2015, Rasmus Villemoes <linux@xxxxxxxxxxxxxxxxxx> wrote: >> >>> And I wasn't hallucinating, I was just overcomplicating things: >>> >>> #define NOT_TAB "\\t" >>> >>> static const char s1[] = NOT_TAB; >>> static const char s2[] = NOT_TAB; >>> >>> indeed fails. >> >> While we're collecting examples, let me also mention that __FILE__ >> doesn't work for files with backslash in their name. Sane people of >> course don't put backslashes in file names, but they are a rather normal >> occurence in path names on a certain operating system. > > Can you submit a patch for adding the test case you found? > I will include those into the the test suit. I'd like to, but I'm not sure how to write the test in terms of sparse's test frame work. How do I check that the string is as expected? Rasmus -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
