Ignore:
Timestamp:
Jun 17, 2014, 3:29:56 PM (11 years ago)
Author:
[email protected]
Message:

Fix error messages for incorrect hex literals
https://bugs.webkit.org/show_bug.cgi?id=133998

Reviewed by Mark Lam.

Source/JavaScriptCore:
Ensure that the error messages for bogus hex literals actually
make sense.

  • parser/Lexer.cpp:

(JSC::Lexer<T>::lex):

  • parser/ParserTokens.h:

LayoutTests:
Update tests for sane error messages.

  • sputnik/Conformance/07_Lexical_Conventions/7.8_Literals/7.8.3_Numeric_Literals/S7.8.3_A6.1_T1-expected.txt:
  • sputnik/Conformance/07_Lexical_Conventions/7.8_Literals/7.8.3_Numeric_Literals/S7.8.3_A6.1_T2-expected.txt:
  • sputnik/Conformance/07_Lexical_Conventions/7.8_Literals/7.8.3_Numeric_Literals/S7.8.3_A6.2_T1-expected.txt:
  • sputnik/Conformance/07_Lexical_Conventions/7.8_Literals/7.8.3_Numeric_Literals/S7.8.3_A6.2_T2-expected.txt:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/Source/JavaScriptCore/parser/ParserTokens.h

    r163960 r170079  
    150150    UNTERMINATED_STRING_LITERAL_ERRORTOK = 8 | ErrorTokenFlag | UnterminatedErrorTokenFlag,
    151151    INVALID_STRING_LITERAL_ERRORTOK = 9 | ErrorTokenFlag,
    152     INVALID_PRIVATE_NAME_ERRORTOK = 10 | ErrorTokenFlag
     152    INVALID_PRIVATE_NAME_ERRORTOK = 10 | ErrorTokenFlag,
     153    INVALID_HEX_NUMBER_ERRORTOK = 11 | ErrorTokenFlag
    153154};
    154155
Note: See TracChangeset for help on using the changeset viewer.