nxstyle: Suppress checking in strings/comments.

nxstyle does not detect when it is within a string and will report crazy things because it is parsing the strng content. For example, if the string contains "Hello", nxstyle would probleam complain about mixed case identifiers, if the strong contains "https://", it would probably complete about C++ style comments. If the string contains "yes/no" it would probably complain about missing spaces before and after an operator.

Below is a even more obsure false alarm example:

junk.c:

/****************************************************************************
* Private Data
****************************************************************************/

static const char g_blabber[] = "Yadda, yadda, yadda, yadda";

/****************************************************************************
* Public Functions
****************************************************************************/

then you see:

$ tools/nxstyle.exe junk.c
junk.c:5:39: error: Multiple data definitions

In this case, nxstyle should ignore the ',' characters is within a string.

Most of this also applies to comments. You will see the same kinds of errors for similer sub-strings within a comment. nxstyle does detect that it is within a comment, however, it does not use that information to suppress certain error reports.

Start with the nxstyle implementation used by tools/nxstyle.exe and reproduce the reported diagnostics with junk.c, including strings and comments containing punctuation or identifier-like text. Trace how the tool identifies strings and comments, then verify that checks are suppressed inside them while normal code is still diagnosed without the listed false alarms.

Written by the indexing model from the issue text.