- Remove unneeded consecutive argument in `.Nm' macros;

- rename `GRAMMAR AMBIGUITY' section to `CAVEATS', and move it to
  correct location;
- bump date.

From Bug Hunting.
This commit is contained in:
wiz 2012-12-16 17:57:49 +00:00
parent 1b59d35cc3
commit dbb168824f
1 changed files with 18 additions and 18 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: test.1,v 1.27 2009/11/10 18:19:46 wiz Exp $
.\" $NetBSD: test.1,v 1.28 2012/12/16 17:57:49 wiz Exp $
.\"
.\" Copyright (c) 1991, 1993
.\" The Regents of the University of California. All rights reserved.
@ -32,7 +32,7 @@
.\"
.\" @(#)test.1 8.1 (Berkeley) 5/31/93
.\"
.Dd November 10, 2009
.Dd December 16, 2012
.Dt TEST 1
.Os
.Sh NAME
@ -40,13 +40,13 @@
.Nm \&[
.Nd condition evaluation utility
.Sh SYNOPSIS
.Nm test
.Nm
.Ar expression
.Nm \&[
.Ar expression Cm \&]
.Sh DESCRIPTION
The
.Nm test
.Nm
utility evaluates
.Ar expression
and, if it evaluates
@ -55,12 +55,12 @@ it returns 1 (false).
If
.Ar expression
is not given,
.Nm test
.Nm
also
returns 1 (false).
.Pp
All operators and flags are separate arguments to the
.Nm test
.Nm
utility.
.Pp
The following primaries are used to construct
@ -293,19 +293,9 @@ Note that all file tests with the exception of
and
.Fl L
follow symbolic links and thus evaluate the test for the file pointed at.
.Sh GRAMMAR AMBIGUITY
The
.Nm test
grammar is inherently ambiguous.
In order to assure a degree of consistency, the cases described in
.St -p1003.2
section 4.62.4,
are evaluated consistently according to the rules specified in the
standards document.
All other cases are subject to the ambiguity in the command semantics.
.Sh EXIT STATUS
The
.Nm test
.Nm
utility exits with one of the following values:
.Bl -tag -width Ds
.It 0
@ -319,7 +309,17 @@ An error occurred.
.El
.Sh STANDARDS
The
.Nm test
.Nm
utility implements a superset of the
.St -p1003.2
specification.
.Sh CAVEATS
The
.Nm
grammar is inherently ambiguous.
In order to assure a degree of consistency, the cases described in
.St -p1003.2
section 4.62.4,
are evaluated consistently according to the rules specified in the
standards document.
All other cases are subject to the ambiguity in the command semantics.