[pcre-dev] [Bug 2362] New: bad_escape_is_literal influences …

https://bugs.exim.org/show_bug.cgi?id=2362

            Bug ID: 2362
           Summary: bad_escape_is_literal influences 'invalid range' check
           Product: PCRE
           Version: 10.32 (PCRE2)
          Hardware: x86
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Code
          Assignee: ph10@???
          Reporter: sjon@???
                CC: pcre-dev@???

when bad_escape_is_literal is specified, certain invalid range checks disappear
- this shouldn't happen. Example:

re> /[^\s-_]/bad_escape_is_literal
Failed: error 150 at offset 4: invalid range in character class

re> /[^_-\s]/bad_escape_is_literal
data>

The second regexp should fail like the first one. This works fine without
bad_escape_is_literal:

re> /[^_-\s]/
Failed: error 150 at offset 6: invalid range in character class

Originally filed as a PHP bug: https://bugs.php.net/bug.php?id=77388

--
You are receiving this mail because:
You are on the CC list for the bug.