Fix handling of Objective-C for...in statements

Without this change, we parse as though the initial declaration is an
uninitialized variable. With this change, we behave the same as we do
for range-based for loops in C++, which is not handled as an
uninitialized variable.

Note, ParseDeclGroup (which is what is eventually called as a result of
this change) was already expecting to be able to handle for...in loops,
so this appears to be fixing an oversight.

Author: AaronBallman

clang/lib/Parse/ParseStmt.cpp

@@ -2154,7 +2154,7 @@ StmtResult Parser::ParseForStatement(SourceLocation *TrailingElseLoc) {
       FirstPart = Actions.ActOnDeclStmt(DG, DeclStart, Tok.getLocation());
     } else {
       // In C++0x, "for (T NS:a" might not be a typo for ::
-      bool MightBeForRangeStmt = getLangOpts().CPlusPlus;
+      bool MightBeForRangeStmt = getLangOpts().CPlusPlus || getLangOpts().ObjC;
       ColonProtectionRAIIObject ColonProtection(*this, MightBeForRangeStmt);
       ParsedAttributes DeclSpecAttrs(AttrFactory);
       DG = ParseSimpleDeclaration(