Fix regexp character classes with \uNNNN and \xNN code points
Currently, if a regexp contains a character class and that character class contains a hex-specified code point -- either \uNNNN or \xNN --, then the character 'u' or 'x' is added to the character class as well. This patch fixes the error and also adds a regression test covering the issue. Fixes #962 JerryScript-DCO-1.0-Signed-off-by: Akos Kiss akiss@inf.u-szeged.hu
This commit is contained in:
@@ -421,6 +421,7 @@ re_parse_char_class (re_parser_ctx_t *parser_ctx_p, /**< number of classes */
|
||||
|
||||
parser_ctx_p->input_curr_p += 2;
|
||||
append_char_class (re_ctx_p, code_unit, code_unit);
|
||||
ch = LIT_CHAR_UNDEF;
|
||||
}
|
||||
else if (ch == LIT_CHAR_LOWERCASE_U)
|
||||
{
|
||||
@@ -433,6 +434,7 @@ re_parse_char_class (re_parser_ctx_t *parser_ctx_p, /**< number of classes */
|
||||
|
||||
parser_ctx_p->input_curr_p += 4;
|
||||
append_char_class (re_ctx_p, code_unit, code_unit);
|
||||
ch = LIT_CHAR_UNDEF;
|
||||
}
|
||||
else if (ch == LIT_CHAR_LOWERCASE_D)
|
||||
{
|
||||
|
||||
Reference in New Issue
Block a user