Avoid choking when regexp ranges can span invalid Ichars, charset_mule
src/ChangeLog addition: 2025-03-06 Aidan Kehoe <kehoea@parhasard.net> * regex.c (compile_extended_range): If THIS_CHAR is not a valid Ichar, don't look it up in the translation table, avoiding crashes with error checking when invalid characters are within the range specified. Do include them in the range table, which will allow coalescing ranges that would otherwise not be. lisp/ChangeLog addition: 2025-03-06 Aidan Kehoe <kehoea@parhasard.net> * unicode.el: Move some code that tested unicode-error-default-translation-table and unicode-invalid-sequence-regexp-range to ../tests/automated/regexp-tests.el. tests/ChangeLog addition: 2025-03-06 Aidan Kehoe <kehoea@parhasard.net> * automated/regexp-tests.el: Move some code to test unicode-error-default-translation-table, unicode-invalid-sequence-regexp-range here from lisp/unicode.el.
Showing
- lisp/ChangeLog 7 additions, 0 deletionslisp/ChangeLog
- lisp/unicode.el 0 additions, 27 deletionslisp/unicode.el
- src/ChangeLog 9 additions, 0 deletionssrc/ChangeLog
- src/regex.c 31 additions, 1 deletionsrc/regex.c
- tests/ChangeLog 6 additions, 0 deletionstests/ChangeLog
- tests/automated/regexp-tests.el 46 additions, 0 deletionstests/automated/regexp-tests.el
Loading
Please register or sign in to comment