Bug 163330
Summary: | can't support the "egrep" pattern such as "word\W" | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | han pingtian <hanpingtian> |
Component: | cscope | Assignee: | Frank Ch. Eigler <fche> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-20 20:45:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
han pingtian
2005-07-15 06:40:13 UTC
It turns out there are many versions of egrep. cscope contains its own little egrep implementation, probably pulled out of an older SystemV UNIX, which predates some modern constructs. Operators like [:alnum:] or \w were not supported in this version. I expect that cscope screen's reference to "egrep" was meant more to indicate that a wider class of regexps are supported than plain grep: alternation, repetition, and so on. I hope this explains (my guess at) the reasons for the problem. Extending cscope's egrep engine is probably not practical. I can't think of a different term to put on the user interface that doesn't suffer from this ambiguity. I think we'll have to live with this problem. |