Fix usage of NULL in integer contexts.
Review URL: http://codereview.chromium.org/5195002 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5856 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
This commit is contained in:
parent
ecf0d85a8e
commit
ed40f93696
@ -720,7 +720,7 @@ Statement PreParser<Scanner, Log>::ParseThrowStatement(bool* ok) {
|
||||
ReportMessageAt(pos.beg_pos, pos.end_pos,
|
||||
"newline_after_throw", NULL);
|
||||
*ok = false;
|
||||
return NULL;
|
||||
return kUnknownStatement;
|
||||
}
|
||||
ParseExpression(true, CHECK_OK);
|
||||
ExpectSemicolon(CHECK_OK);
|
||||
@ -1006,7 +1006,7 @@ Expression PreParser<Scanner, Log>::ParseMemberWithNewPrefixesExpression(
|
||||
// ('[' Expression ']' | '.' Identifier | Arguments)*
|
||||
|
||||
// Parse the initial primary or function expression.
|
||||
Expression result = NULL;
|
||||
Expression result = kUnknownExpression;
|
||||
if (peek() == i::Token::FUNCTION) {
|
||||
Consume(i::Token::FUNCTION);
|
||||
if (peek() == i::Token::IDENTIFIER) {
|
||||
|
Loading…
Reference in New Issue
Block a user