BSD 4_4_Lite1 release

[unix-history] / usr / src / lib / libc / regex / re_format.7

diff --git a/usr/src/lib/libc/regex/re_format.7 b/usr/src/lib/libc/regex/re_format.7
index 7e62b7f..db2f634 100644 (file)
--- a/usr/src/lib/libc/regex/re_format.7
+++ b/usr/src/lib/libc/regex/re_format.7
@@ -1,15 +1,41 @@
-.\" Copyright (c) 1992 Henry Spencer.
-.\" Copyright (c) 1992 The Regents of the University of California.
-.\" All rights reserved.
+.\" Copyright (c) 1992, 1993, 1994 Henry Spencer.
+.\" Copyright (c) 1992, 1993, 1994
+.\"    The Regents of the University of California.  All rights reserved.

 .\"
 .\" This code is derived from software contributed to Berkeley by
 .\"
 .\" This code is derived from software contributed to Berkeley by

-.\" Henry Spencer of the University of Toronto.
+.\" Henry Spencer.

 .\"
 .\"

-.\" %sccs.include.redist.roff%
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.

 .\"
 .\"

-.\"    @(#)re_format.7 5.2 (Berkeley) %G%
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.

 .\"
 .\"

-.TH RE_FORMAT 7 ""
+.\"    @(#)re_format.7 8.3 (Berkeley) 3/20/94
+.\"
+.TH RE_FORMAT 7 "March 20, 1994"

 .SH NAME
 re_format \- POSIX 1003.2 regular expressions
 .SH DESCRIPTION
 .SH NAME
 re_format \- POSIX 1003.2 regular expressions
 .SH DESCRIPTION


@@ -143,12 +169,14 @@ There are two special cases\(dg of bracket expressions:
 the bracket expressions `[[:<:]]' and `[[:>:]]' match the null string at
 the beginning and end of a word respectively.
 A word is defined as a sequence of
 the bracket expressions `[[:<:]]' and `[[:>:]]' match the null string at
 the beginning and end of a word respectively.
 A word is defined as a sequence of

-.I alnum
-characters (as defined by
-.IR ctype (3))
+word characters

 which is neither preceded nor followed by
 which is neither preceded nor followed by

+word characters.
+A word character is an

 .I alnum
 .I alnum

-characters.
+character (as defined by
+.IR ctype (3))
+or an underscore.

 This is an extension,
 compatible with but not specified by POSIX 1003.2,
 and should be used with
 This is an extension,
 compatible with but not specified by POSIX 1003.2,
 and should be used with


@@ -237,3 +265,5 @@ Avoid using them.
 1003.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.
 1003.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
+The syntax for word boundaries is incredibly ugly.