bc: Vendor import new version 3.3.3

(cherry picked from commit 028616d0dd69a3da7a30cb94d35f040bf2ced6b9)

Make length(0) and length(0.0) return 1 for compatibility with GNU bc
and the traditional FreeBSD bc.

Fix a potential division by zero error in a non-standard (extended)
math library function.

1 files changed, 26 insertions, 27 deletions

diff --git a/contrib/bc/manuals/dc/HN.1 b/contrib/bc/manuals/dc/HN.1
index 38efef021c64..a617bb473ec1 100644
--- a/contrib/bc/manuals/dc/HN.1
+++ b/contrib/bc/manuals/dc/HN.1
@@ -25,18 +25,17 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.TH "DC" "1" "February 2021" "Gavin D. Howard" "General Commands Manual"
+.TH "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
 .SH Name
 .PP
 dc - arbitrary-precision decimal reverse-Polish notation calculator
 .SH SYNOPSIS
 .PP
-\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]\[en]version\f[R]]
-[\f[B]\[en]help\f[R]] [\f[B]\[en]interactive\f[R]]
-[\f[B]\[en]no-prompt\f[R]] [\f[B]\[en]extended-register\f[R]]
-[\f[B]-e\f[R] \f[I]expr\f[R]]
-[\f[B]\[en]expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R]
-\f[I]file\f[R]\&...] [\f[B]-file\f[R]=\f[I]file\f[R]\&...]
+\f[B]dc\f[R] [\f[B]-hiPvVx\f[R]] [\f[B]--version\f[R]]
+[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--no-prompt\f[R]]
+[\f[B]--extended-register\f[R]] [\f[B]-e\f[R] \f[I]expr\f[R]]
+[\f[B]--expression\f[R]=\f[I]expr\f[R]\&...] [\f[B]-f\f[R]
+\f[I]file\f[R]\&...] [\f[B]--file\f[R]=\f[I]file\f[R]\&...]
 [\f[I]file\f[R]\&...]
 .SH DESCRIPTION
 .PP
@@ -47,13 +46,13 @@ Arithmetic operations pop arguments off of the stack and push the
 results.
 .PP
 If no files are given on the command-line as extra arguments (i.e., not
-as \f[B]-f\f[R] or \f[B]\[en]file\f[R] arguments), then dc(1) reads from
+as \f[B]-f\f[R] or \f[B]--file\f[R] arguments), then dc(1) reads from
 \f[B]stdin\f[R].
 Otherwise, those files are processed, and dc(1) will then exit.
 .PP
 This is different from the dc(1) on OpenBSD and possibly other dc(1)
-implementations, where \f[B]-e\f[R] (\f[B]\[en]expression\f[R]) and
-\f[B]-f\f[R] (\f[B]\[en]file\f[R]) arguments cause dc(1) to execute them
+implementations, where \f[B]-e\f[R] (\f[B]--expression\f[R]) and
+\f[B]-f\f[R] (\f[B]--file\f[R]) arguments cause dc(1) to execute them
 and exit.
 The reason for this is that this dc(1) allows users to set arguments in
 the environment variable \f[B]DC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT
@@ -72,13 +71,13 @@ argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
 .PP
 The following are the options that dc(1) accepts.
 .TP
-\f[B]-h\f[R], \f[B]\[en]help\f[R]
+\f[B]-h\f[R], \f[B]--help\f[R]
 Prints a usage message and quits.
 .TP
-\f[B]-v\f[R], \f[B]-V\f[R], \f[B]\[en]version\f[R]
+\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
 Print the version information (copyright header) and exit.
 .TP
-\f[B]-i\f[R], \f[B]\[en]interactive\f[R]
+\f[B]-i\f[R], \f[B]--interactive\f[R]
 Forces interactive mode.
 (See the \f[B]INTERACTIVE MODE\f[R] section.)
 .RS
@@ -86,7 +85,7 @@ Forces interactive mode.
 This is a \f[B]non-portable extension\f[R].
 .RE
 .TP
-\f[B]-P\f[R], \f[B]\[en]no-prompt\f[R]
+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
 Disables the prompt in TTY mode.
 (The prompt is only enabled in TTY mode.
 See the \f[B]TTY MODE\f[R] section) This is mostly for those users that
@@ -98,7 +97,7 @@ Most of those users would want to put this option in
 This is a \f[B]non-portable extension\f[R].
 .RE
 .TP
-\f[B]-x\f[R] \f[B]\[en]extended-register\f[R]
+\f[B]-x\f[R] \f[B]--extended-register\f[R]
 Enables extended register mode.
 See the \f[I]Extended Register Mode\f[R] subsection of the
 \f[B]REGISTERS\f[R] section for more information.
@@ -107,7 +106,7 @@ See the \f[I]Extended Register Mode\f[R] subsection of the
 This is a \f[B]non-portable extension\f[R].
 .RE
 .TP
-\f[B]-e\f[R] \f[I]expr\f[R], \f[B]\[en]expression\f[R]=\f[I]expr\f[R]
+\f[B]-e\f[R] \f[I]expr\f[R], \f[B]--expression\f[R]=\f[I]expr\f[R]
 Evaluates \f[I]expr\f[R].
 If multiple expressions are given, they are evaluated in order.
 If files are given as well (see below), the expressions and files are
@@ -120,17 +119,17 @@ If this option is given on the command-line (i.e., not in
 \f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
 then after processing all expressions and files, dc(1) will exit, unless
 \f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
-\f[B]-f\f[R] or \f[B]\[en]file\f[R], whether on the command-line or in
+\f[B]-f\f[R] or \f[B]--file\f[R], whether on the command-line or in
 \f[B]DC_ENV_ARGS\f[R].
-However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
-\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
+However, if any other \f[B]-e\f[R], \f[B]--expression\f[R],
+\f[B]-f\f[R], or \f[B]--file\f[R] arguments are given after
 \f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
 exit.
 .PP
 This is a \f[B]non-portable extension\f[R].
 .RE
 .TP
-\f[B]-f\f[R] \f[I]file\f[R], \f[B]\[en]file\f[R]=\f[I]file\f[R]
+\f[B]-f\f[R] \f[I]file\f[R], \f[B]--file\f[R]=\f[I]file\f[R]
 Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
 were read through \f[B]stdin\f[R].
 If expressions are also given (see above), the expressions are evaluated
@@ -141,9 +140,9 @@ If this option is given on the command-line (i.e., not in
 \f[B]DC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
 then after processing all expressions and files, dc(1) will exit, unless
 \f[B]-\f[R] (\f[B]stdin\f[R]) was given as an argument at least once to
-\f[B]-f\f[R] or \f[B]\[en]file\f[R].
-However, if any other \f[B]-e\f[R], \f[B]\[en]expression\f[R],
-\f[B]-f\f[R], or \f[B]\[en]file\f[R] arguments are given after
+\f[B]-f\f[R] or \f[B]--file\f[R].
+However, if any other \f[B]-e\f[R], \f[B]--expression\f[R],
+\f[B]-f\f[R], or \f[B]--file\f[R] arguments are given after
 \f[B]-f-\f[R] or equivalent is given, dc(1) will give a fatal error and
 exit.
 .PP
@@ -1037,7 +1036,7 @@ Unlike most other dc(1) implentations, this dc(1) provides nearly
 unlimited amounts of registers, if extended register mode is enabled.
 .PP
 If extended register mode is enabled (\f[B]-x\f[R] or
-\f[B]\[en]extended-register\f[R] command-line arguments are given), then
+\f[B]--extended-register\f[R] command-line arguments are given), then
 normal single character registers are used \f[I]unless\f[R] the
 character immediately following a command that needs a register name is
 a space (according to \f[B]isspace()\f[R]) and not a newline
@@ -1260,17 +1259,17 @@ interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
 dc(1) resets its state (see the \f[B]RESET\f[R] section) and accepts
 more input when one of those errors occurs in interactive mode.
 This is also the case when interactive mode is forced by the
-\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option.
+\f[B]-i\f[R] flag or \f[B]--interactive\f[R] option.
 .PP
 These exit statuses allow dc(1) to be used in shell scripting with error
 checking, and its normal behavior can be forced by using the
-\f[B]-i\f[R] flag or \f[B]\[en]interactive\f[R] option.
+\f[B]-i\f[R] flag or \f[B]--interactive\f[R] option.
 .SH INTERACTIVE MODE
 .PP
 Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
 Interactive mode is turned on automatically when both \f[B]stdin\f[R]
 and \f[B]stdout\f[R] are hooked to a terminal, but the \f[B]-i\f[R] flag
-and \f[B]\[en]interactive\f[R] option can turn it on in other cases.
+and \f[B]--interactive\f[R] option can turn it on in other cases.
 .PP
 In interactive mode, dc(1) attempts to recover from errors (see the
 \f[B]RESET\f[R] section), and in normal execution, flushes