src/bin/expr, branch releng/10.0

Add the Clang specific -Wmissing-variable-declarations to WARNS=6.

2013-04-19T19:45:00+00:00

This compiler flag enforces that that people either mark variables
static or use an external declarations for the variable, similar to how
-Wmissing-prototypes works for functions.

Due to the fact that Yacc/Lex generate code that cannot trivially be
changed to not warn because of this (lots of yy* variables), add a
NO_WMISSING_VARIABLE_DECLARATIONS that can be used to turn off this
specific compiler warning.

Announced on:	toolchain@

Remove redundant declaration of yyparse

2012-05-22T03:01:54+00:00

Reported by:	tinderbox

Minor mdoc nits.

2012-05-13T14:16:04+00:00

rm[0].rm_so must be zero (an explicit check is made for zero in the

2012-03-19T00:45:01+00:00

outer if condition)

Reviewed by:	se
Approved by:	cperciva

Whitespace cleanup:

2012-02-25T15:21:43+00:00

 o Wrap sentences on to new lines
 o Cleanup trailing whitespace

Found with:	textproc/igor
MFC after:	1 week
X-MFC-With:	r232157

Fix various typos in manual pages.

2012-02-25T14:31:25+00:00

Submitted by:	amdmi3
PR:		165431
MFC after:	1 week

Fix style, since this file has just been touched in a major way.

2011-07-09T12:20:15+00:00

No actual code changes.

Some refactoring for easier maintenance of the code. This is a follow-up

2011-07-09T12:14:57+00:00

to re-establishment of 64bit arithmetic, but is committed separately, to
not obscure that conversion. This commit does not change the observed
behaviour of expr in any way. Style will be fixed in a follow-up commit.

Make /bin/expr support 64bit numeric range and range checks by default,

2011-07-09T12:05:53+00:00

again. This brings back the behaviour of expr in FreeBSD-4, which had been
reverted due to an assumed incompatbility with POSIX.1 for FreeBSD-5.

This issue has been discussed in the freebsd-standards list, and the
consensus was, that POSIX.1 is in fact not violated by this extension,
since it affects only cases of POSIX undefined behaviour (overflow of
signed long).

Other operating systems did upgrade their versions of expr to support
64bit range, after it had been initially brought to FreeBSD. They have
used it for a decade without problems, meanwhile.

The -e option is retained, but it will only select less strict checking
of numeric parameters (leading white-space, leading "+" are allowed and
skipped, an empty string is considered to represent 0 in numeric context.)
The call of check_utility_compat() as a means of establishing backwards
compatibility with FreeBSD-4 is considered obsolete, but preserved in
this commit. It is expected to be removed in a later revision of this
file.
Reviewed by:	bde, das, jilles
MFC after:	2 month (those parts that do not violate POLA)

expr(1): Add sh(1) versions of examples, remove an incorrect example.

2010-09-09T21:59:53+00:00

The three examples are better done using sh(1) itself these days.

The example
  expr -- "$a" : ".*"
is incorrect in the general case, as "$a" may be an operator.

MFC after:	2 weeks