Bug 63971 - Don't parse the valid QRegExp " a(|b)c"
Summary: Don't parse the valid QRegExp " a(|b)c"
Status: CLOSED FIXED
Alias: None
Product: kregexpeditor
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Jesper Pedersen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-09 18:17 UTC by Pascal Létourneau
Modified: 2003-09-30 22:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Létourneau 2003-09-09 18:17:14 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources

KRegExpEditor don't parse the valid QRegExp "a(|b)c"
Comment 1 Jesper Pedersen 2003-09-10 09:53:48 UTC 
Subject: Re:  New: Don't parse the valid QRegExp " a(|b)c"

Which syntax are you referring to?
In Qt's syntax which is the default from within KDE application, the
following is actually a invalid syntax.
a(x|b)c would be a valid one
a(\|b)c would also be valid
but not the one you write.

Pascal "L
Comment 2 Pascal Létourneau 2003-09-10 17:46:02 UTC 
It is a valid regexp in Qt, python, perl, ... Just try it!
Comment 3 Jesper Pedersen 2003-09-27 16:17:17 UTC 
Thanks, you were right. This is valid syntax, and have now been fixed on HEAD.
Comment 4 Pascal Létourneau 2003-09-30 19:34:48 UTC 
There is still a small problem with the graph for "a(|b)c".
It shows only one alternative: "b".
It should show two: "" and "b".
Comment 5 Jesper Pedersen 2003-09-30 21:56:11 UTC 
Regular expression are not quite simple are they. Until just now, I didn't understand 
why you were that interested in that sily regexp. I though it was equal to a(b)c, 
which it of course isn't. 
 
Now empty lineedit are created. 
Thanks for bugging me till I finally understood. 
Jesper.
Comment 6 Pascal Létourneau 2003-09-30 22:19:08 UTC 
Thanks!