src/bin/expr/expr.1, branch release/9.0.0FreeBSD source treehttps://cgit-dev.freebsd.org/src/atom?h=release%2F9.0.02011-07-09T12:05:53ZMake /bin/expr support 64bit numeric range and range checks by default,2011-07-09T12:05:53ZStefan Eßerse@FreeBSD.org2011-07-09T12:05:53Zurn:sha1:fa717604a42dff3416a3e299da0abf01d9f8521e
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:53ZJilles Tjoelkerjilles@FreeBSD.org2010-09-09T21:59:53Zurn:sha1:f390d8d927e2bc6a8afd086bfdcdbf5edcbc6875
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
Fix markup.2007-03-04T19:52:07ZRuslan Ermilovru@FreeBSD.org2007-03-04T19:52:07Zurn:sha1:9f3cef91087c68f23d917212fc7b88e7c266feefAdd the new standard EXIT STATUS section where appropriate.2005-01-16T16:41:59ZRuslan Ermilovru@FreeBSD.org2005-01-16T16:41:59Zurn:sha1:6fca4c7c3f16b87ad8b9ffa6564f5654f44ed581
Sort standard sections in the (documented) preferred order.
Removed harmful empty lines that crept in during the copyright2005-01-13T08:46:19ZRuslan Ermilovru@FreeBSD.org2005-01-13T08:46:19Zurn:sha1:5f05dfac3226e634a49596250afd5b9ecc885e1d
header update.
/*- or .\"- or #- to begin license clauses.2005-01-10T08:39:26ZWarner Loshimp@FreeBSD.org2005-01-10T08:39:26Zurn:sha1:9ddb49cbe45441fa3f3a10f6dd355e9956480b5fRemove BUGS section that talked about missing multibyte character support.2004-07-12T10:46:55ZTim J. Robbinstjr@FreeBSD.org2004-07-12T10:46:55Zurn:sha1:5292d2aec0d20a8bda87f5d518c040370bb7fc8a
We have support now that the regular expression routines do.
Document missing multibyte character handling in utilities specified2004-07-03T02:03:44ZTim J. Robbinstjr@FreeBSD.org2004-07-03T02:03:44Zurn:sha1:128dc4a2e367eb9a66d26898531004140428b285
by POSIX.
mdoc(7) police:2002-11-26T17:55:41ZRuslan Ermilovru@FreeBSD.org2002-11-26T17:55:41Zurn:sha1:e27480d64d80d828ffd89ae068774389a3c2c764
Revert to using the .Tn POSIX and .Tn ANSI instead of \*[Px] and \*[Ai]
strings; using these strings is unsafe in troff mode, as they include a
change in a font size.
Approved by: re
mdoc(7) police: markup fixes.2002-11-25T13:20:30ZRuslan Ermilovru@FreeBSD.org2002-11-25T13:20:30Zurn:sha1:98d13c7e51ccd70ee88c3c55a587c7fc8157a972
Approved by: re