[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #62705] Some regex patterns are incorrectly tr
From: |
Markus Mützel |
Subject: |
[Octave-bug-tracker] [bug #62705] Some regex patterns are incorrectly treated as named expressions |
Date: |
Mon, 4 Jul 2022 15:31:04 -0400 (EDT) |
URL:
<https://savannah.gnu.org/bugs/?62705>
Summary: Some regex patterns are incorrectly treated as named
expressions
Project: GNU Octave
Submitter: mmuetzel
Submitted: Mon 04 Jul 2022 09:31:01 PM CEST
Category: Octave Function
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Incorrect Result
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Release: dev
Discussion Lock: Any
Operating System: Any
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: Mon 04 Jul 2022 09:31:01 PM CEST By: Markus Mützel <mmuetzel>
The following patterns are incorrectly classified as named expressions by
Octave. Named expressions are transformed to PCRE syntax. This leads to the
(incorrectly classified) patterns to not match where they should:
regexpi ('<', '\(?<')
regexpi ('<n>', '\(?<n\>')
regexpi ('<n>', '\(?<n\>\)?')
regexpi ('<n>a', '\(?<n\>a\)?')
IIUC, all of these should return `1`. But they return `[]` (or crash or emit
an error before the fix for bug #62704).
I have a fix for some of those ready that I'll push when I have a bug number.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62705>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #62705] Some regex patterns are incorrectly treated as named expressions,
Markus Mützel <=