GCC_TREAT_WARNINGS_AS_ERRORS = YES
WARNING_CFLAGS = -Wall
GCC_WARN_CHECK_SWITCH_STATEMENTS = YES
GCC_WARN_EFFECTIVE_CPLUSPLUS_VIOLATIONS = YES
GCC_WARN_FOUR_CHARACTER_CONSTANTS = YES
GCC_WARN_SHADOW = YES
GCC_WARN_INITIALIZER_NOT_FULLY_BRACKETED = YES
GCC_WARN_ABOUT_RETURN_TYPE = YES
GCC_WARN_MISSING_PARENTHESES = YES
GCC_WARN_ABOUT_MISSING_FIELD_INITIALIZERS = YES
GCC_WARN_ABOUT_MISSING_PROTOTYPES = YES
GCC_WARN_NON_VIRTUAL_DESTRUCTOR = YES
GCC_WARN_HIDDEN_VIRTUAL_FUNCTIONS = YES
GCC_WARN_SIGN_COMPARE = YES
GCC_TREAT_IMPLICIT_FUNCTION_DECLARATIONS_AS_ERRORS = YES
GCC_TREAT_NONCONFORMANT_CODE_ERRORS_AS_WARNINGS = YES
GCC_WARN_UNDECLARED_SELECTOR = YES
GCC_WARN_UNKNOWN_PRAGMAS = YES
GCC_WARN_UNUSED_FUNCTION = YES
GCC_WARN_UNUSED_LABEL = YES
GCC_WARN_UNUSED_PARAMETER = YES
GCC_WARN_UNUSED_VALUE = YES
GCC_WARN_UNUSED_VARIABLE = YES
GCC_WARN_ABOUT_MISSING_NEWLINE = YES
GCC_WARN_TYPECHECK_CALLS_TO_PRINTF = YES
GCC_WARN_ABOUT_DEPRECATED_FUNCTIONS = YES
GCC_WARN_ABOUT_INVALID_OFFSETOF_MACRO = YES
GCC_WARN_STRICT_SELECTOR_MATCH = YES
GCC_WARN_64_TO_32_BIT_CONVERSION = YES
RUN_CLANG_STATIC_ANALYZER = YES
Aaron
On Feb 26, 2012, at 3:06 PM, Quincey Morris wrote:
On Feb 26, 2012, at 14:32 , Eeyore wrote:
I couldn't find anything "interesting" or weird about the language use at the places where coloring cuts out. Often just deleting a semi-colon and then retyping it will cause coloring to extend or disappear. I'll keep trying to figure out if there is a pattern.
FWIW, pattern-wise, I've noticed:
1. Coloring may disappear (for part or all of the file) while background source code indexing is in progress. Generally it comes back when the indexing completes, but this might take a while depending on what is being re-indexed.
2. Occasionally (and randomly from the user's perspective AFAIK), coloring won't come back on in an unsaved file, but comes back when you save the file. (But you've seen a variation where it doesn't come back after the save. Perhaps the save and the indexing are both background operations, and it matters which one happens to finish first.)
3. A structural error (like a missing ']' or '}' later in a method often turns off coloring from some point of editing** earlier in the method, and coloring of the intermediate source (between the edit and the later error) won't come back on until you fix the structural error, even though the intermediate code is free of errors. In addition, completions don't work fully on the intermediate section of code -- e.g. you can get some word/identifier completions to pop up, but not methods -- but I haven't taken the time to investigate this systematically.
4. An error in a header file included much earlier can cause symptoms like #3. The place where coloring disappears isn't related to the position of the #import, but perhaps is related to where you make edits**.
5. If there are multiple errors in a different file, enough to cause Xcode to stop trying to finish compilation of that file (sometimes there's a message saying so), then syntax coloring might not come back in the file you're editing, again producing symptoms like #3.
6. When there are errors, in the same or another file, it might make a difference to the return of coloring whether the errors are "live" or the "sticky" kind of errors you get when you do a build.
** It may have to be a point of editing that actually caused its own error to show up, even if you subsequently fix that error. I can't remember for sure.