diff options
| author | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-09-04 09:07:15 +0000 |
|---|---|---|
| committer | Michael Kerrisk <mtk.manpages@gmail.com> | 2006-09-04 09:07:15 +0000 |
| commit | fa203d8506d535eee7163999507ed10a80707626 (patch) | |
| tree | 98e7bc897890ca692d9a445c959e89085ff780f0 /man7/regex.7 | |
| parent | a7422469fd35cb99c2ab77a04360323697d4989e (diff) | |
| download | man-pages-fa203d8506d535eee7163999507ed10a80707626.tar.gz | |
Change references to "1003.2" to "POSIX.2".
Diffstat (limited to 'man7/regex.7')
| -rw-r--r-- | man7/regex.7 | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/man7/regex.7 b/man7/regex.7 index 824a7ce89a..201dfb1748 100644 --- a/man7/regex.7 +++ b/man7/regex.7 @@ -40,15 +40,15 @@ Regular expressions (``RE''s), as defined in POSIX.2, come in two forms: modern REs (roughly those of .IR egrep ; -1003.2 calls these ``extended'' REs) +POSIX.2 calls these ``extended'' REs) and obsolete REs (roughly those of .BR ed (1); -1003.2 ``basic'' REs). +POSIX.2 ``basic'' REs). Obsolete REs mostly exist for backward compatibility in some old programs; they will be discussed at the end. -1003.2 leaves some aspects of RE syntax and semantics open; +POSIX.2 leaves some aspects of RE syntax and semantics open; `\*(dg' marks decisions on these aspects that -may not be fully portable to other 1003.2 implementations. +may not be fully portable to other POSIX.2 implementations. .PP A (modern) RE is one\*(dg or more non-empty\*(dg \fIbranches\fR, separated by `|'. @@ -248,7 +248,7 @@ POSIX.2, section 2.8 (Regular Expression Notation). .SH BUGS Having two kinds of REs is a botch. .PP -The current 1003.2 spec says that `)' is an ordinary character in +The current POSIX.2 spec says that `)' is an ordinary character in the absence of an unmatched `('; this was an unintentional result of a wording error, and change is likely. @@ -261,7 +261,7 @@ They are also somewhat vaguely defined `a\e(\e(b\e)*\e2\e)*d' match `abbbd'?). Avoid using them. .PP -1003.2's specification of case-independent matching is vague. +POSIX.2's specification of case-independent matching is vague. The ``one case implies all cases'' definition given above is current consensus among implementors as to the right interpretation. .PP |