py: Clarify comment in parsenum.c about ValueError vs SyntaxError.

This commit is contained in:
Damien George 2015-06-23 16:08:51 +00:00
parent 228c68a9cd
commit 2a1090a637
1 changed files with 2 additions and 2 deletions

View File

@ -36,7 +36,8 @@
#endif
STATIC NORETURN void raise_exc(mp_obj_t exc, mp_lexer_t *lex) {
// if lex!=NULL then the parser called us and we need to make a SyntaxError with traceback
// if lex!=NULL then the parser called us and we need to convert the
// exception's type from ValueError to SyntaxError and add traceback info
if (lex != NULL) {
((mp_obj_base_t*)exc)->type = &mp_type_SyntaxError;
mp_obj_exception_add_traceback(exc, lex->source_name, lex->tok_line, MP_QSTR_NULL);
@ -142,7 +143,6 @@ overflow:
}
value_error:
// if lex!=NULL then the parser called us and we need to make a ValueError with traceback
if (MICROPY_ERROR_REPORTING == MICROPY_ERROR_REPORTING_TERSE) {
mp_obj_t exc = mp_obj_new_exception_msg(&mp_type_ValueError,
"invalid syntax for integer");