No OneTemporary
Actions

Size

4 MB

Referenced Files

None

Subscribers

None

View Options

This file is larger than 256 KB, so syntax highlighting was skipped.

	diff --git a/contrib/bc/Makefile.in b/contrib/bc/Makefile.in
	index aab7f9b569e5..2b50476a79fe 100644
	--- a/contrib/bc/Makefile.in
	+++ b/contrib/bc/Makefile.in
	@@ -1,445 +1,444 @@
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#
	# %%WARNING%%
	#
	.POSIX:

	-VERSION = 3.3.4
	-
	SRC = %%SRC%%
	OBJ = %%OBJ%%
	GCDA = %%GCDA%%
	GCNO = %%GCNO%%

	BC_ENABLED_NAME = BC_ENABLED
	BC_ENABLED = %%BC_ENABLED%%
	DC_ENABLED_NAME = DC_ENABLED
	DC_ENABLED = %%DC_ENABLED%%

	HEADERS = include/args.h include/file.h include/lang.h include/lex.h include/num.h include/opt.h include/parse.h include/program.h include/read.h include/status.h include/vector.h include/vm.h
	BC_HEADERS = include/bc.h
	DC_HEADERS = include/dc.h
	HISTORY_HEADERS = include/history.h
	EXTRA_MATH_HEADERS = include/rand.h
	LIBRARY_HEADERS = include/bcl.h include/library.h

	GEN_DIR = gen
	GEN = %%GEN%%
	GEN_EXEC = $(GEN_DIR)/$(GEN)
	GEN_C = $(GEN_DIR)/$(GEN).c

	GEN_EMU = %%GEN_EMU%%

	BC_LIB = $(GEN_DIR)/lib.bc
	BC_LIB_C = $(GEN_DIR)/lib.c
	BC_LIB_O = %%BC_LIB_O%%
	BC_LIB_GCDA = $(GEN_DIR)/lib.gcda
	BC_LIB_GCNO = $(GEN_DIR)/lib.gcno

	BC_LIB2 = $(GEN_DIR)/lib2.bc
	BC_LIB2_C = $(GEN_DIR)/lib2.c
	BC_LIB2_O = %%BC_LIB2_O%%
	BC_LIB2_GCDA = $(GEN_DIR)/lib2.gcda
	BC_LIB2_GCNO = $(GEN_DIR)/lib2.gcno

	BC_HELP = $(GEN_DIR)/bc_help.txt
	BC_HELP_C = $(GEN_DIR)/bc_help.c
	BC_HELP_O = %%BC_HELP_O%%
	BC_HELP_GCDA = $(GEN_DIR)/bc_help.gcda
	BC_HELP_GCNO = $(GEN_DIR)/bc_help.gcno

	DC_HELP = $(GEN_DIR)/dc_help.txt
	DC_HELP_C = $(GEN_DIR)/dc_help.c
	DC_HELP_O = %%DC_HELP_O%%
	DC_HELP_GCDA = $(GEN_DIR)/dc_help.gcda
	DC_HELP_GCNO = $(GEN_DIR)/dc_help.gcno

	BIN = bin
	LOCALES = locales
	EXEC_SUFFIX = %%EXECSUFFIX%%
	EXEC_PREFIX = %%EXECPREFIX%%

	BC = bc
	DC = dc
	BC_EXEC = $(BIN)/$(EXEC_PREFIX)$(BC)
	DC_EXEC = $(BIN)/$(EXEC_PREFIX)$(DC)

	BC_TEST_OUTPUTS = tests/bc_outputs
	BC_FUZZ_OUTPUTS = tests/fuzzing/bc_outputs1 tests/fuzzing/bc_outputs2 tests/fuzzing/bc_outputs3
	DC_TEST_OUTPUTS = tests/dc_outputs
	DC_FUZZ_OUTPUTS = tests/fuzzing/dc_outputs

	LIB = libbcl
	LIB_NAME = $(LIB).a
	LIBBC = $(BIN)/$(LIB_NAME)
	BCL = bcl
	BCL_TEST = $(BIN)/$(BCL)
	BCL_TEST_C = tests/$(BCL).c

	MANUALS = manuals
	BC_MANPAGE_NAME = $(EXEC_PREFIX)$(BC)$(EXEC_SUFFIX).1
	BC_MANPAGE = $(MANUALS)/$(BC).1
	BC_MD = $(BC_MANPAGE).md
	DC_MANPAGE_NAME = $(EXEC_PREFIX)$(DC)$(EXEC_SUFFIX).1
	DC_MANPAGE = $(MANUALS)/$(DC).1
	DC_MD = $(DC_MANPAGE).md
	BCL_MANPAGE_NAME = bcl.3
	BCL_MANPAGE = $(MANUALS)/$(BCL_MANPAGE_NAME)
	BCL_MD = $(BCL_MANPAGE).md

	MANPAGE_INSTALL_ARGS = -Dm644
	BINARY_INSTALL_ARGS = -Dm755

	BCL_HEADER_NAME = bcl.h
	BCL_HEADER = include/$(BCL_HEADER_NAME)

	%%DESTDIR%%
	BINDIR = %%BINDIR%%
	INCLUDEDIR = %%INCLUDEDIR%%
	LIBDIR = %%LIBDIR%%
	MAN1DIR = %%MAN1DIR%%
	MAN3DIR = %%MAN3DIR%%
	MAIN_EXEC = $(EXEC_PREFIX)$(%%MAIN_EXEC%%)$(EXEC_SUFFIX)
	EXEC = $(%%EXEC%%)
	NLSPATH = %%NLSPATH%%

	+BC_BUILD_TYPE = %%BUILD_TYPE%%
	+
	BC_ENABLE_LIBRARY = %%LIBRARY%%

	BC_ENABLE_HISTORY = %%HISTORY%%
	BC_ENABLE_EXTRA_MATH_NAME = BC_ENABLE_EXTRA_MATH
	BC_ENABLE_EXTRA_MATH = %%EXTRA_MATH%%
	BC_ENABLE_NLS = %%NLS%%
	BC_ENABLE_PROMPT = %%PROMPT%%
	BC_LONG_BIT = %%LONG_BIT%%

	BC_ENABLE_AFL = %%FUZZ%%
	BC_ENABLE_MEMCHECK = %%MEMCHECK%%

	RM = rm
	MKDIR = mkdir

	INSTALL = ./exec-install.sh
	SAFE_INSTALL = ./safe-install.sh
	LINK = ./link.sh
	MANPAGE = ./manpage.sh
	KARATSUBA = ./karatsuba.py
	LOCALE_INSTALL = ./locale_install.sh
	LOCALE_UNINSTALL = ./locale_uninstall.sh

	VALGRIND_ARGS = --error-exitcode=100 --leak-check=full --show-leak-kinds=all --errors-for-leak-kinds=all

	TEST_STARS = "***********************************************************************"

	BC_NUM_KARATSUBA_LEN = %%KARATSUBA_LEN%%

	CPPFLAGS1 = -D$(BC_ENABLED_NAME)=$(BC_ENABLED) -D$(DC_ENABLED_NAME)=$(DC_ENABLED)
	-CPPFLAGS2 = $(CPPFLAGS1) -I./include/ -DVERSION=$(VERSION) %%LONG_BIT_DEFINE%%
	+CPPFLAGS2 = $(CPPFLAGS1) -I./include/ -DBUILD_TYPE=$(BC_BUILD_TYPE) %%LONG_BIT_DEFINE%%
	CPPFLAGS3 = $(CPPFLAGS2) -DEXECPREFIX=$(EXEC_PREFIX) -DMAINEXEC=$(MAIN_EXEC)
	CPPFLAGS4 = $(CPPFLAGS3) -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700
	CPPFLAGS5 = $(CPPFLAGS4) -DBC_NUM_KARATSUBA_LEN=$(BC_NUM_KARATSUBA_LEN)
	CPPFLAGS6 = $(CPPFLAGS5) -DBC_ENABLE_NLS=$(BC_ENABLE_NLS) -DBC_ENABLE_PROMPT=$(BC_ENABLE_PROMPT)
	CPPFLAGS7 = $(CPPFLAGS6) -D$(BC_ENABLE_EXTRA_MATH_NAME)=$(BC_ENABLE_EXTRA_MATH)
	CPPFLAGS8 = $(CPPFLAGS7) -DBC_ENABLE_HISTORY=$(BC_ENABLE_HISTORY) -DBC_ENABLE_LIBRARY=$(BC_ENABLE_LIBRARY)
	CPPFLAGS = $(CPPFLAGS8) -DBC_ENABLE_MEMCHECK=$(BC_ENABLE_MEMCHECK) -DBC_ENABLE_AFL=$(BC_ENABLE_AFL)
	CFLAGS = $(CPPFLAGS) %%CPPFLAGS%% %%CFLAGS%%
	LDFLAGS = %%LDFLAGS%%

	HOSTCFLAGS = %%HOSTCFLAGS%%

	CC = %%CC%%
	HOSTCC = %%HOSTCC%%

	BC_LIB_C_ARGS = bc_lib bc_lib_name $(BC_ENABLED_NAME) 1
	BC_LIB2_C_ARGS = bc_lib2 bc_lib2_name "$(BC_ENABLED_NAME) && $(BC_ENABLE_EXTRA_MATH_NAME)" 1

	OBJS = $(DC_HELP_O) $(BC_HELP_O) $(BC_LIB_O) $(BC_LIB2_O) $(OBJ)

	all: %%DEFAULT_TARGET%%

	%%DEFAULT_TARGET%%: %%DEFAULT_TARGET_PREREQS%%
	%%DEFAULT_TARGET_CMD%%

	%%SECOND_TARGET%%: %%SECOND_TARGET_PREREQS%%
	%%SECOND_TARGET_CMD%%

	$(GEN_EXEC):
	%%GEN_EXEC_TARGET%%

	$(BC_LIB_C): $(GEN_EXEC) $(BC_LIB)
	$(GEN_EMU) $(GEN_EXEC) $(BC_LIB) $(BC_LIB_C) $(BC_LIB_C_ARGS)

	$(BC_LIB_O): $(BC_LIB_C)
	$(CC) $(CFLAGS) -o $@ -c $<

	$(BC_LIB2_C): $(GEN_EXEC) $(BC_LIB2)
	$(GEN_EMU) $(GEN_EXEC) $(BC_LIB2) $(BC_LIB2_C) $(BC_LIB2_C_ARGS)

	$(BC_LIB2_O): $(BC_LIB2_C)
	$(CC) $(CFLAGS) -o $@ -c $<

	$(BC_HELP_C): $(GEN_EXEC) $(BC_HELP)
	$(GEN_EMU) $(GEN_EXEC) $(BC_HELP) $(BC_HELP_C) bc_help "" $(BC_ENABLED_NAME)

	$(BC_HELP_O): $(BC_HELP_C)
	$(CC) $(CFLAGS) -o $@ -c $<

	$(DC_HELP_C): $(GEN_EXEC) $(DC_HELP)
	$(GEN_EMU) $(GEN_EXEC) $(DC_HELP) $(DC_HELP_C) dc_help "" $(DC_ENABLED_NAME)

	$(DC_HELP_O): $(DC_HELP_C)
	$(CC) $(CFLAGS) -o $@ -c $<

	$(BIN):
	$(MKDIR) -p $(BIN)

	headers: %%HEADERS%%

	help:
	@printf 'available targets:\n'
	@printf '\n'
	@printf ' all (default) builds %%EXECUTABLES%%\n'
	@printf ' check alias for `make test`\n'
	@printf ' clean removes all build files\n'
	@printf ' clean_config removes all build files as well as the generated Makefile\n'
	@printf ' clean_tests removes all build files, the generated Makefile,\n'
	@printf ' and generated tests\n'
	@printf ' install installs binaries to "%s%s"\n' "$(DESTDIR)" "$(BINDIR)"
	@printf ' and (if enabled) manpages to "%s%s"\n' "$(DESTDIR)" "$(MAN1DIR)"
	@printf ' karatsuba runs the karatsuba script (requires Python 3)\n'
	@printf ' karatsuba_test runs the karatsuba script while running tests\n'
	@printf ' (requires Python 3)\n'
	@printf ' uninstall uninstalls binaries from "%s%s"\n' "$(DESTDIR)" "$(BINDIR)"
	@printf ' and (if enabled) manpages from "%s%s"\n' "$(DESTDIR)" "$(MAN1DIR)"
	@printf ' test runs the test suite\n'
	@printf ' test_bc runs the bc test suite, if bc has been built\n'
	@printf ' test_dc runs the dc test suite, if dc has been built\n'
	@printf ' time_test runs the test suite, displaying times for some things\n'
	@printf ' time_test_bc runs the bc test suite, displaying times for some things\n'
	@printf ' time_test_dc runs the dc test suite, displaying times for some things\n'
	@printf ' timeconst runs the test on the Linux timeconst.bc script,\n'
	@printf ' if it exists and bc has been built\n'
	@printf ' valgrind runs the test suite through valgrind\n'
	@printf ' valgrind_bc runs the bc test suite, if bc has been built,\n'
	@printf ' through valgrind\n'
	@printf ' valgrind_dc runs the dc test suite, if dc has been built,\n'
	@printf ' through valgrind\n'

	run_all_tests:
	%%BC_ALL_TESTS%%
	%%TIMECONST_ALL_TESTS%%
	%%DC_ALL_TESTS%%

	check: test

	test: %%TESTS%%

	test_bc: test_bc_header test_bc_tests test_bc_scripts test_bc_stdin test_bc_read test_bc_errors test_bc_other
	@printf '\nAll bc tests passed.\n\n$(TEST_STARS)\n'

	test_bc_tests:%%BC_TESTS%%

	test_bc_scripts:%%BC_SCRIPT_TESTS%%

	test_bc_stdin:
	@sh tests/stdin.sh bc %%BC_TEST_EXEC%%

	test_bc_read:
	@sh tests/read.sh bc %%BC_TEST_EXEC%%

	test_bc_errors:
	@sh tests/errors.sh bc %%BC_TEST_EXEC%%

	test_bc_other:
	@sh tests/other.sh bc %%BC_TEST_EXEC%%

	test_bc_header:
	@printf '$(TEST_STARS)\n\nRunning bc tests...\n\n'

	test_dc: test_dc_header test_dc_tests test_dc_scripts test_dc_stdin test_dc_read test_dc_errors test_dc_other
	@printf '\nAll dc tests passed.\n\n$(TEST_STARS)\n'

	test_dc_tests:%%DC_TESTS%%

	test_dc_scripts:%%DC_SCRIPT_TESTS%%

	test_dc_stdin:
	@sh tests/stdin.sh dc %%DC_TEST_EXEC%%

	test_dc_read:
	@sh tests/read.sh dc %%DC_TEST_EXEC%%

	test_dc_errors:
	@sh tests/errors.sh dc %%DC_TEST_EXEC%%

	test_dc_other:
	@sh tests/other.sh dc %%DC_TEST_EXEC%%

	test_dc_header:
	@printf '$(TEST_STARS)\n\nRunning dc tests...\n\n'

	timeconst:
	%%TIMECONST%%

	library_test: $(LIBBC)
	$(CC) $(CFLAGS) $(BCL_TEST_C) $(LIBBC) -o $(BCL_TEST)

	test_library: library_test
	$(BCL_TEST)

	karatsuba:
	%%KARATSUBA%%

	karatsuba_test:
	%%KARATSUBA_TEST%%

	coverage_output:
	%%COVERAGE_OUTPUT%%

	coverage:%%COVERAGE_PREREQS%%

	-version:
	- @printf '%s' "$(VERSION)"
	-
	libcname:
	@printf '%s' "$(BC_LIB_C)"

	extra_math:
	@printf '%s' "$(BC_ENABLE_EXTRA_MATH)"

	manpages:
	$(MANPAGE) bc
	$(MANPAGE) dc
	$(MANPAGE) bcl

	clean_gen:
	@$(RM) -f $(GEN_EXEC)

	clean:%%CLEAN_PREREQS%%
	@printf 'Cleaning files...\n'
	+ @$(RM) -f src/.tmp gen/.tmp
	@$(RM) -f $(OBJ)
	@$(RM) -f $(BC_EXEC)
	@$(RM) -f $(DC_EXEC)
	@$(RM) -fr $(BIN)
	@$(RM) -f $(LOCALES)/*.cat
	@$(RM) -f $(BC_LIB_C) $(BC_LIB_O)
	@$(RM) -f $(BC_LIB2_C) $(BC_LIB2_O)
	@$(RM) -f $(BC_HELP_C) $(BC_HELP_O)
	@$(RM) -f $(DC_HELP_C) $(DC_HELP_O)
	@$(RM) -fr $(BC_TEST_OUTPUTS) $(DC_TEST_OUTPUTS)
	@$(RM) -fr $(BC_FUZZ_OUTPUTS) $(DC_FUZZ_OUTPUTS)
	+ @$(RM) -fr Debug/ Release/

	clean_config: clean
	@printf 'Cleaning config...\n'
	@$(RM) -f Makefile
	@$(RM) -f $(BC_MD) $(DC_MD)
	@$(RM) -f $(BC_MANPAGE) $(DC_MANPAGE)

	clean_coverage:
	@printf 'Cleaning coverage files...\n'
	@$(RM) -f *.gcov
	@$(RM) -f *.html
	@$(RM) -f .gcda .gcno
	@$(RM) -f *.profraw
	@$(RM) -f $(GCDA) $(GCNO)
	@$(RM) -f $(BC_GCDA) $(BC_GCNO)
	@$(RM) -f $(DC_GCDA) $(DC_GCNO)
	@$(RM) -f $(HISTORY_GCDA) $(HISTORY_GCNO)
	@$(RM) -f $(RAND_GCDA) $(RAND_GCNO)
	@$(RM) -f $(BC_LIB_GCDA) $(BC_LIB_GCNO)
	@$(RM) -f $(BC_LIB2_GCDA) $(BC_LIB2_GCNO)
	@$(RM) -f $(BC_HELP_GCDA) $(BC_HELP_GCNO)
	@$(RM) -f $(DC_HELP_GCDA) $(DC_HELP_GCNO)

	clean_tests: clean clean_config clean_coverage
	@printf 'Cleaning test files...\n'
	@$(RM) -f tests/bc/parse.txt tests/bc/parse_results.txt
	@$(RM) -f tests/bc/print.txt tests/bc/print_results.txt
	@$(RM) -f tests/bc/bessel.txt tests/bc/bessel_results.txt
	@$(RM) -f tests/bc/scripts/bessel.txt
	@$(RM) -f tests/bc/scripts/parse.txt
	@$(RM) -f tests/bc/scripts/print.txt
	@$(RM) -f tests/bc/scripts/add.txt
	@$(RM) -f tests/bc/scripts/divide.txt
	@$(RM) -f tests/bc/scripts/multiply.txt
	@$(RM) -f tests/bc/scripts/subtract.txt
	@$(RM) -f tests/dc/scripts/prime.txt tests/dc/scripts/stream.txt
	@$(RM) -f .log_*.txt
	@$(RM) -f .math.txt .results.txt .ops.txt
	@$(RM) -f .test.txt
	@$(RM) -f tags .gdbbreakpoints .gdb_history .gdbsetup
	@$(RM) -f cscope.*
	@$(RM) -f bc.old

	install_locales:
	%%INSTALL_LOCALES%%

	install_bc_manpage:
	$(SAFE_INSTALL) $(MANPAGE_INSTALL_ARGS) $(BC_MANPAGE) $(DESTDIR)$(MAN1DIR)/$(BC_MANPAGE_NAME)

	install_dc_manpage:
	$(SAFE_INSTALL) $(MANPAGE_INSTALL_ARGS) $(DC_MANPAGE) $(DESTDIR)$(MAN1DIR)/$(DC_MANPAGE_NAME)

	install_bcl_manpage:
	$(SAFE_INSTALL) $(MANPAGE_INSTALL_ARGS) $(BCL_MANPAGE) $(DESTDIR)$(MAN3DIR)/$(BCL_MANPAGE_NAME)

	install_bcl_header:
	$(SAFE_INSTALL) $(MANPAGE_INSTALL_ARGS) $(BCL_HEADER) $(DESTDIR)$(INCLUDEDIR)/$(BCL_HEADER_NAME)

	install_execs:
	$(INSTALL) $(DESTDIR)$(BINDIR) "$(EXEC_SUFFIX)"

	install_library:
	$(SAFE_INSTALL) $(BINARY_INSTALL_ARGS) $(LIBBC) $(DESTDIR)$(LIBDIR)/$(LIB_NAME)

	install:%%INSTALL_LOCALES_PREREQS%%%%INSTALL_MAN_PREREQS%%%%INSTALL_PREREQS%%

	uninstall_locales:
	$(LOCALE_UNINSTALL) $(NLSPATH) $(MAIN_EXEC) $(DESTDIR)

	uninstall_bc_manpage:
	$(RM) -f $(DESTDIR)$(MAN1DIR)/$(BC_MANPAGE_NAME)

	uninstall_bc:
	$(RM) -f $(DESTDIR)$(BINDIR)/$(EXEC_PREFIX)$(BC)$(EXEC_SUFFIX)

	uninstall_dc_manpage:
	$(RM) -f $(DESTDIR)$(MAN1DIR)/$(DC_MANPAGE_NAME)

	uninstall_dc:
	$(RM) -f $(DESTDIR)$(BINDIR)/$(EXEC_PREFIX)$(DC)$(EXEC_SUFFIX)

	uninstall_library:
	$(RM) -f $(DESTDIR)$(LIBDIR)/$(LIB_NAME)

	uninstall_bcl_header:
	$(RM) -f $(DESTDIR)$(INCLUDEDIR)/$(BCL_HEADER_NAME)

	uninstall_bcl_manpage:
	$(RM) -f $(DESTDIR)$(MAN3DIR)/$(BCL_MANPAGE_NAME)

	uninstall:%%UNINSTALL_LOCALES_PREREQS%%%%UNINSTALL_MAN_PREREQS%%%%UNINSTALL_PREREQS%%
	diff --git a/contrib/bc/NEWS.md b/contrib/bc/NEWS.md
	index 3374ab57bc41..011cb9138912 100644
	--- a/contrib/bc/NEWS.md
	+++ b/contrib/bc/NEWS.md
	@@ -1,1065 +1,1090 @@
	# News

	+## 4.0.0
	+
	+This is a production release with many fixes, a new command-line option, and a
	+big surprise:
	+
	+* A bug was fixed in `dc`'s `P` command where the item on the stack was not
	+ popped.
	+* Various bugs in the manuals have been fixed.
	+* A known bug was fixed where history did not interact well with prompts printed
	+ by user code without newlines.
	+* A new command-line option, `-R` and `--no-read-prompt` was added to disable
	+ just the prompt when using `read()` (`bc`) or `?` (`dc`).
	+* And finally, official support for Windows was added.
	+
	+The last item is why this is a major version bump.
	+
	+Currently, only one set of build options (extra math and prompt enabled, history
	+and NLS/locale support disabled, both calculators enabled) is supported on
	+Windows. However, both debug and release builds are supported.
	+
	+In addition, Windows builds are supported for the the library (`bcl`).
	+
	+For more details about how to build on Windows, see the [README][5] or the
	+[build manual][13].
	+
	## 3.3.4

	This is a production release that fixes a small bug.

	The bug was that output was not flushed before a `read()` call, so prompts
	without a newline on the end were not flushed before the `read()` call.

	This is such a tiny bug that users only need to upgrade if they are affected.

	## 3.3.3

	This is a production release with one tweak and fixes for manuals.

	The tweak is that `length(0)` returns `1` instead of `0`. In `3.3.1`, I changed
	it so `length(0.x)`, where `x` could be any number of digits, returned the
	`scale`, but `length(0)` still returned `0` because I believe that `0` has `0`
	significant digits.

	After request of FreeBSD and considering the arguments of a mathematician,
	compatibility with other `bc`'s, and the expectations of users, I decided to
	make the change.

	The fixes for manuals fixed a bug where `--` was rendered as `-`.

	## 3.3.2

	This is a production release that fixes a divide-by-zero bug in `root()` in the
	[extended math library][16]. All previous versions with `root()` have the bug.

	## 3.3.1

	This is a production release that fixes a bug.

	The bug was in the reporting of number length when the value was 0.

	## 3.3.0

	This is a production release that changes one behavior and fixes documentation
	bugs.

	The changed behavior is the treatment of `-e` and `-f` when given through
	`BC_ENV_ARGS` or `DC_ENV_ARGS`. Now `bc` and `dc` do not exit when those options
	(or their equivalents) are given through those environment variables. However,
	`bc` and `dc` still exit when they or their equivalents are given on the
	command-line.

	## 3.2.7

	This is a production release that removes a small non-portable shell operation
	in `configure.sh`. This problem was only noticed on OpenBSD, not FreeBSD or
	Linux.

	Non-OpenBSD users do *NOT* need to upgrade, although NetBSD users may also
	need to upgrade.

	## 3.2.6

	This is a production release that fixes the build on FreeBSD.

	There was a syntax error in `configure.sh` that the Linux shell did not catch,
	and FreeBSD depends on the existence of `tests/all.sh`.

	All users that already upgraded to `3.2.5` should update to this release, with
	my apologies for the poor release of `3.2.5`. Other users should skip `3.2.5` in
	favor of this version.

	## 3.2.5

	This is a production release that fixes several bugs and adds a couple small
	things.

	The two most important bugs were bugs that causes `dc` to access memory
	out-of-bounds (crash in debug builds). This was found by upgrading to `afl++`
	from `afl`. Both were caused by a failure to distinguish between the same two
	cases.

	Another bug was the failure to put all of the licenses in the `LICENSE.md` file.

	Third, some warnings by `scan-build` were found and eliminated. This needed one
	big change: `bc` and `dc` now bail out as fast as possible on fatal errors
	instead of unwinding the stack.

	Fourth, the pseudo-random number now attempts to seed itself with `/dev/random`
	if `/dev/urandom` fails.

	Finally, this release has a few quality-of-life changes to the build system. The
	usage should not change at all; the only thing that changed was making sure the
	`Makefile.in` was written to rebuild properly when headers changed and to not
	rebuild when not necessary.

	## 3.2.4

	This is a production release that fixes a warning on `gcc` 6 or older, which
	does not have an attribute that is used.

	Users do *NOT* need to upgrade if they don't use `gcc` 6 or older.

	## 3.2.3

	This is a production release that fixes a bug in `gen/strgen.sh`. I recently
	changed `gen/strgen.c`, but I did not change `gen/strgen.sh`.

	Users that do not use `gen/strgen.sh` do not need to upgrade.

	## 3.2.2

	This is a production release that fixes a portability bug in `configure.sh`. The
	bug was using the GNU `find` extension `-wholename`.

	## 3.2.1

	This is a production release that has one fix for `bcl(3)`. It is technically
	not a bug fix since the behavior is undefined, but the `BclNumber`s that
	`bcl_divmod()` returns will be set to `BCL_ERROR_INVALID_NUM` if there is an
	error. Previously, they were not set.

	## 3.2.0

	This is a production release that has one bug fix and a major addition.

	The bug fix was a missing `auto` variable in the bessel `j()` function in the
	math library.

	The major addition is a way to build a version of `bc`'s math code as a library.
	This is done with the `-a` option to `configure.sh`. The API for the library can
	be read in `./manuals/bcl.3.md` or `man bcl` once the library is installed with
	`make install`.

	This library was requested by developers before I even finished version 1.0, but
	I could not figure out how to do it until now.

	If the library has API breaking changes, the major version of `bc` will be
	incremented.

	## 3.1.6

	This is a production release that fixes a new warning from Clang 12 for FreeBSD
	and also removes some possible undefined behavior found by UBSan that compilers
	did not seem to take advantage of.

	Users do *NOT* need to upgrade, if they do not want to.

	## 3.1.5

	This is a production release that fixes the Chinese locales (which caused `bc`
	to crash) and a crash caused by `bc` executing code when it should not have been
	able to.

	*ALL USERS SHOULD UPGRADE.*

	## 3.1.4

	This is a production release that fixes one bug, changes two behaviors, and
	removes one environment variable.

	The bug is like the one in the last release except it applies if files are being
	executed. I also made the fix more general.

	The behavior that was changed is that `bc` now exits when given `-e`, `-f`,
	`--expression` or `--file`. However, if the last one of those is `-f-` (using
	`stdin` as the file), `bc` does not exit. If `-f-` exists and is not the last of
	the `-e` and `-f` options (and equivalents), `bc` gives a fatal error and exits.

	Next, I removed the `BC_EXPR_EXIT` and `DC_EXPR_EXIT` environment variables
	since their use is not needed with the behavior change.

	Finally, I made it so `bc` does not print the header, though the `-q` and
	`--quiet` options were kept for compatibility with GNU `bc`.

	## 3.1.3

	This is a production release that fixes one minor bug: if `bc` was invoked like
	the following, it would error:

	```
	echo "if (1 < 3) 1" \| bc
	```

	Unless users run into this bug, they do not need to upgrade, but it is suggested
	that they do.

	## 3.1.2

	This is a production release that adds a way to install all locales. Users do
	*NOT* need to upgrade.

	For package maintainers wishing to make use of the change, just pass `-l` to
	`configure.sh`.

	## 3.1.1

	This is a production release that adds two Spanish locales. Users do *NOT*
	need to upgrade, unless they want those locales.

	## 3.1.0

	This is a production release that adjusts one behavior, fixes eight bugs, and
	improves manpages for FreeBSD. Because this release fixes bugs, **users and
	package maintainers should update to this version as soon as possible**.

	The behavior that was adjusted was how code from the `-e` and `-f` arguments
	(and equivalents) were executed. They used to be executed as one big chunk, but
	in this release, they are now executed line-by-line.

	The first bug fix in how output to `stdout` was handled in `SIGINT`. If a
	`SIGINT` came in, the `stdout` buffer was not correctly flushed. In fact, a
	clean-up function was not getting called. This release fixes that bug.

	The second bug is in how `dc` handled input from `stdin`. This affected `bc` as
	well since it was a mishandling of the `stdin` buffer.

	The third fixed bug was that `bc` and `dc` could `abort()` (in debug mode) when
	receiving a `SIGTERM`. This one was a race condition with pushing and popping
	items onto and out of vectors.

	The fourth bug fixed was that `bc` could leave extra items on the stack and
	thus, not properly clean up some memory. (The memory would still get
	`free()`'ed, but it would not be `free()`'ed when it could have been.)

	The next two bugs were bugs in `bc`'s parser that caused crashes when executing
	the resulting code.

	The last two bugs were crashes in `dc` that resulted from mishandling of
	strings.

	The manpage improvement was done by switching from [ronn][20] to [Pandoc][21] to
	generate manpages. Pandoc generates much cleaner manpages and doesn't leave
	blank lines where they shouldn't be.

	## 3.0.3

	This is a production release that adds one new feature: specific manpages.

	Before this release, `bc` and `dc` only used one manpage each that referred to
	various build options. This release changes it so there is one manpage set per
	relevant build type. Each manual only has information about its particular
	build, and `configure.sh` selects the correct set for install.

	## 3.0.2

	This is a production release that adds `utf8` locale symlinks and removes an
	unused `auto` variable from the `ceil()` function in the [extended math
	library][16].

	Users do *NOT* need to update unless they want the locales.

	## 3.0.1

	This is a production release with two small changes. Users do *NOT* need to
	upgrade to this release; however, if they haven't upgraded to `3.0.0` yet, it
	may be worthwhile to upgrade to this release.

	The first change is fixing a compiler warning on FreeBSD with strict warnings
	on.

	The second change is to make the new implementation of `ceil()` in `lib2.bc`
	much more efficient.

	## 3.0.0

	Notes for package maintainers:

	*First, the `2.7.0` release series saw a change in the option parsing. This made
	me change one error message and add a few others. The error message that was
	changed removed one format specifier. This means that `printf()` will seqfault
	on old locale files. Unfortunately, `bc` cannot use any locale files except the
	global ones that are already installed, so it will use the previous ones while
	running tests during install. **If `bc` segfaults while running arg tests when
	updating, it is because the global locale files have not been replaced. Make
	sure to either prevent the test suite from running on update or remove the old
	locale files before updating.** (Removing the locale files can be done with
	`make uninstall` or by running the `locale_uninstall.sh` script.) Once this is
	done, `bc` should install without problems.*

	Second, the option to build without signal support has been removed*. See
	below for the reasons why.*

	This is a production release with some small bug fixes, a few improvements,
	three major bug fixes, and a complete redesign of `bc`'s error and signal
	handling. **Users and package maintainers should update to this version as soon
	as possible.**

	The first major bug fix was in how `bc` executed files. Previously, a whole file
	was parsed before it was executed, but if a function is defined after code,
	especially if the function definition was actually a redefinition, and the code
	before the definition referred to the previous function, this `bc` would replace
	the function before executing any code. The fix was to make sure that all code
	that existed before a function definition was executed.

	The second major bug fix was in `bc`'s `lib2.bc`. The `ceil()` function had a
	bug where a `0` in the decimal place after the truncation position, caused it to
	output the wrong numbers if there was any non-zero digit after.

	The third major bug is that when passing parameters to functions, if an
	expression included an array (not an array element) as a parameter, it was
	accepted, when it should have been rejected. It is now correctly rejected.

	Beyond that, this `bc` got several improvements that both sped it up, improved
	the handling of signals, and improved the error handling.

	First, the requirements for `bc` were pushed back to POSIX 2008. `bc` uses one
	function, `strdup()`, which is not in POSIX 2001, and it is in the X/Open System
	Interfaces group 2001. It is, however, in POSIX 2008, and since POSIX 2008 is
	old enough to be supported anywhere that I care, that should be the requirement.

	Second, the BcVm global variable was put into `bss`. This actually slightly
	reduces the size of the executable from a massive code shrink, and it will stop
	`bc` from allocating a large set of memory when `bc` starts.

	Third, the default Karatsuba length was updated from 64 to 32 after making the
	optimization changes below, since 32 is going to be better than 64 after the
	changes.

	Fourth, Spanish translations were added.

	Fifth, the interpreter received a speedup to make performance on non-math-heavy
	scripts more competitive with GNU `bc`. While improvements did, in fact, get it
	much closer (see the [benchmarks][19]), it isn't quite there.

	There were several things done to speed up the interpreter:

	First, several small inefficiencies were removed. These inefficiencies included
	calling the function `bc_vec_pop(v)` twice instead of calling
	`bc_vec_npop(v, 2)`. They also included an extra function call for checking the
	size of the stack and checking the size of the stack more than once on several
	operations.

	Second, since the current `bc` function is the one that stores constants and
	strings, the program caches pointers to the current function's vectors of
	constants and strings to prevent needing to grab the current function in order
	to grab a constant or a string.

	Third, `bc` tries to reuse `BcNum`'s (the internal representation of
	arbitary-precision numbers). If a `BcNum` has the default capacity of
	`BC_NUM_DEF_SIZE` (32 on 64-bit and 16 on 32-bit) when it is freed, it is added
	to a list of available `BcNum`'s. And then, when a `BcNum` is allocated with a
	capacity of `BC_NUM_DEF_SIZE` and any `BcNum`'s exist on the list of reusable
	ones, one of those ones is grabbed instead.

	In order to support these changes, the `BC_NUM_DEF_SIZE` was changed. It used to
	be 16 bytes on all systems, but it was changed to more closely align with the
	minimum allocation size on Linux, which is either 32 bytes (64-bit musl), 24
	bytes (64-bit glibc), 16 bytes (32-bit musl), or 12 bytes (32-bit glibc). Since
	these are the minimum allocation sizes, these are the sizes that would be
	allocated anyway, making it worth it to just use the whole space, so the value
	of `BC_NUM_DEF_SIZE` on 64-bit systems was changed to 32 bytes.

	On top of that, at least on 64-bit, `BC_NUM_DEF_SIZE` supports numbers with
	either 72 integer digits or 45 integer digits and 27 fractional digits. This
	should be more than enough for most cases since `bc`'s default `scale` values
	are 0 or 20, meaning that, by default, it has at most 20 fractional digits. And
	45 integer digits are a lot; it's enough to calculate the amount of mass in
	the Milky Way galaxy in kilograms. Also, 72 digits is enough to calculate the
	diameter of the universe in Planck lengths.

	(For 32-bit, these numbers are either 32 integer digits or 12 integer digits and
	20 fractional digits. These are also quite big, and going much bigger on a
	32-bit system seems a little pointless since 12 digits in just under a trillion
	and 20 fractional digits is still enough for about any use since `10^-20` light
	years is just under a millimeter.)

	All of this together means that for ordinary uses, and even uses in scientific
	work, the default number size will be all that is needed, which means that
	nearly all, if not all, numbers will be reused, relieving pressure on the system
	allocator.

	I did several experiments to find the changes that had the most impact,
	especially with regard to reusing `BcNum`'s. One was putting `BcNum`'s into
	buckets according to their capacity in powers of 2 up to 512. That performed
	worse than `bc` did in `2.7.2`. Another was putting any `BcNum` on the reuse
	list that had a capacity of `BC_NUM_DEF_SIZE * 2` and reusing them for `BcNum`'s
	that requested `BC_NUM_DEF_SIZE`. This did reduce the amount of time spent, but
	it also spent a lot of time in the system allocator for an unknown reason. (When
	using `strace`, a bunch more `brk` calls showed up.) Just reusing `BcNum`'s that
	had exactly `BC_NUM_DEF_SIZE` capacity spent the smallest amount of time in both
	user and system time. This makes sense, especially with the changes to make
	`BC_NUM_DEF_SIZE` bigger on 64-bit systems, since the vast majority of numbers
	will only ever use numbers with a size less than or equal to `BC_NUM_DEF_SIZE`.

	Last of all, `bc`'s signal handling underwent a complete redesign. (This is the
	reason that this version is `3.0.0` and not `2.8.0`.) The change was to move
	from a polling approach to signal handling to an interrupt-based approach.

	Previously, every single loop condition had a check for signals. I suspect that
	this could be expensive when in tight loops.

	Now, the signal handler just uses `longjmp()` (actually `siglongjmp()`) to start
	an unwinding of the stack until it is stopped or the stack is unwound to
	`main()`, which just returns. If `bc` is currently executing code that cannot be
	safely interrupted (according to POSIX), then signals are "locked." The signal
	handler checks if the lock is taken, and if it is, it just sets the status to
	indicate that a signal arrived. Later, when the signal lock is released, the
	status is checked to see if a signal came in. If so, the stack unwinding starts.

	This design eliminates polling in favor of maintaining a stack of `jmp_buf`'s.
	This has its own performance implications, but it gives better interaction. And
	the cost of pushing and popping a `jmp_buf` in a function is paid at most twice.
	Most functions do not pay that price, and most of the rest only pay it once.
	(There are only some 3 functions in `bc` that push and pop a `jmp_buf` twice.)

	As a side effect of this change, I had to eliminate the use of `stdio.h` in `bc`
	because `stdio` does not play nice with signals and `longjmp()`. I implemented
	custom I/O buffer code that takes a fraction of the size. This means that static
	builds will be smaller, but non-static builds will be bigger, though they will
	have less linking time.

	This change is also good because my history implementation was already bypassing
	`stdio` for good reasons, and unifying the architecture was a win.

	Another reason for this change is that my `bc` should always behave correctly
	in the presence of signals like `SIGINT`, `SIGTERM`, and `SIGQUIT`. With the
	addition of my own I/O buffering, I needed to also make sure that the buffers
	were correctly flushed even when such signals happened.

	For this reason, I removed the option to build without signal support.

	As a nice side effect of this change, the error handling code could be changed
	to take advantage of the stack unwinding that signals used. This means that
	signals and error handling use the same code paths, which means that the stack
	unwinding is well-tested. (Errors are tested heavily in the test suite.)

	It also means that functions do not need to return a status code that
	*every* caller needs to check. This eliminated over 100 branches that simply
	checked return codes and then passed that return code up the stack if necessary.
	The code bloat savings from this is at least 1700 bytes on `x86_64`, before
	taking into account the extra code from removing `stdio.h`.

	## 2.7.2

	This is a production release with one major bug fix.

	The `length()` built-in function can take either a number or an array. If it
	takes an array, it returns the length of the array. Arrays can be passed by
	reference. The bug is that the `length()` function would not properly
	dereference arrays that were references. This is a bug that affects all users.

	ALL USERS SHOULD UPDATE `bc`.

	## 2.7.1

	This is a production release with fixes for new locales and fixes for compiler
	warnings on FreeBSD.

	## 2.7.0

	This is a production release with a bug fix for Linux, new translations, and new
	features.

	Bug fixes:

	* Option parsing in `BC_ENV_ARGS` was broken on Linux in 2.6.1 because `glibc`'s
	`getopt_long()` is broken. To get around that, and to support long options on
	every platform, an adapted version of [`optparse`][17] was added. Now, `bc`
	does not even use `getopt()`.
	* Parsing `BC_ENV_ARGS` with quotes now works. It isn't the smartest, but it
	does the job if there are spaces in file names.

	The following new languages are supported:

	* Dutch
	* Polish
	* Russian
	* Japanes
	* Simplified Chinese

	All of these translations were generated using [DeepL][18], so improvements are
	welcome.

	There is only one new feature: **`bc` now has a built-in pseudo-random number
	generator** (PRNG).

	The PRNG is seeded, making it useful for applications where
	`/dev/urandom` does not work because output needs to be reproducible. However,
	it also uses `/dev/urandom` to seed itself by default, so it will start with a
	good seed by default.

	It also outputs 32 bits on 32-bit platforms and 64 bits on 64-bit platforms, far
	better than the 15 bits of C's `rand()` and `bash`'s `$RANDOM`.

	In addition, the PRNG can take a bound, and when it gets a bound, it
	automatically adjusts to remove bias. It can also generate numbers of arbitrary
	size. (As of the time of release, the largest pseudo-random number generated by
	this `bc` was generated with a bound of `2^(2^20)`.)

	***IMPORTANT: read the [`bc` manual][9] and the [`dc` manual][10] to find out
	exactly what guarantees the PRNG provides. The underlying implementation is not
	guaranteed to stay the same, but the guarantees that it provides are guaranteed
	to stay the same regardless of the implementation.***

	On top of that, four functions were added to `bc`'s [extended math library][16]
	to make using the PRNG easier:

	* `frand(p)`: Generates a number between `[0,1)` to `p` decimal places.
	* `ifrand(i, p)`: Generates an integer with bound `i` and adds it to `frand(p)`.
	* `srand(x)`: Randomizes the sign of `x`. In other words, it flips the sign of
	`x` with probability `0.5`.
	* `brand()`: Returns a random boolean value (either `0` or `1`).

	## 2.6.1

	This is a production release with a bug fix for FreeBSD.

	The bug was that when `bc` was built without long options, it would give a fatal
	error on every run. This was caused by a mishandling of `optind`.

	## 2.6.0

	This release is a production release *with no bugfixes*. If you do not want
	to upgrade, you don't have to.

	No source code changed; the only thing that changed was `lib2.bc`.

	This release adds one function to the [extended math library][16]: `p(x, y)`,
	which calculates `x` to the power of `y`, whether or not `y` is an integer. (The
	`^` operator can only accept integer powers.)

	This release also includes a couple of small tweaks to the [extended math
	library][16], mostly to fix returning numbers with too high of `scale`.

	## 2.5.3

	This release is a production release which addresses inconsistencies in the
	Portuguese locales. No `bc` code was changed.

	The issues were that the ISO files used different naming, and also that the
	files that should have been symlinks were not. I did not catch that because
	GitHub rendered them the exact same way.

	## 2.5.2

	This release is a production release.

	No code was changed, but the build system was changed to allow `CFLAGS` to be
	given to `CC`, like this:

	```
	CC="gcc -O3 -march=native" ./configure.sh
	```

	If this happens, the flags are automatically put into `CFLAGS`, and the compiler
	is set appropriately. In the example above this means that `CC` will be "gcc"
	and `CFLAGS` will be "-O3 -march=native".

	This behavior was added to conform to GNU autotools practices.

	## 2.5.1

	This is a production release which addresses portability concerns discovered
	in the `bc` build system. No `bc` code was changed.

	* Support for Solaris SPARC and AIX were added.
	* Minor documentations edits were performed.
	* An option for `configure.sh` was added to disable long options if
	`getopt_long()` is missing.

	## 2.5.0

	This is a production release with new translations. No code changed.

	The translations were contributed by [bugcrazy][15], and they are for
	Portuguese, both Portugal and Brazil locales.

	## 2.4.0

	This is a production release primarily aimed at improving `dc`.

	* A couple of copy and paste errors in the [`dc` manual][10] were fixed.
	* `dc` startup was optimized by making sure it didn't have to set up `bc`-only
	things.
	* The `bc` `&&` and `\|\|` operators were made available to `dc` through the `M`
	and `m` commands, respectively.
	* `dc` macros were changed to be tail call-optimized.

	The last item, tail call optimization, means that if the last thing in a macro
	is a call to another macro, then the old macro is popped before executing the
	new macro. This change was made to stop `dc` from consuming more and more memory
	as macros are executed in a loop.

	The `q` and `Q` commands still respect the "hidden" macros by way of recording
	how many macros were removed by tail call optimization.

	## 2.3.2

	This is a production release meant to fix warnings in the Gentoo `ebuild` by
	making it possible to disable binary stripping. Other users do not need to
	upgrade.

	## 2.3.1

	This is a production release. It fixes a bug that caused `-1000000000 < -1` to
	return `0`. This only happened with negative numbers and only if the value on
	the left was more negative by a certain amount. That said, this bug is a bad
	bug, and needs to be fixed.

	ALL USERS SHOULD UPDATE `bc`.

	## 2.3.0

	This is a production release with changes to the build system.

	## 2.2.0

	This release is a production release. It only has new features and performance
	improvements.

	1. The performance of `sqrt(x)` was improved.
	2. The new function `root(x, n)` was added to the extended math library to
	calculate `n`th roots.
	3. The new function `cbrt(x)` was added to the extended math library to
	calculate cube roots.

	## 2.1.3

	This is a non-critical release; it just changes the build system, and in
	non-breaking ways:

	1. Linked locale files were changed to link to their sources with a relative
	link.
	2. A bug in `configure.sh` that caused long option parsing to fail under `bash`
	was fixed.

	## 2.1.2

	This release is not a critical release.

	1. A few codes were added to history.
	2. Multiplication was optimized a bit more.
	3. Addition and subtraction were both optimized a bit more.

	## 2.1.1

	This release contains a fix for the test suite made for Linux from Scratch: now
	the test suite prints `pass` when a test is passed.

	Other than that, there is no change in this release, so distros and other users
	do not need to upgrade.

	## 2.1.0

	This release is a production release.

	The following bugs were fixed:

	1. A `dc` bug that caused stack mishandling was fixed.
	2. A warning on OpenBSD was fixed.
	3. Bugs in `ctrl+arrow` operations in history were fixed.
	4. The ability to paste multiple lines in history was added.
	5. A `bc` bug, mishandling of array arguments to functions, was fixed.
	6. A crash caused by freeing the wrong pointer was fixed.
	7. A `dc` bug where strings, in a rare case, were mishandled in parsing was
	fixed.

	In addition, the following changes were made:

	1. Division was slightly optimized.
	2. An option was added to the build to disable printing of prompts.
	3. The special case of empty arguments is now handled. This is to prevent
	errors in scripts that end up passing empty arguments.
	4. A harmless bug was fixed. This bug was that, with the pop instructions
	(mostly) removed (see below), `bc` would leave extra values on its stack for
	`void` functions and in a few other cases. These extra items would not
	affect anything put on the stack and would not cause any sort of crash or
	even buggy behavior, but they would cause `bc` to take more memory than it
	needed.

	On top of the above changes, the following optimizations were added:

	1. The need for pop instructions in `bc` was removed.
	2. Extra tests on every iteration of the interpreter loop were removed.
	3. Updating function and code pointers on every iteration of the interpreter
	loop was changed to only updating them when necessary.
	4. Extra assignments to pointers were removed.

	Altogether, these changes sped up the interpreter by around 2x.

	*NOTE*: This is the last release with new features because this `bc` is now
	considered complete. From now on, only bug fixes and new translations will be
	added to this `bc`.

	## 2.0.3

	This is a production, bug-fix release.

	Two bugs were fixed in this release:

	1. A rare and subtle signal handling bug was fixed.
	2. A misbehavior on `0` to a negative power was fixed.

	The last bug bears some mentioning.

	When I originally wrote power, I did not thoroughly check its error cases;
	instead, I had it check if the first number was `0` and then if so, just return
	`0`. However, `0` to a negative power means that `1` will be divided by `0`,
	which is an error.

	I caught this, but only after I stopped being cocky. You see, sometime later, I
	had noticed that GNU `bc` returned an error, correctly, but I thought it was
	wrong simply because that's not what my `bc` did. I saw it again later and had a
	double take. I checked for real, finally, and found out that my `bc` was wrong
	all along.

	That was bad on me. But the bug was easy to fix, so it is fixed now.

	There are two other things in this release:

	1. Subtraction was optimized by [Stefan Eßer][14].
	2. Division was also optimized, also by Stefan Eßer.

	## 2.0.2

	This release contains a fix for a possible overflow in the signal handling. I
	would be surprised if any users ran into it because it would only happen after 2
	billion (`2^31-1`) `SIGINT`'s, but I saw it and had to fix it.

	## 2.0.1

	This release contains very few things that will apply to any users.

	1. A slight bug in `dc`'s interactive mode was fixed.
	2. A bug in the test suite that was only triggered on NetBSD was fixed.
	3. The `-P`/`--no-prompt` option was added for users that do not want a
	prompt.
	4. A `make check` target was added as an alias for `make test`.
	5. `dc` got its own read prompt: `?> `.

	## 2.0.0

	This release is a production release.

	This release is also a little different from previous releases. From here on
	out, I do not plan on adding any more features to this `bc`; I believe that it
	is complete. However, there may be bug fix releases in the future, if I or any
	others manage to find bugs.

	This release has only a few new features:

	1. `atan2(y, x)` was added to the extended math library as both `a2(y, x)` and
	`atan2(y, x)`.
	2. Locales were fixed.
	3. A **POSIX shell-compatible script was added as an alternative to compiling
	`gen/strgen.c`** on a host machine. More details about making the choice
	between the two can be found by running `./configure.sh --help` or reading
	the [build manual][13].
	4. Multiplication was optimized by using diagonal multiplication, rather
	than straight brute force.
	5. The `locale_install.sh` script was fixed.
	6. `dc` was given the ability to **use the environment variable
	`DC_ENV_ARGS`**.
	7. `dc` was also given the ability to use the `-i` or `--interactive`
	options.
	8. Printing the prompt was fixed so that it did not print when it shouldn't.
	9. Signal handling was fixed.
	10. Handling of `SIGTERM` and `SIGQUIT` was fixed.
	11. The built-in functions `maxibase()`, `maxobase()`, and `maxscale()` (the
	commands `T`, `U`, `V` in `dc`, respectively) were added to allow scripts to
	query for the max allowable values of those globals.
	12. Some incompatibilities with POSIX were fixed.

	In addition, this release is `2.0.0` for a big reason: the internal format for
	numbers changed. They used to be a `char` array. Now, they are an array of
	larger integers, packing more decimal digits into each integer. This has
	delivered *HUGE* performance improvements, especially for multiplication,
	division, and power.

	This `bc` should now be the fastest `bc` available, but I may be wrong.

	## 1.2.8

	This release contains a fix for a harmless bug (it is harmless in that it still
	works, but it just copies extra data) in the [`locale_install.sh`][12] script.

	## 1.2.7

	This version contains fixes for the build on Arch Linux.

	## 1.2.6

	This release removes the use of `local` in shell scripts because it's not POSIX
	shell-compatible, and also updates a man page that should have been updated a
	long time ago but was missed.

	## 1.2.5

	This release contains some missing locale `*.msg` files.

	## 1.2.4

	This release contains a few bug fixes and new French translations.

	## 1.2.3

	This release contains a fix for a bug: use of uninitialized data. Such data was
	only used when outputting an error message, but I am striving for perfection. As
	Michelangelo said, "Trifles make perfection, and perfection is no trifle."

	## 1.2.2

	This release contains fixes for OpenBSD.

	## 1.2.1

	This release contains bug fixes for some rare bugs.

	## 1.2.0

	This is a production release.

	There have been several changes since `1.1.0`:

	1. The build system had some changes.
	2. Locale support has been added. (Patches welcome for translations.)
	3. The ability to turn `ibase`, `obase`, and `scale` into stacks was added
	with the `-g` command-line option. (See the [`bc` manual][9] for more
	details.)
	4. Support for compiling on Mac OSX out of the box was added.
	5. The extended math library got `t(x)`, `ceil(x)`, and some aliases.
	6. The extended math library also got `r2d(x)` (for converting from radians to
	degrees) and `d2r(x)` (for converting from degrees to radians). This is to
	allow using degrees with the standard library.
	7. Both calculators now accept numbers in scientific notation. See the
	[`bc` manual][9] and the [`dc` manual][10] for details.
	8. Both calculators can **output in either scientific or engineering
	notation**. See the [`bc` manual][9] and the [`dc` manual][10] for details.
	9. Some inefficiencies were removed.
	10. Some bugs were fixed.
	11. Some bugs in the extended library were fixed.
	12. Some defects from [Coverity Scan][11] were fixed.

	## 1.1.4

	This release contains a fix to the build system that allows it to build on older
	versions of `glibc`.

	## 1.1.3

	This release contains a fix for a bug in the test suite where `bc` tests and
	`dc` tests could not be run in parallel.

	## 1.1.2

	This release has a fix for a history bug; the down arrow did not work.

	## 1.1.1

	This release fixes a bug in the `1.1.0` build system. The source is exactly the
	same.

	The bug that was fixed was a failure to install if no `EXECSUFFIX` was used.

	## 1.1.0

	This is a production release. However, many new features were added since `1.0`.

	1. The build system has been changed to use a custom, POSIX
	shell-compatible configure script ([`configure.sh`][6]) to generate a POSIX
	make-compatible `Makefile`, which means that `bc` and `dc` now build out of
	the box on any POSIX-compatible system.
	2. Out-of-memory and output errors now cause the `bc` to report the error,
	clean up, and die, rather than just reporting and trying to continue.
	3. Strings and constants are now garbage collected when possible.
	4. Signal handling and checking has been made more simple and more thorough.
	5. `BcGlobals` was refactored into `BcVm` and `BcVm` was made global. Some
	procedure names were changed to reflect its difference to everything else.
	6. Addition got a speed improvement.
	7. Some common code for addition and multiplication was refactored into its own
	procedure.
	8. A bug was removed where `dc` could have been selected, but the internal
	`#define` that returned `true` for a query about `dc` would not have
	returned `true`.
	9. Useless calls to `bc_num_zero()` were removed.
	10. History support was added. The history support is based off of a
	[UTF-8 aware fork][7] of [`linenoise`][8], which has been customized with
	`bc`'s own data structures and signal handling.
	11. Generating C source from the math library now removes tabs from the library,
	shrinking the size of the executable.
	12. The math library was shrunk.
	13. Error handling and reporting was improved.
	14. Reallocations were reduced by giving access to the request size for each
	operation.
	15. `abs()` (`b` command for `dc`) was added as a builtin.
	16. Both calculators were tested on FreeBSD.
	17. Many obscure parse bugs were fixed.
	18. Markdown and man page manuals were added, and the man pages are installed by
	`make install`.
	19. Executable size was reduced, though the added features probably made the
	executable end up bigger.
	20. GNU-style array references were added as a supported feature.
	21. Allocations were reduced.
	22. New operators were added: `$` (`$` for `dc`), `@` (`@` for `dc`), `@=`,
	`<<` (`H` for `dc`), `<<=`, `>>` (`h` for `dc`), and `>>=`. See the
	[`bc` manual][9] and the [`dc` manual][10] for more details.
	23. An extended math library was added. This library contains code that
	makes it so I can replace my desktop calculator with this `bc`. See the
	[`bc` manual][3] for more details.
	24. Support for all capital letters as numbers was added.
	25. Support for GNU-style void functions was added.
	26. A bug fix for improper handling of function parameters was added.
	27. Precedence for the or (`\|\|`) operator was changed to match GNU `bc`.
	28. `dc` was given an explicit negation command.
	29. `dc` was changed to be able to handle strings in arrays.

	## 1.1 Release Candidate 3

	This release is the eighth release candidate for 1.1, though it is the third
	release candidate meant as a general release candidate. The new code has not
	been tested as thoroughly as it should for release.

	## 1.1 Release Candidate 2

	This release is the seventh release candidate for 1.1, though it is the second
	release candidate meant as a general release candidate. The new code has not
	been tested as thoroughly as it should for release.

	## 1.1 FreeBSD Beta 5

	This release is the sixth release candidate for 1.1, though it is the fifth
	release candidate meant specifically to test if `bc` works on FreeBSD. The new
	code has not been tested as thoroughly as it should for release.

	## 1.1 FreeBSD Beta 4

	This release is the fifth release candidate for 1.1, though it is the fourth
	release candidate meant specifically to test if `bc` works on FreeBSD. The new
	code has not been tested as thoroughly as it should for release.

	## 1.1 FreeBSD Beta 3

	This release is the fourth release candidate for 1.1, though it is the third
	release candidate meant specifically to test if `bc` works on FreeBSD. The new
	code has not been tested as thoroughly as it should for release.

	## 1.1 FreeBSD Beta 2

	This release is the third release candidate for 1.1, though it is the second
	release candidate meant specifically to test if `bc` works on FreeBSD. The new
	code has not been tested as thoroughly as it should for release.

	## 1.1 FreeBSD Beta 1

	This release is the second release candidate for 1.1, though it is meant
	specifically to test if `bc` works on FreeBSD. The new code has not been tested as
	thoroughly as it should for release.

	## 1.1 Release Candidate 1

	This is the first release candidate for 1.1. The new code has not been tested as
	thoroughly as it should for release.

	## 1.0

	This is the first non-beta release. `bc` is ready for production use.

	As such, a lot has changed since 0.5.

	1. `dc` has been added. It has been tested even more thoroughly than `bc` was
	for `0.5`. It does not have the `!` command, and for security reasons, it
	never will, so it is complete.
	2. `bc` has been more thoroughly tested. An entire section of the test suite
	(for both programs) has been added to test for errors.
	3. A prompt (`>>> `) has been added for interactive mode, making it easier to
	see inputs and outputs.
	4. Interrupt handling has been improved, including elimination of race
	conditions (as much as possible).
	5. MinGW and [Windows Subsystem for Linux][1] support has been added (see
	[xstatic][2] for binaries).
	6. Memory leaks and errors have been eliminated (as far as ASan and Valgrind
	can tell).
	7. Crashes have been eliminated (as far as [afl][3] can tell).
	8. Karatsuba multiplication was added (and thoroughly) tested, speeding up
	multiplication and power by orders of magnitude.
	9. Performance was further enhanced by using a "divmod" function to reduce
	redundant divisions and by removing superfluous `memset()` calls.
	10. To switch between Karatsuba and `O(n^2)` multiplication, the config variable
	`BC_NUM_KARATSUBA_LEN` was added. It is set to a sane default, but the
	optimal number can be found with [`karatsuba.py`][4] (requires Python 3)
	and then configured through `make`.
	11. The random math test generator script was changed to Python 3 and improved.
	`bc` and `dc` have together been run through 30+ million random tests.
	12. All known math bugs have been fixed, including out of control memory
	allocations in `sine` and `cosine` (that was actually a parse bug), certain
	cases of infinite loop on square root, and slight inaccuracies (as much as
	possible; see the [README][5]) in transcendental functions.
	13. Parsing has been fixed as much as possible.
	14. Test coverage was improved to 94.8%. The only paths not covered are ones
	that happen when `malloc()` or `realloc()` fails.
	15. An extension to get the length of an array was added.
	16. The boolean not (`!`) had its precedence change to match negation.
	17. Data input was hardened.
	18. `bc` was made fully compliant with POSIX when the `-s` flag is used or
	`POSIXLY_CORRECT` is defined.
	19. Error handling was improved.
	20. `bc` now checks that files it is given are not directories.

	## 1.0 Release Candidate 7

	This is the seventh release candidate for 1.0. It fixes a few bugs in 1.0
	Release Candidate 6.

	## 1.0 Release Candidate 6

	This is the sixth release candidate for 1.0. It fixes a few bugs in 1.0 Release
	Candidate 5.

	## 1.0 Release Candidate 5

	This is the fifth release candidate for 1.0. It fixes a few bugs in 1.0 Release
	Candidate 4.

	## 1.0 Release Candidate 4

	This is the fourth release candidate for 1.0. It fixes a few bugs in 1.0 Release
	Candidate 3.

	## 1.0 Release Candidate 3

	This is the third release candidate for 1.0. It fixes a few bugs in 1.0 Release
	Candidate 2.

	## 1.0 Release Candidate 2

	This is the second release candidate for 1.0. It fixes a few bugs in 1.0 Release
	Candidate 1.

	## 1.0 Release Candidate 1

	This is the first Release Candidate for 1.0. `bc` is complete, with `dc`, but it
	is not tested.

	## 0.5

	This beta release completes more features, but it is still not complete nor
	tested as thoroughly as necessary.

	## 0.4.1

	This beta release fixes a few bugs in 0.4.

	## 0.4

	This is a beta release. It does not have the complete set of features, and it is
	not thoroughly tested.

	[1]: https://docs.microsoft.com/en-us/windows/wsl/install-win10
	[2]: https://pkg.musl.cc/bc/
	[3]: http://lcamtuf.coredump.cx/afl/
	[4]: ./karatsuba.py
	[5]: ./README.md
	[6]: ./configure.sh
	[7]: https://github.com/rain-1/linenoise-mob
	[8]: https://github.com/antirez/linenoise
	[9]: ./manuals/bc/A.1.md
	[10]: ./manuals/dc/A.1.md
	[11]: https://scan.coverity.com/projects/gavinhoward-bc
	[12]: ./locale_install.sh
	[13]: ./manuals/build.md
	[14]: https://github.com/stesser
	[15]: https://github.com/bugcrazy
	[16]: ./manuals/bc/A.1.md#extended-library
	[17]: https://github.com/skeeto/optparse
	[18]: https://www.deepl.com/translator
	[19]: ./manuals/benchmarks.md
	[20]: https://github.com/apjanke/ronn-ng
	[21]: https://pandoc.org/
	diff --git a/contrib/bc/README.md b/contrib/bc/README.md
	index 6a37a8bfb8da..852c8956a73d 100644
	--- a/contrib/bc/README.md
	+++ b/contrib/bc/README.md
	@@ -1,340 +1,407 @@
	# `bc`

	[![Coverity Scan Build Status][17]][18]

	***WARNING: This project has moved to [https://git.yzena.com/][20] for [these
	reasons][21], though GitHub will remain a mirror.***

	This is an implementation of the [POSIX `bc` calculator][12] that implements
	[GNU `bc`][1] extensions, as well as the period (`.`) extension for the BSD
	flavor of `bc`.

	For more information, see this `bc`'s full manual.

	This `bc` also includes an implementation of `dc` in the same binary, accessible
	via a symbolic link, which implements all FreeBSD and GNU extensions. (If a
	standalone `dc` binary is desired, `bc` can be copied and renamed to `dc`.) The
	`!` command is omitted; I believe this poses security concerns and that such
	functionality is unnecessary.

	For more information, see the `dc`'s full manual.

	This `bc` is Free and Open Source Software (FOSS). It is offered under the BSD
	2-clause License. Full license text may be found in the [`LICENSE.md`][4] file.

	## Prerequisites

	-This `bc` only requires a C99-compatible compiler and a (mostly) POSIX
	-2008-compatible system with the XSI (X/Open System Interfaces) option group.
	+This `bc` only requires either:
	+
	+1. Windows 10 or later, or
	+2. A C99-compatible compiler and a (mostly) POSIX 2008-compatible system with
	+ the XSI (X/Open System Interfaces) option group.

	Since POSIX 2008 with XSI requires the existence of a C99 compiler as `c99`, any
	POSIX and XSI-compatible system will have everything needed.

	-Systems that are known to work:
	+POSIX-compatible systems that are known to work:

	* Linux
	* FreeBSD
	* OpenBSD
	* NetBSD
	* Mac OSX
	* Solaris* (as long as the Solaris version supports POSIX 2008)
	* AIX
	* HP-UX* (except for history)

	+In addition, there is compatibility code to make this `bc` work on Windows.
	+
	Please submit bug reports if this `bc` does not build out of the box on any
	-system besides Windows.
	+system.

	## Build

	-This `bc` should build unmodified on any POSIX-compliant system.
	+### Windows
	+
	+There is no guarantee that this `bc` will work on any version of Windows earlier
	+than Windows 10 (I cannot test on earlier versions), but it is guaranteed to
	+work on Windows 10 at least.
	+
	+Also, if building with MSBuild, the MSBuild bundled with Visual Studio is
	+required.
	+
	+Note: Unlike the POSIX-compatible platforms, only one build configuration is
	+supported on Windows: extra math and prompt enabled, history and NLS (locale
	+support) disabled, with both calculators built.
	+
	+#### `bc`
	+
	+To build `bc`, you can open the `bc.sln` file in Visual Studio, select the
	+configuration, and build.
	+
	+You can also build using MSBuild with the following from the root directory:
	+
	+```
	+msbuild -property:Configuration=<config> bc.sln
	+```
	+
	+where `<config>` is either one of `Debug` or `Release`.
	+
	+#### `bcl` (Library)
	+
	+To build the library, you can open the `bcl.sln` file in Visual Studio, select
	+the configuration, and build.
	+
	+You can also build using MSBuild with the following from the root directory:
	+
	+```
	+msbuild -property:Configuration=<config> bcl.sln
	+```
	+
	+where `<config>` is either one of `Debug` or `Release`.
	+
	+### POSIX-Compatible Systems
	+
	+This `bc` should build unmodified on any POSIX-compliant system or on Windows
	+starting with Windows 10 (though earlier versions may work).

	For more complex build requirements than the ones below, see the
	[build manual][5].

	-### Default
	+On POSIX-compatible systems, `bc` is built as `bin/bc` and `dc` is built as
	+`bin/dc` by default. On Windows, they are built as `Release/bc/bc.exe` and
	+`Release/bc/dc.exe`.
	+
	+Note: On Windows, `dc.exe` is just copied from `bc.exe`; it is not linked.
	+Patches are welcome for a way to do that.
	+
	+#### Default

	For the default build with optimization, use the following commands in the root
	directory:

	```
	./configure.sh -O3
	make
	```

	-### One Calculator
	+#### One Calculator

	To only build `bc`, use the following commands:

	```
	./configure.sh --disable-dc
	make
	```

	To only build `dc`, use the following commands:

	```
	./configure.sh --disable-bc
	make
	```

	-### Debug
	+#### Debug

	For debug builds, use the following commands in the root directory:

	```
	./configure.sh -g
	make
	```

	-### Install
	+#### Install

	To install, use the following command:

	```
	make install
	```

	By default, `bc` and `dc` will be installed in `/usr/local`. For installing in
	other locations, use the `PREFIX` environment variable when running
	`configure.sh` or pass the `--prefix=<prefix>` option to `configure.sh`. See the
	[build manual][5], or run `./configure.sh --help`, for more details.

	-### Library
	+#### Library

	This `bc` does provide a way to build a math library with C bindings. This is
	done by the `-a` or `--library` options to `configure.sh`:

	```
	./configure.sh -a
	```

	When building the library, the executables are not built. For more information,
	see the [build manual][5].

	The library API can be found in [`manuals/bcl.3.md`][26] or `man bcl` once the
	library is installed.

	-The library is built as `bin/libbcl.a`.
	+The library is built as `bin/libbcl.a` on POSIX-compatible systems or as
	+`Release/bcl/bcl.lib` on Windows.

	-### Package and Distro Maintainers
	+#### Package and Distro Maintainers

	-#### Recommended Compiler
	+##### Recommended Compiler

	When I ran benchmarks with my `bc` compiled under `clang`, it performed much
	better than when compiled under `gcc`. I recommend compiling this `bc` with
	`clang`.

	I also recommend building this `bc` with C11 if you can because `bc` will detect
	a C11 compiler and add `_Noreturn` to any relevant function(s).

	-#### Recommended Optimizations
	+##### Recommended Optimizations

	I wrote this `bc` with Separation of Concerns, which means that there are many
	small functions that could be inlined. However, they are often called across
	file boundaries, and the default optimizer can only look at the current file,
	which means that they are not inlined.

	Thus, because of the way this `bc` is built, it will automatically be slower
	than other `bc` implementations when running scripts with no math. (My `bc`'s
	math is much faster, so any non-trivial script should run faster in my `bc`.)

	Some, or all, of the difference can be made up with the right optimizations. The
	optimizations I recommend are:

	1. `-O3`
	2. `-flto` (link-time optimization)

	in that order.

	Link-time optimization, in particular, speeds up the `bc` a lot. This is because
	when link-time optimization is turned on, the optimizer can look across files
	and inline much more heavily.

	However, I recommend *NOT* using `-march=native`. Doing so will reduce this
	`bc`'s performance, at least when building with link-time optimization. See the
	[benchmarks][19] for more details.

	-#### Stripping Binaries
	+##### Stripping Binaries

	By default, non-debug binaries are stripped, but stripping can be disabled with
	the `-T` option to `configure.sh`.

	-#### Using This `bc` as an Alternative
	+##### Using This `bc` as an Alternative

	If this `bc` is packaged as an alternative to an already existing `bc` package,
	it is possible to rename it in the build to prevent name collision. To prepend
	to the name, just run the following:

	```
	EXECPREFIX=<some_prefix> ./configure.sh
	```

	To append to the name, just run the following:

	```
	EXECSUFFIX=<some_suffix> ./configure.sh
	```

	If a package maintainer wishes to add both a prefix and a suffix, that is
	allowed.

	Note: The suggested name (and package name) when `bc` is not available is
	`bc-gh`.

	-#### Karatsuba Number
	+##### Karatsuba Number

	Package and distro maintainers have one tool at their disposal to build this
	`bc` in the optimal configuration: `karatsuba.py`.

	This script is not a compile-time or runtime prerequisite; it is for package and
	distro maintainers to run once when a package is being created. It finds the
	optimal Karatsuba number (see the [algorithms manual][7] for more information)
	for the machine that it is running on.

	The easiest way to run this script is with `make karatsuba`.

	If desired, maintainers can also skip running this script because there is a
	sane default for the Karatsuba number.

	## Status

	This `bc` is robust.

	It is well-tested, fuzzed, and fully standards-compliant (though not certified)
	with POSIX `bc`. The math has been tested with 40+ million random problems, so
	it is as correct as I can make it.

	This `bc` can be used as a drop-in replacement for any existing `bc`. This `bc`
	is also compatible with MinGW toolchains, though history is not supported on
	Windows.

	In addition, this `bc` is considered complete; i.e., there will be no more
	releases with additional features. However, it is actively maintained, so if
	any bugs are found, they will be fixed in new releases. Also, additional
	translations will also be added as they are provided.

	## Comparison to GNU `bc`

	This `bc` compares favorably to GNU `bc`.

	+* This `bc` builds natively on Windows.
	* It has more extensions, which make this `bc` more useful for scripting.
	* This `bc` is a bit more POSIX compliant.
	* It has a much less buggy parser. The GNU `bc` will give parse errors for what
	is actually valid `bc` code, or should be. For example, putting an `else` on
	a new line after a brace can cause GNU `bc` to give a parse error.
	* This `bc` has fewer crashes.
	* GNU `bc` calculates the wrong number of significant digits for `length(x)`.
	* GNU `bc` will sometimes print numbers incorrectly. For example, when running
	it on the file `tests/bc/power.txt` in this repo, GNU `bc` gets all the right
	answers, but it fails to wrap the numbers at the proper place when outputting
	to a file.
	* This `bc` is faster. (See [Performance](#performance).)

	### Performance

	Because this `bc` packs more than `1` decimal digit per hardware integer, this
	`bc` is faster than GNU `bc` and can be much faster. Full benchmarks can be
	found at [manuals/benchmarks.md][19].

	There is one instance where this `bc` is slower: if scripts are light on math.
	This is because this `bc`'s intepreter is slightly slower than GNU `bc`, but
	that is because it is more robust. See the [benchmarks][19].

	## Algorithms

	To see what algorithms this `bc` uses, see the [algorithms manual][7].

	## Locales

	-Currently, this `bc` only has support for English (and US English), French,
	+Currently, there is no locale support on Windows.
	+
	+Additionally, this `bc` only has support for English (and US English), French,
	German, Portuguese, Dutch, Polish, Russian, Japanese, and Chinese locales.
	Patches are welcome for translations; use the existing `*.msg` files in
	`locales/` as a starting point.

	In addition, patches for improvements are welcome; the last two messages in
	Portuguese were made with Google Translate, and the Dutch, Polish, Russian,
	Japanese, and Chinese locales were all generated with [DeepL][22].

	The message files provided assume that locales apply to all regions where a
	language is used, but this might not be true for, e.g., `fr_CA` and `fr_CH`.
	Any corrections or a confirmation that the current texts are acceptable for
	those regions would be appreciated, too.

	## Other Projects

	Other projects based on this bc are:

	* [busybox `bc`][8]. The busybox maintainers have made their own changes, so any
	bugs in the busybox `bc` should be reported to them.

	* [toybox `bc`][9]. The maintainer has also made his own changes, so bugs in the
	toybox `bc` should be reported there.

	* [FreeBSD `bc`][23]. While the `bc` in FreeBSD is kept up-to-date, it is better
	to [report bugs there][24], as well as [submit patches][25], and the
	maintainers of the package will contact me if necessary.

	## Language

	-This `bc` is written in pure ISO C99, using POSIX 2008 APIs.
	+This `bc` is written in pure ISO C99, using POSIX 2008 APIs with custom Windows
	+compatibility code.

	## Commit Messages

	This `bc` uses the commit message guidelines laid out in [this blog post][10].

	## Semantic Versioning

	This `bc` uses [semantic versioning][11].

	## Contents

	Items labeled with `(maintainer use only)` are not included in release source
	tarballs.

	Files:

	.gitignore The git ignore file (maintainer use only).
	+ .gitattributes The git attributes file (maintainer use only).
	+ bc.sln The Visual Studio solution file for bc.
	+ bc.vcxproj The Visual Studio project file for bc.
	+ bc.vcxproj.filters The Visual Studio filters file for bc.
	+ bcl.sln The Visual Studio solution file for bcl.
	+ bcl.vcxproj The Visual Studio project file for bcl.
	+ bcl.vcxproj.filters The Visual Studio filters file for bcl.
	configure A symlink to configure.sh to make packaging easier.
	configure.sh The configure script.
	functions.sh A script with functions used by other scripts.
	install.sh Install script.
	karatsuba.py Script to find the optimal Karatsuba number.
	LICENSE.md A Markdown form of the BSD 2-clause License.
	link.sh A script to link dc to bc.
	locale_install.sh A script to install locales, if desired.
	locale_uninstall.sh A script to uninstall locales.
	Makefile.in The Makefile template.
	- manpage.sh Script to generate man pages from markdown files.
	+ manpage.sh Script to generate man pages from markdown files
	+ (maintainer use only).
	NOTICE.md List of contributors and copyright owners.
	RELEASE.md A checklist for making a release (maintainer use only).
	release.sh A script to test for release (maintainer use only).
	safe-install.sh Safe install script from musl libc.

	Folders:

	gen The bc math library, help texts, and code to generate C source.
	include All header files.
	locales Locale files, in .msg format. Patches welcome for translations.
	manuals Manuals for both programs.
	src All source code.
	tests All tests.

	[1]: https://www.gnu.org/software/bc/
	[4]: ./LICENSE.md
	[5]: ./manuals/build.md
	[7]: ./manuals/algorithms.md
	[8]: https://git.busybox.net/busybox/tree/miscutils/bc.c
	[9]: https://github.com/landley/toybox/blob/master/toys/pending/bc.c
	[10]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
	[11]: http://semver.org/
	[12]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[17]: https://img.shields.io/coverity/scan/16609.svg
	[18]: https://scan.coverity.com/projects/gavinhoward-bc
	[19]: ./manuals/benchmarks.md
	[20]: https://git.yzena.com/gavin/bc
	[21]: https://gavinhoward.com/2020/04/i-am-moving-away-from-github/
	[22]: https://www.deepl.com/translator
	[23]: https://cgit.freebsd.org/src/tree/contrib/bc
	[24]: https://bugs.freebsd.org/
	[25]: https://reviews.freebsd.org/
	[26]: ./manuals/bcl.3.md
	diff --git a/contrib/bc/bc.sln b/contrib/bc/bc.sln
	new file mode 100644
	index 000000000000..584b28d13bf6
	--- /dev/null
	+++ b/contrib/bc/bc.sln
	@@ -0,0 +1,31 @@
	+
	+Microsoft Visual Studio Solution File, Format Version 12.00
	+# Visual Studio Version 16
	+VisualStudioVersion = 16.0.31129.286
	+MinimumVisualStudioVersion = 10.0.40219.1
	+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "bc", "bc.vcxproj", "{D5086CFE-052C-4742-B005-E05DB983BBA2}"
	+EndProject
	+Global
	+ GlobalSection(SolutionConfigurationPlatforms) = preSolution
	+ Debug\|x64 = Debug\|x64
	+ Debug\|x86 = Debug\|x86
	+ Release\|x64 = Release\|x64
	+ Release\|x86 = Release\|x86
	+ EndGlobalSection
	+ GlobalSection(ProjectConfigurationPlatforms) = postSolution
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Debug\|x64.ActiveCfg = Debug\|x64
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Debug\|x64.Build.0 = Debug\|x64
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Debug\|x86.ActiveCfg = Debug\|Win32
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Debug\|x86.Build.0 = Debug\|Win32
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Release\|x64.ActiveCfg = Release\|x64
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Release\|x64.Build.0 = Release\|x64
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Release\|x86.ActiveCfg = Release\|Win32
	+ {D5086CFE-052C-4742-B005-E05DB983BBA2}.Release\|x86.Build.0 = Release\|Win32
	+ EndGlobalSection
	+ GlobalSection(SolutionProperties) = preSolution
	+ HideSolutionNode = FALSE
	+ EndGlobalSection
	+ GlobalSection(ExtensibilityGlobals) = postSolution
	+ SolutionGuid = {7869B1FB-A7C4-4FCF-8B99-F696DB2765EC}
	+ EndGlobalSection
	+EndGlobal
	diff --git a/contrib/bc/bc.vcxproj b/contrib/bc/bc.vcxproj
	new file mode 100644
	index 000000000000..ba0a7f6f1dd6
	--- /dev/null
	+++ b/contrib/bc/bc.vcxproj
	@@ -0,0 +1,278 @@
	+<?xml version="1.0" encoding="utf-8"?>
	+<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
	+ <ItemGroup Label="ProjectConfigurations">
	+ <ProjectConfiguration Include="Debug\|Win32">
	+ <Configuration>Debug</Configuration>
	+ <Platform>Win32</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Release\|Win32">
	+ <Configuration>Release</Configuration>
	+ <Platform>Win32</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Debug\|x64">
	+ <Configuration>Debug</Configuration>
	+ <Platform>x64</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Release\|x64">
	+ <Configuration>Release</Configuration>
	+ <Platform>x64</Platform>
	+ </ProjectConfiguration>
	+ </ItemGroup>
	+ <PropertyGroup Label="Globals">
	+ <VCProjectVersion>16.0</VCProjectVersion>
	+ <ProjectGuid>{D5086CFE-052C-4742-B005-E05DB983BBA2}</ProjectGuid>
	+ <Keyword>Win32Proj</Keyword>
	+ </PropertyGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'" Label="Configuration">
	+ <ConfigurationType>Application</ConfigurationType>
	+ <UseDebugLibraries>true</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'" Label="Configuration">
	+ <ConfigurationType>Application</ConfigurationType>
	+ <UseDebugLibraries>false</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'" Label="Configuration">
	+ <ConfigurationType>Application</ConfigurationType>
	+ <UseDebugLibraries>true</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'" Label="Configuration">
	+ <ConfigurationType>Application</ConfigurationType>
	+ <UseDebugLibraries>false</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
	+ <ImportGroup Label="ExtensionSettings">
	+ </ImportGroup>
	+ <ImportGroup Label="Shared">
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ItemGroup>
	+ <CustomBuild Include="gen\strgen.c">
	+ <Message>Building strgen</Message>
	+ <Command>CL /Fo:$(Configuration)\$(ProjectName)\ /Fe:$(Configuration)\$(ProjectName)\strgen.exe gen\strgen.c</Command>
	+ <Inputs>gen\strgen.c</Inputs>
	+ <Outputs>$(Configuration)\$(ProjectName)\strgen.exe</Outputs>
	+ </CustomBuild>
	+ <CustomBuild Include="gen\lib.bc">
	+ <Message>Generating $(Configuration)\$(ProjectName)/lib.c</Message>
	+ <Command>START $(Configuration)\$(ProjectName)/strgen gen\lib.bc $(Configuration)\$(ProjectName)/lib.c bc_lib bc_lib_name BC_ENABLED 1</Command>
	+ <Inputs>$(Configuration)\$(ProjectName)\strgen.exe;gen\lib.bc</Inputs>
	+ <Outputs>$(Configuration)\$(ProjectName)\lib.c</Outputs>
	+ </CustomBuild>
	+ <CustomBuild Include="gen\lib2.bc">
	+ <Message>Generating $(Configuration)\$(ProjectName)/lib2.c</Message>
	+ <Command>START $(Configuration)\$(ProjectName)/strgen gen\lib2.bc $(Configuration)\$(ProjectName)/lib2.c bc_lib2 bc_lib2_name BC_ENABLED 1</Command>
	+ <Inputs>$(Configuration)\$(ProjectName)\strgen.exe;gen\lib2.bc</Inputs>
	+ <Outputs>$(Configuration)\$(ProjectName)\lib2.c</Outputs>
	+ </CustomBuild>
	+ <CustomBuild Include="gen\bc_help.txt">
	+ <Message>Generating $(Configuration)\$(ProjectName)/bc_help.c</Message>
	+ <Command>START $(Configuration)\$(ProjectName)/strgen gen\bc_help.txt $(Configuration)\$(ProjectName)\bc_help.c bc_help "" BC_ENABLED</Command>
	+ <Inputs>$(Configuration)\$(ProjectName)\strgen.exe;gen\bc_help.txt</Inputs>
	+ <Outputs>$(Configuration)\$(ProjectName)\bc_help.c</Outputs>
	+ </CustomBuild>
	+ <CustomBuild Include="gen\dc_help.txt">
	+ <Message>Generating $(Configuration)\$(ProjectName)/dc_help.c</Message>
	+ <Command>START $(Configuration)\$(ProjectName)/strgen gen\dc_help.txt $(Configuration)\$(ProjectName)\dc_help.c dc_help "" DC_ENABLED</Command>
	+ <Inputs>$(Configuration)\$(ProjectName)\strgen.exe;gen\dc_help.txt</Inputs>
	+ <Outputs>$(Configuration)\$(ProjectName)\dc_help.c</Outputs>
	+ </CustomBuild>
	+ </ItemGroup>
	+ <PropertyGroup>
	+ <CustomBuildBeforeTargets>ClCompile</CustomBuildBeforeTargets>
	+ </PropertyGroup>
	+ <PropertyGroup Label="UserMacros" />
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <LinkIncremental>false</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <LinkIncremental>false</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=1;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=0;EXECSUFFIX=.exe;BUILD_TYPE=HN</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
	+ <RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <Optimization>Disabled</Optimization>
	+ <ExceptionHandling>false</ExceptionHandling>
	+ <AdditionalOptions>/W3 %(AdditionalOptions)</AdditionalOptions>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX86</TargetMachine>
	+ <GenerateDebugInformation>true</GenerateDebugInformation>
	+ <SubSystem>Console</SubSystem>
	+ <AdditionalDependencies>kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;odbccp32.lib;bcrypt.lib;ucrt.lib;%(AdditionalDependencies)</AdditionalDependencies>
	+ </Link>
	+ <PostBuildEvent>
	+ <Command>copy /b "$(SolutionDir)\$(Configuration)\$(ProjectName)\bc.exe" "$(SolutionDir)\$(Configuration)\$(ProjectName)\dc.exe"</Command>
	+ </PostBuildEvent>
	+ <PostBuildEvent>
	+ <Message>Copying bc to dc...</Message>
	+ </PostBuildEvent>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=1;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=0;EXECSUFFIX=.exe;BUILD_TYPE=HN</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
	+ <RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <Optimization>MaxSpeed</Optimization>
	+ <ExceptionHandling>false</ExceptionHandling>
	+ <AdditionalOptions>/W3 %(AdditionalOptions)</AdditionalOptions>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX86</TargetMachine>
	+ <GenerateDebugInformation>false</GenerateDebugInformation>
	+ <SubSystem>Console</SubSystem>
	+ <AdditionalDependencies>kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;odbccp32.lib;bcrypt.lib;ucrt.lib;%(AdditionalDependencies)</AdditionalDependencies>
	+ <EnableCOMDATFolding>true</EnableCOMDATFolding>
	+ <OptimizeReferences>true</OptimizeReferences>
	+ </Link>
	+ <PostBuildEvent>
	+ <Command>copy /b "$(SolutionDir)\$(Configuration)\$(ProjectName)\bc.exe" "$(SolutionDir)\$(Configuration)\$(ProjectName)\dc.exe"</Command>
	+ </PostBuildEvent>
	+ <PostBuildEvent>
	+ <Message>Copying bc to dc...</Message>
	+ </PostBuildEvent>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=1;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=0;EXECSUFFIX=.exe;BUILD_TYPE=HN</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
	+ <RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <Optimization>Disabled</Optimization>
	+ <ExceptionHandling>false</ExceptionHandling>
	+ <AdditionalOptions>/W3 %(AdditionalOptions)</AdditionalOptions>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX64</TargetMachine>
	+ <GenerateDebugInformation>true</GenerateDebugInformation>
	+ <SubSystem>Console</SubSystem>
	+ <AdditionalDependencies>kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;odbccp32.lib;bcrypt.lib;ucrt.lib;%(AdditionalDependencies)</AdditionalDependencies>
	+ </Link>
	+ <PostBuildEvent>
	+ <Command>copy /b "$(SolutionDir)\$(Configuration)\$(ProjectName)\bc.exe" "$(SolutionDir)\$(Configuration)\$(ProjectName)\dc.exe"</Command>
	+ </PostBuildEvent>
	+ <PostBuildEvent>
	+ <Message>Copying bc to dc...</Message>
	+ </PostBuildEvent>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=1;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=0;EXECSUFFIX=.exe;BUILD_TYPE=HN</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include;%(AdditionalIncludeDirectories)</AdditionalIncludeDirectories>
	+ <RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <Optimization>MaxSpeed</Optimization>
	+ <ExceptionHandling>false</ExceptionHandling>
	+ <AdditionalOptions>/W3 %(AdditionalOptions)</AdditionalOptions>
	+ <BasicRuntimeChecks>Default</BasicRuntimeChecks>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX64</TargetMachine>
	+ <GenerateDebugInformation>false</GenerateDebugInformation>
	+ <SubSystem>Console</SubSystem>
	+ <AdditionalDependencies>kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;odbccp32.lib;bcrypt.lib;ucrt.lib;%(AdditionalDependencies)</AdditionalDependencies>
	+ </Link>
	+ <PostBuildEvent>
	+ <Command>copy /b "$(SolutionDir)\$(Configuration)\$(ProjectName)\bc.exe" "$(SolutionDir)\$(Configuration)\$(ProjectName)\dc.exe"</Command>
	+ </PostBuildEvent>
	+ <PostBuildEvent>
	+ <Message>Copying bc to dc...</Message>
	+ </PostBuildEvent>
	+ </ItemDefinitionGroup>
	+ <ItemGroup>
	+ <ClCompile Include="$(Configuration)\$(ProjectName)\lib.c" />
	+ <ClCompile Include="$(Configuration)\$(ProjectName)\lib2.c" />
	+ <ClCompile Include="$(Configuration)\$(ProjectName)\bc_help.c" />
	+ <ClCompile Include="$(Configuration)\$(ProjectName)\dc_help.c" />
	+ <ClCompile Include="src\args.c" />
	+ <ClCompile Include="src\bc.c" />
	+ <ClCompile Include="src\bc_lex.c" />
	+ <ClCompile Include="src\bc_parse.c" />
	+ <ClCompile Include="src\data.c" />
	+ <ClCompile Include="src\dc.c" />
	+ <ClCompile Include="src\dc_lex.c" />
	+ <ClCompile Include="src\dc_parse.c" />
	+ <ClCompile Include="src\file.c" />
	+ <ClCompile Include="src\history.c" />
	+ <ClCompile Include="src\lang.c" />
	+ <ClCompile Include="src\lex.c" />
	+ <ClCompile Include="src\main.c" />
	+ <ClCompile Include="src\num.c" />
	+ <ClCompile Include="src\opt.c" />
	+ <ClCompile Include="src\parse.c" />
	+ <ClCompile Include="src\program.c" />
	+ <ClCompile Include="src\rand.c" />
	+ <ClCompile Include="src\read.c" />
	+ <ClCompile Include="src\vector.c" />
	+ <ClCompile Include="src\vm.c" />
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClInclude Include="include\args.h" />
	+ <ClInclude Include="include\bc.h" />
	+ <ClInclude Include="include\bcl.h" />
	+ <ClInclude Include="include\dc.h" />
	+ <ClInclude Include="include\file.h" />
	+ <ClInclude Include="include\history.h" />
	+ <ClInclude Include="include\lang.h" />
	+ <ClInclude Include="include\lex.h" />
	+ <ClInclude Include="include\library.h" />
	+ <ClInclude Include="include\num.h" />
	+ <ClInclude Include="include\opt.h" />
	+ <ClInclude Include="include\parse.h" />
	+ <ClInclude Include="include\program.h" />
	+ <ClInclude Include="include\rand.h" />
	+ <ClInclude Include="include\read.h" />
	+ <ClInclude Include="include\status.h" />
	+ <ClInclude Include="include\vector.h" />
	+ <ClInclude Include="include\version.h" />
	+ <ClInclude Include="include\vm.h" />
	+ </ItemGroup>
	+ <ItemGroup>
	+ <Text Include="gen\bc_help.txt" />
	+ <Text Include="gen\dc_help.txt" />
	+ </ItemGroup>
	+ <ItemGroup>
	+ <None Include="gen\lib.bc" />
	+ <None Include="gen\lib2.bc" />
	+ </ItemGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
	+ <ImportGroup Label="ExtensionTargets">
	+ </ImportGroup>
	+</Project>
	\ No newline at end of file
	diff --git a/contrib/bc/bc.vcxproj.filters b/contrib/bc/bc.vcxproj.filters
	new file mode 100644
	index 000000000000..bc72b60519e9
	--- /dev/null
	+++ b/contrib/bc/bc.vcxproj.filters
	@@ -0,0 +1,182 @@
	+<?xml version="1.0" encoding="utf-8"?>
	+<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
	+ <ItemGroup>
	+ <Filter Include="Source Files">
	+ <UniqueIdentifier>{4FC737F1-C7A5-4376-A066-2A32D752A2FF}</UniqueIdentifier>
	+ <Extensions>cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx</Extensions>
	+ </Filter>
	+ <Filter Include="Header Files">
	+ <UniqueIdentifier>{93995380-89BD-4b04-88EB-625FBE52EBFB}</UniqueIdentifier>
	+ <Extensions>h;hh;hpp;hxx;hm;inl;inc;xsd</Extensions>
	+ </Filter>
	+ <Filter Include="Resource Files">
	+ <UniqueIdentifier>{67DA6AB6-F800-4c08-8B7A-83BB121AAD01}</UniqueIdentifier>
	+ <Extensions>rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav</Extensions>
	+ </Filter>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClCompile Include="src\args.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\bc.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\bc_lex.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\bc_parse.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\data.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\dc.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\dc_lex.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\dc_parse.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\file.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\history.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\lang.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\lex.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\main.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\num.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\opt.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\parse.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\program.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\rand.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\read.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\vector.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\vm.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="gen\lib.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="gen\lib2.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="gen\bc_help.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="gen\dc_help.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClInclude Include="include\args.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\bc.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\bcl.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\dc.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\file.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\history.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\lang.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\lex.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\library.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\num.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\opt.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\parse.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\program.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\rand.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\read.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\status.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\vector.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\version.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\vm.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <CustomBuild Include="gen\strgen.c">
	+ <Filter>Source Files</Filter>
	+ </CustomBuild>
	+ <CustomBuild Include="gen\lib.bc" />
	+ <CustomBuild Include="gen\lib2.bc" />
	+ <CustomBuild Include="gen\bc_help.txt" />
	+ <CustomBuild Include="gen\dc_help.txt" />
	+ <CustomBuild Include="gen\lib.bc" />
	+ <CustomBuild Include="gen\lib2.bc" />
	+ <CustomBuild Include="gen\bc_help.txt" />
	+ <CustomBuild Include="gen\dc_help.txt" />
	+ </ItemGroup>
	+ <ItemGroup>
	+ <Text Include="gen\bc_help.txt">
	+ <Filter>Resource Files</Filter>
	+ </Text>
	+ <Text Include="gen\dc_help.txt">
	+ <Filter>Resource Files</Filter>
	+ </Text>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <None Include="gen\lib.bc">
	+ <Filter>Resource Files</Filter>
	+ </None>
	+ <None Include="gen\lib2.bc">
	+ <Filter>Resource Files</Filter>
	+ </None>
	+ </ItemGroup>
	+</Project>
	\ No newline at end of file
	diff --git a/contrib/bc/bcl.sln b/contrib/bc/bcl.sln
	new file mode 100644
	index 000000000000..77009a439db3
	--- /dev/null
	+++ b/contrib/bc/bcl.sln
	@@ -0,0 +1,31 @@
	+
	+Microsoft Visual Studio Solution File, Format Version 12.00
	+# Visual Studio Version 16
	+VisualStudioVersion = 16.0.31129.286
	+MinimumVisualStudioVersion = 10.0.40219.1
	+Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "bcl", "bcl.vcxproj", "{D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}"
	+EndProject
	+Global
	+ GlobalSection(SolutionConfigurationPlatforms) = preSolution
	+ Debug\|x64 = Debug\|x64
	+ Debug\|x86 = Debug\|x86
	+ Release\|x64 = Release\|x64
	+ Release\|x86 = Release\|x86
	+ EndGlobalSection
	+ GlobalSection(ProjectConfigurationPlatforms) = postSolution
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Debug\|x64.ActiveCfg = Debug\|x64
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Debug\|x64.Build.0 = Debug\|x64
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Debug\|x86.ActiveCfg = Debug\|Win32
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Debug\|x86.Build.0 = Debug\|Win32
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Release\|x64.ActiveCfg = Release\|x64
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Release\|x64.Build.0 = Release\|x64
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Release\|x86.ActiveCfg = Release\|Win32
	+ {D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}.Release\|x86.Build.0 = Release\|Win32
	+ EndGlobalSection
	+ GlobalSection(SolutionProperties) = preSolution
	+ HideSolutionNode = FALSE
	+ EndGlobalSection
	+ GlobalSection(ExtensibilityGlobals) = postSolution
	+ SolutionGuid = {591735E0-C314-4BFF-A595-E9999B49CB25}
	+ EndGlobalSection
	+EndGlobal
	diff --git a/contrib/bc/bcl.vcxproj b/contrib/bc/bcl.vcxproj
	new file mode 100644
	index 000000000000..933c4e93094c
	--- /dev/null
	+++ b/contrib/bc/bcl.vcxproj
	@@ -0,0 +1,161 @@
	+<?xml version="1.0" encoding="utf-8"?>
	+<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
	+ <ItemGroup Label="ProjectConfigurations">
	+ <ProjectConfiguration Include="Debug\|Win32">
	+ <Configuration>Debug</Configuration>
	+ <Platform>Win32</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Release\|Win32">
	+ <Configuration>Release</Configuration>
	+ <Platform>Win32</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Debug\|x64">
	+ <Configuration>Debug</Configuration>
	+ <Platform>x64</Platform>
	+ </ProjectConfiguration>
	+ <ProjectConfiguration Include="Release\|x64">
	+ <Configuration>Release</Configuration>
	+ <Platform>x64</Platform>
	+ </ProjectConfiguration>
	+ </ItemGroup>
	+ <PropertyGroup Label="Globals">
	+ <VCProjectVersion>16.0</VCProjectVersion>
	+ <ProjectGuid>{D2CC3DCF-7919-4DEF-839D-E9B897EC3E8E}</ProjectGuid>
	+ <Keyword>Win32Proj</Keyword>
	+ <WindowsTargetPlatformVersion>10.0</WindowsTargetPlatformVersion>
	+ </PropertyGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'" Label="Configuration">
	+ <ConfigurationType>StaticLibrary</ConfigurationType>
	+ <UseDebugLibraries>true</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'" Label="Configuration">
	+ <ConfigurationType>StaticLibrary</ConfigurationType>
	+ <UseDebugLibraries>false</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'" Label="Configuration">
	+ <ConfigurationType>StaticLibrary</ConfigurationType>
	+ <UseDebugLibraries>true</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'" Label="Configuration">
	+ <ConfigurationType>StaticLibrary</ConfigurationType>
	+ <UseDebugLibraries>false</UseDebugLibraries>
	+ <PlatformToolset>v142</PlatformToolset>
	+ </PropertyGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
	+ <ImportGroup Label="ExtensionSettings">
	+ </ImportGroup>
	+ <ImportGroup Label="Shared">
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <ImportGroup Label="PropertySheets" Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
	+ </ImportGroup>
	+ <PropertyGroup Label="UserMacros" />
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <PropertyGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <LinkIncremental>true</LinkIncremental>
	+ <OutDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</OutDir>
	+ <IntDir>$(SolutionDir)\$(Configuration)\$(ProjectName)\</IntDir>
	+ </PropertyGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|Win32'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_LIB;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=0;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=1</PreprocessorDefinitions>
	+ <RuntimeLibrary>MultiThreadedDebugDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <Optimization>Disabled</Optimization>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include</AdditionalIncludeDirectories>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX86</TargetMachine>
	+ <GenerateDebugInformation>true</GenerateDebugInformation>
	+ <SubSystem>Windows</SubSystem>
	+ </Link>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|Win32'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_LIB;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=0;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=1</PreprocessorDefinitions>
	+ <RuntimeLibrary>MultiThreadedDLL</RuntimeLibrary>
	+ <WarningLevel>Level3</WarningLevel>
	+ <DebugInformationFormat>ProgramDatabase</DebugInformationFormat>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include</AdditionalIncludeDirectories>
	+ </ClCompile>
	+ <Link>
	+ <TargetMachine>MachineX86</TargetMachine>
	+ <GenerateDebugInformation>true</GenerateDebugInformation>
	+ <SubSystem>Windows</SubSystem>
	+ <EnableCOMDATFolding>true</EnableCOMDATFolding>
	+ <OptimizeReferences>true</OptimizeReferences>
	+ </Link>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Release\|x64'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_LIB;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=0;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=1</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include</AdditionalIncludeDirectories>
	+ </ClCompile>
	+ </ItemDefinitionGroup>
	+ <ItemDefinitionGroup Condition="'$(Configuration)\|$(Platform)'=='Debug\|x64'">
	+ <ClCompile>
	+ <PreprocessorDefinitions>WIN32;_DEBUG;_LIB;%(PreprocessorDefinitions);BC_ENABLED=1;DC_ENABLED=1;BC_ENABLE_EXTRA_MATH=1;BC_ENABLE_HISTORY=0;BC_ENABLE_NLS=0;BC_ENABLE_PROMPT=0;BC_DEBUG_CODE=0;BC_ENABLE_LIBRARY=1</PreprocessorDefinitions>
	+ <AdditionalIncludeDirectories>$(SolutionDir)\include</AdditionalIncludeDirectories>
	+ </ClCompile>
	+ </ItemDefinitionGroup>
	+ <ItemGroup>
	+ <ClCompile Include="src\data.c" />
	+ <ClCompile Include="src\library.c" />
	+ <ClCompile Include="src\num.c" />
	+ <ClCompile Include="src\rand.c" />
	+ <ClCompile Include="src\vector.c" />
	+ <ClCompile Include="src\vm.c" />
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClInclude Include="include\args.h" />
	+ <ClInclude Include="include\bc.h" />
	+ <ClInclude Include="include\bcl.h" />
	+ <ClInclude Include="include\dc.h" />
	+ <ClInclude Include="include\file.h" />
	+ <ClInclude Include="include\history.h" />
	+ <ClInclude Include="include\lang.h" />
	+ <ClInclude Include="include\lex.h" />
	+ <ClInclude Include="include\library.h" />
	+ <ClInclude Include="include\num.h" />
	+ <ClInclude Include="include\opt.h" />
	+ <ClInclude Include="include\parse.h" />
	+ <ClInclude Include="include\program.h" />
	+ <ClInclude Include="include\rand.h" />
	+ <ClInclude Include="include\read.h" />
	+ <ClInclude Include="include\status.h" />
	+ <ClInclude Include="include\vector.h" />
	+ <ClInclude Include="include\version.h" />
	+ <ClInclude Include="include\vm.h" />
	+ </ItemGroup>
	+ <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
	+ <ImportGroup Label="ExtensionTargets">
	+ </ImportGroup>
	+</Project>
	\ No newline at end of file
	diff --git a/contrib/bc/bcl.vcxproj.filters b/contrib/bc/bcl.vcxproj.filters
	new file mode 100644
	index 000000000000..5d8a13ba25f7
	--- /dev/null
	+++ b/contrib/bc/bcl.vcxproj.filters
	@@ -0,0 +1,96 @@
	+<?xml version="1.0" encoding="utf-8"?>
	+<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
	+ <ItemGroup>
	+ <Filter Include="Source Files">
	+ <UniqueIdentifier>{4FC737F1-C7A5-4376-A066-2A32D752A2FF}</UniqueIdentifier>
	+ <Extensions>cpp;c;cc;cxx;def;odl;idl;hpj;bat;asm;asmx</Extensions>
	+ </Filter>
	+ <Filter Include="Header Files">
	+ <UniqueIdentifier>{93995380-89BD-4b04-88EB-625FBE52EBFB}</UniqueIdentifier>
	+ <Extensions>h;hh;hpp;hxx;hm;inl;inc;xsd</Extensions>
	+ </Filter>
	+ <Filter Include="Resource Files">
	+ <UniqueIdentifier>{67DA6AB6-F800-4c08-8B7A-83BB121AAD01}</UniqueIdentifier>
	+ <Extensions>rc;ico;cur;bmp;dlg;rc2;rct;bin;rgs;gif;jpg;jpeg;jpe;resx;tiff;tif;png;wav</Extensions>
	+ </Filter>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClCompile Include="src\data.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\library.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\num.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\rand.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\vector.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ <ClCompile Include="src\vm.c">
	+ <Filter>Source Files</Filter>
	+ </ClCompile>
	+ </ItemGroup>
	+ <ItemGroup>
	+ <ClInclude Include="include\args.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\bc.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\bcl.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\dc.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\file.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\history.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\lang.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\lex.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\library.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\num.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\opt.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\parse.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\program.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\rand.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\read.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\status.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\vector.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\version.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ <ClInclude Include="include\vm.h">
	+ <Filter>Header Files</Filter>
	+ </ClInclude>
	+ </ItemGroup>
	+</Project>
	\ No newline at end of file
	diff --git a/contrib/bc/configure b/contrib/bc/configure
	deleted file mode 120000
	index bd7a56adb6f9..000000000000
	--- a/contrib/bc/configure
	+++ /dev/null
	@@ -1 +0,0 @@
	-configure.sh
	\ No newline at end of file
	diff --git a/contrib/bc/configure b/contrib/bc/configure
	new file mode 100755
	index 000000000000..af96564e7702
	--- /dev/null
	+++ b/contrib/bc/configure
	@@ -0,0 +1,1321 @@
	+#! /bin/sh
	+#
	+# SPDX-License-Identifier: BSD-2-Clause
	+#
	+# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	+#
	+# Redistribution and use in source and binary forms, with or without
	+# modification, are permitted provided that the following conditions are met:
	+#
	+# * Redistributions of source code must retain the above copyright notice, this
	+# list of conditions and the following disclaimer.
	+#
	+# * 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.
	+#
	+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	+#
	+
	+script="$0"
	+scriptdir=$(dirname "$script")
	+script=$(basename "$script")
	+
	+. "$scriptdir/functions.sh"
	+
	+cd "$scriptdir"
	+
	+usage() {
	+
	+ if [ $# -gt 0 ]; then
	+
	+ _usage_val=1
	+
	+ printf "%s\n\n" "$1"
	+
	+ else
	+ _usage_val=0
	+ fi
	+
	+ printf 'usage:\n'
	+ printf ' %s -h\n' "$script"
	+ printf ' %s --help\n' "$script"
	+ printf ' %s [-a\|-bD\|-dB\|-c] [-CEfgGHlmMNPtTvz] [-O OPT_LEVEL] [-k KARATSUBA_LEN]\n' "$script"
	+ printf ' %s \\\n' "$script"
	+ printf ' [--library\|--bc-only --disable-dc\|--dc-only --disable-bc\|--coverage]\\\n'
	+ printf ' [--force --debug --disable-extra-math --disable-generated-tests] \\\n'
	+ printf ' [--disable-history --disable-man-pages --disable-nls] \\\n'
	+ printf ' [--disable-prompt --disable-strip] [--install-all-locales] \\\n'
	+ printf ' [--opt=OPT_LEVEL] [--karatsuba-len=KARATSUBA_LEN] \\\n'
	+ printf ' [--prefix=PREFIX] [--bindir=BINDIR] [--datarootdir=DATAROOTDIR] \\\n'
	+ printf ' [--datadir=DATADIR] [--mandir=MANDIR] [--man1dir=MAN1DIR] \\\n'
	+ printf '\n'
	+ printf ' -a, --library\n'
	+ printf ' Build the libbc instead of the programs. This is meant to be used with\n'
	+ printf ' Other software like programming languages that want to make use of the\n'
	+ printf ' parsing and math capabilities. This option will install headers using\n'
	+ printf ' `make install`.\n'
	+ printf ' -b, --bc-only\n'
	+ printf ' Build bc only. It is an error if "-d", "--dc-only", "-B", or\n'
	+ printf ' "--disable-bc" are specified too.\n'
	+ printf ' -B, --disable-bc\n'
	+ printf ' Disable bc. It is an error if "-b", "--bc-only", "-D", or "--disable-dc"\n'
	+ printf ' are specified too.\n'
	+ printf ' -c, --coverage\n'
	+ printf ' Generate test coverage code. Requires gcov and regcovr.\n'
	+ printf ' It is an error if either "-b" ("-D") or "-d" ("-B") is specified.\n'
	+ printf ' Requires a compiler that use gcc-compatible coverage options\n'
	+ printf ' -C, --disable-clean\n'
	+ printf ' Disable the clean that configure.sh does before configure.\n'
	+ printf ' -d, --dc-only\n'
	+ printf ' Build dc only. It is an error if "-b", "--bc-only", "-D", or\n'
	+ printf ' "--disable-dc" are specified too.\n'
	+ printf ' -D, --disable-dc\n'
	+ printf ' Disable dc. It is an error if "-d", "--dc-only", "-B", or "--disable-bc"\n'
	+ printf ' are specified too.\n'
	+ printf ' -E, --disable-extra-math\n'
	+ printf ' Disable extra math. This includes: "$" operator (truncate to integer),\n'
	+ printf ' "@" operator (set number of decimal places), and r(x, p) (rounding\n'
	+ printf ' function). Additionally, this option disables the extra printing\n'
	+ printf ' functions in the math library.\n'
	+ printf ' -f, --force\n'
	+ printf ' Force use of all enabled options, even if they do not work. This\n'
	+ printf ' option is to allow the maintainer a way to test that certain options\n'
	+ printf ' are not failing invisibly. (Development only.)'
	+ printf ' -g, --debug\n'
	+ printf ' Build in debug mode. Adds the "-g" flag, and if there are no\n'
	+ printf ' other CFLAGS, and "-O" was not given, this also adds the "-O0"\n'
	+ printf ' flag. If this flag is not given, "-DNDEBUG" is added to CPPFLAGS\n'
	+ printf ' and a strip flag is added to the link stage.\n'
	+ printf ' -G, --disable-generated-tests\n'
	+ printf ' Disable generating tests. This is for platforms that do not have a\n'
	+ printf ' GNU bc-compatible bc to generate tests.\n'
	+ printf ' -h, --help\n'
	+ printf ' Print this help message and exit.\n'
	+ printf ' -H, --disable-history\n'
	+ printf ' Disable history.\n'
	+ printf ' -k KARATSUBA_LEN, --karatsuba-len KARATSUBA_LEN\n'
	+ printf ' Set the karatsuba length to KARATSUBA_LEN (default is 64).\n'
	+ printf ' It is an error if KARATSUBA_LEN is not a number or is less than 16.\n'
	+ printf ' -l, --install-all-locales\n'
	+ printf ' Installs all locales, regardless of how many are on the system. This\n'
	+ printf ' option is useful for package maintainers who want to make sure that\n'
	+ printf ' a package contains all of the locales that end users might need.\n'
	+ printf ' -m, --enable-memcheck\n'
	+ printf ' Enable memcheck mode, to ensure no memory leaks. For development only.\n'
	+ printf ' -M, --disable-man-pages\n'
	+ printf ' Disable installing manpages.\n'
	+ printf ' -N, --disable-nls\n'
	+ printf ' Disable POSIX locale (NLS) support.\n'
	+ printf ' -O OPT_LEVEL, --opt OPT_LEVEL\n'
	+ printf ' Set the optimization level. This can also be included in the CFLAGS,\n'
	+ printf ' but it is provided, so maintainers can build optimized debug builds.\n'
	+ printf ' This is passed through to the compiler, so it must be supported.\n'
	+ printf ' -P, --disable-prompt\n'
	+ printf ' Disables the prompt in the built bc. The prompt will never show up,\n'
	+ printf ' or in other words, it will be permanently disabled and cannot be\n'
	+ printf ' enabled.\n'
	+ printf ' -t, --enable-test-timing\n'
	+ printf ' Enable the timing of tests. This is for development only.\n'
	+ printf ' -T, --disable-strip\n'
	+ printf ' Disable stripping symbols from the compiled binary or binaries.\n'
	+ printf ' Stripping symbols only happens when debug mode is off.\n'
	+ printf ' -v, --enable-valgrind\n'
	+ printf ' Enable a build appropriate for valgrind. For development only.\n'
	+ printf ' -z, --enable-fuzz-mode\n'
	+ printf ' Enable fuzzing mode. THIS IS FOR DEVELOPMENT ONLY.\n'
	+ printf ' --prefix PREFIX\n'
	+ printf ' The prefix to install to. Overrides "$PREFIX" if it exists.\n'
	+ printf ' If PREFIX is "/usr", install path will be "/usr/bin".\n'
	+ printf ' Default is "/usr/local".\n'
	+ printf ' --bindir BINDIR\n'
	+ printf ' The directory to install binaries in. Overrides "$BINDIR" if it exists.\n'
	+ printf ' Default is "$PREFIX/bin".\n'
	+ printf ' --includedir INCLUDEDIR\n'
	+ printf ' The directory to install headers in. Overrides "$INCLUDEDIR" if it\n'
	+ printf ' exists. Default is "$PREFIX/include".\n'
	+ printf ' --libdir LIBDIR\n'
	+ printf ' The directory to install libraries in. Overrides "$LIBDIR" if it exists.\n'
	+ printf ' Default is "$PREFIX/lib".\n'
	+ printf ' --datarootdir DATAROOTDIR\n'
	+ printf ' The root location for data files. Overrides "$DATAROOTDIR" if it exists.\n'
	+ printf ' Default is "$PREFIX/share".\n'
	+ printf ' --datadir DATADIR\n'
	+ printf ' The location for data files. Overrides "$DATADIR" if it exists.\n'
	+ printf ' Default is "$DATAROOTDIR".\n'
	+ printf ' --mandir MANDIR\n'
	+ printf ' The location to install manpages to. Overrides "$MANDIR" if it exists.\n'
	+ printf ' Default is "$DATADIR/man".\n'
	+ printf ' --man1dir MAN1DIR\n'
	+ printf ' The location to install Section 1 manpages to. Overrides "$MAN1DIR" if\n'
	+ printf ' it exists. Default is "$MANDIR/man1".\n'
	+ printf ' --man3dir MAN3DIR\n'
	+ printf ' The location to install Section 3 manpages to. Overrides "$MAN3DIR" if\n'
	+ printf ' it exists. Default is "$MANDIR/man3".\n'
	+ printf '\n'
	+ printf 'In addition, the following environment variables are used:\n'
	+ printf '\n'
	+ printf ' CC C compiler. Must be compatible with POSIX c99. If there is a\n'
	+ printf ' space in the basename of the compiler, the items after the\n'
	+ printf ' first space are assumed to be compiler flags, and in that case,\n'
	+ printf ' the flags are automatically moved into CFLAGS. Default is\n'
	+ printf ' "c99".\n'
	+ printf ' HOSTCC Host C compiler. Must be compatible with POSIX c99. If there is\n'
	+ printf ' a space in the basename of the compiler, the items after the\n'
	+ printf ' first space are assumed to be compiler flags, and in the case,\n'
	+ printf ' the flags are automatically moved into HOSTCFLAGS. Default is\n'
	+ printf ' "$CC".\n'
	+ printf ' HOST_CC Same as HOSTCC. If HOSTCC also exists, it is used.\n'
	+ printf ' CFLAGS C compiler flags.\n'
	+ printf ' HOSTCFLAGS CFLAGS for HOSTCC. Default is "$CFLAGS".\n'
	+ printf ' HOST_CFLAGS Same as HOST_CFLAGS. If HOST_CFLAGS also exists, it is used.\n'
	+ printf ' CPPFLAGS C preprocessor flags. Default is "".\n'
	+ printf ' LDFLAGS Linker flags. Default is "".\n'
	+ printf ' PREFIX The prefix to install to. Default is "/usr/local".\n'
	+ printf ' If PREFIX is "/usr", install path will be "/usr/bin".\n'
	+ printf ' BINDIR The directory to install binaries in. Default is "$PREFIX/bin".\n'
	+ printf ' INCLUDEDIR The directory to install header files in. Default is\n'
	+ printf ' "$PREFIX/include".\n'
	+ printf ' LIBDIR The directory to install libraries in. Default is\n'
	+ printf ' "$PREFIX/lib".\n'
	+ printf ' DATAROOTDIR The root location for data files. Default is "$PREFIX/share".\n'
	+ printf ' DATADIR The location for data files. Default is "$DATAROOTDIR".\n'
	+ printf ' MANDIR The location to install manpages to. Default is "$DATADIR/man".\n'
	+ printf ' MAN1DIR The location to install Section 1 manpages to. Default is\n'
	+ printf ' "$MANDIR/man1".\n'
	+ printf ' MAN3DIR The location to install Section 3 manpages to. Default is\n'
	+ printf ' "$MANDIR/man3".\n'
	+ printf ' NLSPATH The location to install locale catalogs to. Must be an absolute\n'
	+ printf ' path (or contain one). This is treated the same as the POSIX\n'
	+ printf ' definition of $NLSPATH (see POSIX environment variables for\n'
	+ printf ' more information). Default is "/usr/share/locale/%%L/%%N".\n'
	+ printf ' EXECSUFFIX The suffix to append to the executable names, used to not\n'
	+ printf ' interfere with other installed bc executables. Default is "".\n'
	+ printf ' EXECPREFIX The prefix to append to the executable names, used to not\n'
	+ printf ' interfere with other installed bc executables. Default is "".\n'
	+ printf ' DESTDIR For package creation. Default is "". If it is empty when\n'
	+ printf ' `%s` is run, it can also be passed to `make install`\n' "$script"
	+ printf ' later as an environment variable. If both are specified,\n'
	+ printf ' the one given to `%s` takes precedence.\n' "$script"
	+ printf ' LONG_BIT The number of bits in a C `long` type. This is mostly for the\n'
	+ printf ' embedded space since this `bc` uses `long`s internally for\n'
	+ printf ' overflow checking. In C99, a `long` is required to be 32 bits.\n'
	+ printf ' For most normal desktop systems, setting this is unnecessary,\n'
	+ printf ' except that 32-bit platforms with 64-bit longs may want to set\n'
	+ printf ' it to `32`. Default is the default of `LONG_BIT` for the target\n'
	+ printf ' platform. Minimum allowed is `32`. It is a build time error if\n'
	+ printf ' the specified value of `LONG_BIT` is greater than the default\n'
	+ printf ' value of `LONG_BIT` for the target platform.\n'
	+ printf ' GEN_HOST Whether to use `gen/strgen.c`, instead of `gen/strgen.sh`, to\n'
	+ printf ' produce the C files that contain the help texts as well as the\n'
	+ printf ' math libraries. By default, `gen/strgen.c` is used, compiled by\n'
	+ printf ' "$HOSTCC" and run on the host machine. Using `gen/strgen.sh`\n'
	+ printf ' removes the need to compile and run an executable on the host\n'
	+ printf ' machine since `gen/strgen.sh` is a POSIX shell script. However,\n'
	+ printf ' `gen/lib2.bc` is perilously close to 4095 characters, the max\n'
	+ printf ' supported length of a string literal in C99 (and it could be\n'
	+ printf ' added to in the future), and `gen/strgen.sh` generates a string\n'
	+ printf ' literal instead of an array, as `gen/strgen.c` does. For most\n'
	+ printf ' production-ready compilers, this limit probably is not\n'
	+ printf ' enforced, but it could be. Both options are still available for\n'
	+ printf ' this reason. If you are sure your compiler does not have the\n'
	+ printf ' limit and do not want to compile and run a binary on the host\n'
	+ printf ' machine, set this variable to "0". Any other value, or a\n'
	+ printf ' non-existent value, will cause the build system to compile and\n'
	+ printf ' run `gen/strgen.c`. Default is "".\n'
	+ printf ' GEN_EMU Emulator to run string generator code under (leave empty if not\n'
	+ printf ' necessary). This is not necessary when using `gen/strgen.sh`.\n'
	+ printf ' Default is "".\n'
	+ printf '\n'
	+ printf 'WARNING: even though `configure.sh` supports both option types, short and\n'
	+ printf 'long, it does not support handling both at the same time. Use only one type.\n'
	+
	+ exit "$_usage_val"
	+}
	+
	+replace_ext() {
	+
	+ if [ "$#" -ne 3 ]; then
	+ err_exit "Invalid number of args to $0"
	+ fi
	+
	+ _replace_ext_file="$1"
	+ _replace_ext_ext1="$2"
	+ _replace_ext_ext2="$3"
	+
	+ _replace_ext_result="${_replace_ext_file%.$_replace_ext_ext1}.$_replace_ext_ext2"
	+
	+ printf '%s\n' "$_replace_ext_result"
	+}
	+
	+replace_exts() {
	+
	+ if [ "$#" -ne 3 ]; then
	+ err_exit "Invalid number of args to $0"
	+ fi
	+
	+ _replace_exts_files="$1"
	+ _replace_exts_ext1="$2"
	+ _replace_exts_ext2="$3"
	+
	+ for _replace_exts_file in $_replace_exts_files; do
	+ _replace_exts_new_name=$(replace_ext "$_replace_exts_file" "$_replace_exts_ext1" "$_replace_exts_ext2")
	+ _replace_exts_result="$_replace_exts_result $_replace_exts_new_name"
	+ done
	+
	+ printf '%s\n' "$_replace_exts_result"
	+}
	+
	+replace() {
	+
	+ if [ "$#" -ne 3 ]; then
	+ err_exit "Invalid number of args to $0"
	+ fi
	+
	+ _replace_str="$1"
	+ _replace_needle="$2"
	+ _replace_replacement="$3"
	+
	+ substring_replace "$_replace_str" "%%$_replace_needle%%" "$_replace_replacement"
	+}
	+
	+find_src_files() {
	+
	+ if [ "$#" -ge 1 ] && [ "$1" != "" ]; then
	+
	+ while [ "$#" -ge 1 ]; do
	+ _find_src_files_a="${1## }"
	+ shift
	+ _find_src_files_args="$_find_src_files_args ! -path src/${_find_src_files_a}"
	+ done
	+
	+ else
	+ _find_src_files_args="-print"
	+ fi
	+
	+ printf '%s\n' $(find src/ -depth -name "*.c" $_find_src_files_args)
	+}
	+
	+gen_file_list() {
	+
	+ if [ "$#" -lt 1 ]; then
	+ err_exit "Invalid number of args to $0"
	+ fi
	+
	+ _gen_file_list_contents="$1"
	+ shift
	+
	+ p=$(pwd)
	+
	+ cd "$scriptdir"
	+
	+ if [ "$#" -ge 1 ]; then
	+ _gen_file_list_unneeded="$@"
	+ else
	+ _gen_file_list_unneeded=""
	+ fi
	+
	+ _gen_file_list_needle_src="SRC"
	+ _gen_file_list_needle_obj="OBJ"
	+ _gen_file_list_needle_gcda="GCDA"
	+ _gen_file_list_needle_gcno="GCNO"
	+
	+ _gen_file_list_replacement=$(find_src_files $_gen_file_list_unneeded \| tr '\n' ' ')
	+ _gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	+ "$_gen_file_list_needle_src" "$_gen_file_list_replacement")
	+
	+ _gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "c" "o")
	+ _gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	+ "$_gen_file_list_needle_obj" "$_gen_file_list_replacement")
	+
	+ _gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "o" "gcda")
	+ _gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	+ "$_gen_file_list_needle_gcda" "$_gen_file_list_replacement")
	+
	+ _gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "gcda" "gcno")
	+ _gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	+ "$_gen_file_list_needle_gcno" "$_gen_file_list_replacement")
	+
	+ cd "$p"
	+
	+ printf '%s\n' "$_gen_file_list_contents"
	+}
	+
	+gen_tests() {
	+
	+ _gen_tests_name="$1"
	+ shift
	+
	+ _gen_tests_uname="$1"
	+ shift
	+
	+ _gen_tests_extra_math="$1"
	+ shift
	+
	+ _gen_tests_time_tests="$1"
	+ shift
	+
	+ _gen_tests_extra_required=$(cat tests/extra_required.txt)
	+
	+ for _gen_tests_t in $(cat "$scriptdir/tests/$_gen_tests_name/all.txt"); do
	+
	+ if [ "$_gen_tests_extra_math" -eq 0 ]; then
	+
	+ if [ -z "${_gen_tests_extra_required##$_gen_tests_t}" ]; then
	+ printf 'test_%s_%s:\n\t@printf "Skipping %s %s\\n"\n\n' \
	+ "$_gen_tests_name" "$_gen_tests_t" "$_gen_tests_name" \
	+ "$_gen_tests_t" >> "$scriptdir/Makefile"
	+ continue
	+ fi
	+
	+ fi
	+
	+ printf 'test_%s_%s:\n\t@sh tests/test.sh %s %s %s %s %s\n\n' \
	+ "$_gen_tests_name" "$_gen_tests_t" "$_gen_tests_name" \
	+ "$_gen_tests_t" "$generate_tests" "$time_tests" \
	+ "$*" >> "$scriptdir/Makefile"
	+
	+ done
	+}
	+
	+gen_test_targets() {
	+
	+ _gen_test_targets_name="$1"
	+ shift
	+
	+ _gen_test_targets_tests=$(cat "$scriptdir/tests/${_gen_test_targets_name}/all.txt")
	+
	+ for _gen_test_targets_t in $_gen_test_targets_tests; do
	+ printf ' test_%s_%s' "$_gen_test_targets_name" "$_gen_test_targets_t"
	+ done
	+
	+ printf '\n'
	+}
	+
	+gen_script_tests() {
	+
	+ _gen_script_tests_name="$1"
	+ shift
	+
	+ _gen_script_tests_extra_math="$1"
	+ shift
	+
	+ _gen_script_tests_generate="$1"
	+ shift
	+
	+ _gen_script_tests_time="$1"
	+ shift
	+
	+ _gen_script_tests_tests=$(cat "$scriptdir/tests/$_gen_script_tests_name/scripts/all.txt")
	+
	+ for _gen_script_tests_f in $_gen_script_tests_tests; do
	+
	+ _gen_script_tests_b=$(basename "$_gen_script_tests_f" ".${_gen_script_tests_name}")
	+
	+ printf 'test_%s_script_%s:\n\t@sh tests/script.sh %s %s %s 1 %s %s %s\n\n' \
	+ "$_gen_script_tests_name" "$_gen_script_tests_b" "$_gen_script_tests_name" \
	+ "$_gen_script_tests_f" "$_gen_script_tests_extra_math" "$_gen_script_tests_generate" \
	+ "$_gen_script_tests_time" "$*" >> "$scriptdir/Makefile"
	+ done
	+}
	+
	+gen_script_test_targets() {
	+
	+ _gen_script_test_targets_name="$1"
	+ shift
	+
	+ _gen_script_test_targets_tests=$(cat "$scriptdir/tests/$_gen_script_test_targets_name/scripts/all.txt")
	+
	+ for _gen_script_test_targets_f in $_gen_script_test_targets_tests; do
	+ _gen_script_test_targets_b=$(basename "$_gen_script_test_targets_f" \
	+ ".$_gen_script_test_targets_name")
	+ printf ' test_%s_script_%s' "$_gen_script_test_targets_name" \
	+ "$_gen_script_test_targets_b"
	+ done
	+
	+ printf '\n'
	+}
	+
	+bc_only=0
	+dc_only=0
	+coverage=0
	+karatsuba_len=32
	+debug=0
	+hist=1
	+extra_math=1
	+optimization=""
	+generate_tests=1
	+install_manpages=1
	+nls=1
	+prompt=1
	+force=0
	+strip_bin=1
	+all_locales=0
	+library=0
	+fuzz=0
	+time_tests=0
	+vg=0
	+memcheck=0
	+clean=1
	+
	+while getopts "abBcdDEfgGhHk:lMmNO:PStTvz-" opt; do
	+
	+ case "$opt" in
	+ a) library=1 ;;
	+ b) bc_only=1 ;;
	+ B) dc_only=1 ;;
	+ c) coverage=1 ;;
	+ C) clean=0 ;;
	+ d) dc_only=1 ;;
	+ D) bc_only=1 ;;
	+ E) extra_math=0 ;;
	+ f) force=1 ;;
	+ g) debug=1 ;;
	+ G) generate_tests=0 ;;
	+ h) usage ;;
	+ H) hist=0 ;;
	+ k) karatsuba_len="$OPTARG" ;;
	+ l) all_locales=1 ;;
	+ m) memcheck=1 ;;
	+ M) install_manpages=0 ;;
	+ N) nls=0 ;;
	+ O) optimization="$OPTARG" ;;
	+ P) prompt=0 ;;
	+ t) time_tests=1 ;;
	+ T) strip_bin=0 ;;
	+ v) vg=1 ;;
	+ z) fuzz=1 ;;
	+ -)
	+ arg="$1"
	+ arg="${arg#--}"
	+ LONG_OPTARG="${arg#*=}"
	+ case $arg in
	+ help) usage ;;
	+ library) library=1 ;;
	+ bc-only) bc_only=1 ;;
	+ dc-only) dc_only=1 ;;
	+ coverage) coverage=1 ;;
	+ debug) debug=1 ;;
	+ force) force=1 ;;
	+ prefix=?*) PREFIX="$LONG_OPTARG" ;;
	+ prefix)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ PREFIX="$2"
	+ shift ;;
	+ bindir=?*) BINDIR="$LONG_OPTARG" ;;
	+ bindir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ BINDIR="$2"
	+ shift ;;
	+ includedir=?*) INCLUDEDIR="$LONG_OPTARG" ;;
	+ includedir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ INCLUDEDIR="$2"
	+ shift ;;
	+ libdir=?*) LIBDIR="$LONG_OPTARG" ;;
	+ libdir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ LIBDIR="$2"
	+ shift ;;
	+ datarootdir=?*) DATAROOTDIR="$LONG_OPTARG" ;;
	+ datarootdir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ DATAROOTDIR="$2"
	+ shift ;;
	+ datadir=?*) DATADIR="$LONG_OPTARG" ;;
	+ datadir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ DATADIR="$2"
	+ shift ;;
	+ mandir=?*) MANDIR="$LONG_OPTARG" ;;
	+ mandir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ MANDIR="$2"
	+ shift ;;
	+ man1dir=?*) MAN1DIR="$LONG_OPTARG" ;;
	+ man1dir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ MAN1DIR="$2"
	+ shift ;;
	+ man3dir=?*) MAN3DIR="$LONG_OPTARG" ;;
	+ man3dir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ MAN3DIR="$2"
	+ shift ;;
	+ localedir=?*) LOCALEDIR="$LONG_OPTARG" ;;
	+ localedir)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ LOCALEDIR="$2"
	+ shift ;;
	+ karatsuba-len=?*) karatsuba_len="$LONG_OPTARG" ;;
	+ karatsuba-len)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ karatsuba_len="$1"
	+ shift ;;
	+ opt=?*) optimization="$LONG_OPTARG" ;;
	+ opt)
	+ if [ "$#" -lt 2 ]; then
	+ usage "No argument given for '--$arg' option"
	+ fi
	+ optimization="$1"
	+ shift ;;
	+ disable-bc) dc_only=1 ;;
	+ disable-dc) bc_only=1 ;;
	+ disable-clean) clean=0 ;;
	+ disable-extra-math) extra_math=0 ;;
	+ disable-generated-tests) generate_tests=0 ;;
	+ disable-history) hist=0 ;;
	+ disable-man-pages) install_manpages=0 ;;
	+ disable-nls) nls=0 ;;
	+ disable-prompt) prompt=0 ;;
	+ disable-strip) strip_bin=0 ;;
	+ enable-test-timing) time_tests=1 ;;
	+ enable-valgrind) vg=1 ;;
	+ enable-fuzz-mode) fuzz=1 ;;
	+ enable-memcheck) memcheck=1 ;;
	+ install-all-locales) all_locales=1 ;;
	+ help* \| bc-only* \| dc-only* \| coverage* \| debug*)
	+ usage "No arg allowed for --$arg option" ;;
	+ disable-bc* \| disable-dc* \| disable-clean*)
	+ usage "No arg allowed for --$arg option" ;;
	+ disable-extra-math*)
	+ usage "No arg allowed for --$arg option" ;;
	+ disable-generated-tests* \| disable-history*)
	+ usage "No arg allowed for --$arg option" ;;
	+ disable-man-pages* \| disable-nls* \| disable-strip*)
	+ usage "No arg allowed for --$arg option" ;;
	+ enable-fuzz-mode* \| enable-test-timing* \| enable-valgrind*)
	+ usage "No arg allowed for --$arg option" ;;
	+ enable-memcheck* \| install-all-locales*)
	+ usage "No arg allowed for --$arg option" ;;
	+ '') break ;; # "--" terminates argument processing
	+ * ) usage "Invalid option $LONG_OPTARG" ;;
	+ esac
	+ shift
	+ OPTIND=1 ;;
	+ ?) usage "Invalid option $opt" ;;
	+ esac
	+
	+done
	+
	+if [ "$clean" -ne 0 ]; then
	+ if [ -f ./Makefile ]; then
	+ make clean_config > /dev/null
	+ fi
	+fi
	+
	+if [ "$bc_only" -eq 1 ] && [ "$dc_only" -eq 1 ]; then
	+ usage "Can only specify one of -b(-D) or -d(-B)"
	+fi
	+
	+if [ "$library" -ne 0 ]; then
	+ if [ "$bc_only" -eq 1 ] \|\| [ "$dc_only" -eq 1 ]; then
	+ usage "Must not specify -b(-D) or -d(-B) when building the library"
	+ fi
	+fi
	+
	+case $karatsuba_len in
	+ ([!0-9]\|'') usage "KARATSUBA_LEN is not a number" ;;
	+ (*) ;;
	+esac
	+
	+if [ "$karatsuba_len" -lt 16 ]; then
	+ usage "KARATSUBA_LEN is less than 16"
	+fi
	+
	+set -e
	+
	+if [ -z "${LONG_BIT+set}" ]; then
	+ LONG_BIT_DEFINE=""
	+elif [ "$LONG_BIT" -lt 32 ]; then
	+ usage "LONG_BIT is less than 32"
	+else
	+ LONG_BIT_DEFINE="-DBC_LONG_BIT=\$(BC_LONG_BIT)"
	+fi
	+
	+if [ -z "$CC" ]; then
	+ CC="c99"
	+else
	+ ccbase=$(basename "$CC")
	+ suffix=" *"
	+ prefix="* "
	+
	+ if [ "${ccbase%%$suffix}" != "$ccbase" ]; then
	+ ccflags="${ccbase#$prefix}"
	+ cc="${ccbase%%$suffix}"
	+ ccdir=$(dirname "$CC")
	+ if [ "$ccdir" = "." ] && [ "${CC#.}" = "$CC" ]; then
	+ ccdir=""
	+ else
	+ ccdir="$ccdir/"
	+ fi
	+ CC="${ccdir}${cc}"
	+ CFLAGS="$CFLAGS $ccflags"
	+ fi
	+fi
	+
	+if [ -z "$HOSTCC" ] && [ -z "$HOST_CC" ]; then
	+ HOSTCC="$CC"
	+elif [ -z "$HOSTCC" ]; then
	+ HOSTCC="$HOST_CC"
	+fi
	+
	+if [ "$HOSTCC" != "$CC" ]; then
	+ ccbase=$(basename "$HOSTCC")
	+ suffix=" *"
	+ prefix="* "
	+
	+ if [ "${ccbase%%$suffix}" != "$ccbase" ]; then
	+ ccflags="${ccbase#$prefix}"
	+ cc="${ccbase%%$suffix}"
	+ ccdir=$(dirname "$HOSTCC")
	+ if [ "$ccdir" = "." ] && [ "${HOSTCC#.}" = "$HOSTCC" ]; then
	+ ccdir=""
	+ else
	+ ccdir="$ccdir/"
	+ fi
	+ HOSTCC="${ccdir}${cc}"
	+ HOSTCFLAGS="$HOSTCFLAGS $ccflags"
	+ fi
	+fi
	+
	+if [ -z "${HOSTCFLAGS+set}" ] && [ -z "${HOST_CFLAGS+set}" ]; then
	+ HOSTCFLAGS="$CFLAGS"
	+elif [ -z "${HOSTCFLAGS+set}" ]; then
	+ HOSTCFLAGS="$HOST_CFLAGS"
	+fi
	+
	+link="@printf 'No link necessary\\\\n'"
	+main_exec="BC"
	+executable="BC_EXEC"
	+
	+tests="test_bc timeconst test_dc"
	+
	+bc_test="@tests/all.sh bc $extra_math 1 $generate_tests 0 \$(BC_EXEC)"
	+dc_test="@tests/all.sh dc $extra_math 1 $generate_tests 0 \$(DC_EXEC)"
	+
	+timeconst="@tests/bc/timeconst.sh tests/bc/scripts/timeconst.bc \$(BC_EXEC)"
	+
	+# In order to have cleanup at exit, we need to be in
	+# debug mode, so don't run valgrind without that.
	+if [ "$vg" -ne 0 ]; then
	+ debug=1
	+ bc_test_exec='valgrind $(VALGRIND_ARGS) $(BC_EXEC)'
	+ dc_test_exec='valgrind $(VALGRIND_ARGS) $(DC_EXEC)'
	+else
	+ bc_test_exec='$(BC_EXEC)'
	+ dc_test_exec='$(DC_EXEC)'
	+fi
	+
	+karatsuba="@printf 'karatsuba cannot be run because one of bc or dc is not built\\\\n'"
	+karatsuba_test="@printf 'karatsuba cannot be run because one of bc or dc is not built\\\\n'"
	+
	+bc_lib="\$(GEN_DIR)/lib.o"
	+bc_help="\$(GEN_DIR)/bc_help.o"
	+dc_help="\$(GEN_DIR)/dc_help.o"
	+
	+default_target_prereqs="\$(BIN) \$(OBJS)"
	+default_target_cmd="\$(CC) \$(CFLAGS) \$(OBJS) \$(LDFLAGS) -o \$(EXEC)"
	+default_target="\$(DC_EXEC)"
	+
	+second_target_prereqs=""
	+second_target_cmd="$default_target_cmd"
	+second_target="\$(BC_EXEC)"
	+
	+if [ "$library" -ne 0 ]; then
	+
	+ extra_math=1
	+ nls=0
	+ hist=0
	+ prompt=0
	+ bc=1
	+ dc=1
	+
	+ default_target_prereqs="\$(BIN) \$(OBJ)"
	+ default_target_cmd="ar -r -cu \$(LIBBC) \$(OBJ)"
	+ default_target="\$(LIBBC)"
	+ tests="test_library"
	+
	+elif [ "$bc_only" -eq 1 ]; then
	+
	+ bc=1
	+ dc=0
	+
	+ dc_help=""
	+
	+ executables="bc"
	+
	+ dc_test="@printf 'No dc tests to run\\\\n'"
	+
	+ install_prereqs=" install_execs"
	+ install_man_prereqs=" install_bc_manpage"
	+ uninstall_prereqs=" uninstall_bc"
	+ uninstall_man_prereqs=" uninstall_bc_manpage"
	+
	+ default_target="\$(BC_EXEC)"
	+ second_target="\$(DC_EXEC)"
	+ tests="test_bc timeconst"
	+
	+elif [ "$dc_only" -eq 1 ]; then
	+
	+ bc=0
	+ dc=1
	+
	+ bc_lib=""
	+ bc_help=""
	+
	+ executables="dc"
	+
	+ main_exec="DC"
	+ executable="DC_EXEC"
	+
	+ bc_test="@printf 'No bc tests to run\\\\n'"
	+
	+ timeconst="@printf 'timeconst cannot be run because bc is not built\\\\n'"
	+
	+ install_prereqs=" install_execs"
	+ install_man_prereqs=" install_dc_manpage"
	+ uninstall_prereqs=" uninstall_dc"
	+ uninstall_man_prereqs=" uninstall_dc_manpage"
	+
	+ tests="test_dc"
	+
	+else
	+
	+ bc=1
	+ dc=1
	+
	+ executables="bc and dc"
	+
	+ karatsuba="@\$(KARATSUBA) 30 0 \$(BC_EXEC)"
	+ karatsuba_test="@\$(KARATSUBA) 1 100 \$(BC_EXEC)"
	+
	+ if [ "$library" -eq 0 ]; then
	+ install_prereqs=" install_execs"
	+ install_man_prereqs=" install_bc_manpage install_dc_manpage"
	+ uninstall_prereqs=" uninstall_bc uninstall_dc"
	+ uninstall_man_prereqs=" uninstall_bc_manpage uninstall_dc_manpage"
	+ else
	+ install_prereqs=" install_library install_bcl_header"
	+ install_man_prereqs=" install_bcl_manpage"
	+ uninstall_prereqs=" uninstall_library uninstall_bcl_header"
	+ uninstall_man_prereqs=" uninstall_bcl_manpage"
	+ tests="test_library"
	+ fi
	+
	+ second_target_prereqs="$default_target_prereqs"
	+ default_target_prereqs="$second_target"
	+ default_target_cmd="\$(LINK) \$(BIN) \$(EXEC_PREFIX)\$(DC)"
	+
	+fi
	+
	+if [ "$fuzz" -ne 0 ]; then
	+ debug=1
	+ hist=0
	+ prompt=0
	+ nls=0
	+ optimization="3"
	+fi
	+
	+if [ "$debug" -eq 1 ]; then
	+
	+ if [ -z "$CFLAGS" ] && [ -z "$optimization" ]; then
	+ CFLAGS="-O0"
	+ fi
	+
	+ CFLAGS="-g $CFLAGS"
	+
	+else
	+ CPPFLAGS="-DNDEBUG $CPPFLAGS"
	+ if [ "$strip_bin" -ne 0 ]; then
	+ LDFLAGS="-s $LDFLAGS"
	+ fi
	+fi
	+
	+if [ -n "$optimization" ]; then
	+ CFLAGS="-O$optimization $CFLAGS"
	+fi
	+
	+if [ "$coverage" -eq 1 ]; then
	+
	+ if [ "$bc_only" -eq 1 ] \|\| [ "$dc_only" -eq 1 ]; then
	+ usage "Can only specify -c without -b or -d"
	+ fi
	+
	+ CFLAGS="-fprofile-arcs -ftest-coverage -g -O0 $CFLAGS"
	+ CPPFLAGS="-DNDEBUG $CPPFLAGS"
	+
	+ COVERAGE_OUTPUT="@gcov -pabcdf \$(GCDA) \$(BC_GCDA) \$(DC_GCDA) \$(HISTORY_GCDA) \$(RAND_GCDA)"
	+ COVERAGE_OUTPUT="$COVERAGE_OUTPUT;\$(RM) -f \$(GEN).gc"
	+ COVERAGE_OUTPUT="$COVERAGE_OUTPUT;gcovr --html-details --output index.html"
	+ COVERAGE_PREREQS=" test coverage_output"
	+
	+else
	+ COVERAGE_OUTPUT="@printf 'Coverage not generated\\\\n'"
	+ COVERAGE_PREREQS=""
	+fi
	+
	+if [ -z "${DESTDIR+set}" ]; then
	+ destdir=""
	+else
	+ destdir="DESTDIR = $DESTDIR"
	+fi
	+
	+if [ -z "${PREFIX+set}" ]; then
	+ PREFIX="/usr/local"
	+fi
	+
	+if [ -z "${BINDIR+set}" ]; then
	+ BINDIR="$PREFIX/bin"
	+fi
	+
	+if [ -z "${INCLUDEDIR+set}" ]; then
	+ INCLUDEDIR="$PREFIX/include"
	+fi
	+
	+if [ -z "${LIBDIR+set}" ]; then
	+ LIBDIR="$PREFIX/lib"
	+fi
	+
	+if [ "$install_manpages" -ne 0 ] \|\| [ "$nls" -ne 0 ]; then
	+ if [ -z "${DATAROOTDIR+set}" ]; then
	+ DATAROOTDIR="$PREFIX/share"
	+ fi
	+fi
	+
	+if [ "$install_manpages" -ne 0 ]; then
	+
	+ if [ -z "${DATADIR+set}" ]; then
	+ DATADIR="$DATAROOTDIR"
	+ fi
	+
	+ if [ -z "${MANDIR+set}" ]; then
	+ MANDIR="$DATADIR/man"
	+ fi
	+
	+ if [ -z "${MAN1DIR+set}" ]; then
	+ MAN1DIR="$MANDIR/man1"
	+ fi
	+
	+ if [ -z "${MAN3DIR+set}" ]; then
	+ MAN3DIR="$MANDIR/man3"
	+ fi
	+
	+else
	+ install_man_prereqs=""
	+ uninstall_man_prereqs=""
	+fi
	+
	+if [ "$nls" -ne 0 ]; then
	+
	+ set +e
	+
	+ printf 'Testing NLS...\n'
	+
	+ flags="-DBC_ENABLE_NLS=1 -DBC_ENABLED=$bc -DDC_ENABLED=$dc"
	+ flags="$flags -DBC_ENABLE_HISTORY=$hist"
	+ flags="$flags -DBC_ENABLE_EXTRA_MATH=$extra_math -I./include/"
	+ flags="$flags -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700"
	+
	+ "$CC" $CPPFLAGS $CFLAGS $flags -c "src/vm.c" -o "$scriptdir/vm.o" > /dev/null 2>&1
	+
	+ err="$?"
	+
	+ rm -rf "$scriptdir/vm.o"
	+
	+ # If this errors, it is probably because of building on Windows,
	+ # and NLS is not supported on Windows, so disable it.
	+ if [ "$err" -ne 0 ]; then
	+ printf 'NLS does not work.\n'
	+ if [ $force -eq 0 ]; then
	+ printf 'Disabling NLS...\n\n'
	+ nls=0
	+ else
	+ printf 'Forcing NLS...\n\n'
	+ fi
	+ else
	+ printf 'NLS works.\n\n'
	+
	+ printf 'Testing gencat...\n'
	+ gencat "$scriptdir/en_US.cat" "$scriptdir/locales/en_US.msg" > /dev/null 2>&1
	+
	+ err="$?"
	+
	+ rm -rf "$scriptdir/en_US.cat"
	+
	+ if [ "$err" -ne 0 ]; then
	+ printf 'gencat does not work.\n'
	+ if [ $force -eq 0 ]; then
	+ printf 'Disabling NLS...\n\n'
	+ nls=0
	+ else
	+ printf 'Forcing NLS...\n\n'
	+ fi
	+ else
	+
	+ printf 'gencat works.\n\n'
	+
	+ if [ "$HOSTCC" != "$CC" ]; then
	+ printf 'Cross-compile detected.\n\n'
	+ printf 'WARNING: Catalog files generated with gencat may not be portable\n'
	+ printf ' across different architectures.\n\n'
	+ fi
	+
	+ if [ -z "$NLSPATH" ]; then
	+ NLSPATH="/usr/share/locale/%L/%N"
	+ fi
	+
	+ install_locales_prereqs=" install_locales"
	+ uninstall_locales_prereqs=" uninstall_locales"
	+
	+ fi
	+
	+ fi
	+
	+ set -e
	+
	+else
	+ install_locales_prereqs=""
	+ uninstall_locales_prereqs=""
	+ all_locales=0
	+fi
	+
	+if [ "$nls" -ne 0 ] && [ "$all_locales" -ne 0 ]; then
	+ install_locales="\$(LOCALE_INSTALL) -l \$(NLSPATH) \$(MAIN_EXEC) \$(DESTDIR)"
	+else
	+ install_locales="\$(LOCALE_INSTALL) \$(NLSPATH) \$(MAIN_EXEC) \$(DESTDIR)"
	+fi
	+
	+if [ "$hist" -eq 1 ]; then
	+
	+ set +e
	+
	+ printf 'Testing history...\n'
	+
	+ flags="-DBC_ENABLE_HISTORY=1 -DBC_ENABLED=$bc -DDC_ENABLED=$dc"
	+ flags="$flags -DBC_ENABLE_NLS=$nls -DBC_ENABLE_LIBRARY=0"
	+ flags="$flags -DBC_ENABLE_EXTRA_MATH=$extra_math -I./include/"
	+ flags="$flags -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700"
	+
	+ "$CC" $CPPFLAGS $CFLAGS $flags -c "src/history.c" -o "$scriptdir/history.o" > /dev/null 2>&1
	+
	+ err="$?"
	+
	+ rm -rf "$scriptdir/history.o"
	+
	+ # If this errors, it is probably because of building on Windows,
	+ # and history is not supported on Windows, so disable it.
	+ if [ "$err" -ne 0 ]; then
	+ printf 'History does not work.\n'
	+ if [ $force -eq 0 ]; then
	+ printf 'Disabling history...\n\n'
	+ hist=0
	+ else
	+ printf 'Forcing history...\n\n'
	+ fi
	+ else
	+ printf 'History works.\n\n'
	+ fi
	+
	+ set -e
	+
	+fi
	+
	+if [ "$library" -eq 1 ]; then
	+ bc_lib=""
	+fi
	+
	+if [ "$extra_math" -eq 1 ] && [ "$bc" -ne 0 ] && [ "$library" -eq 0 ]; then
	+ BC_LIB2_O="\$(GEN_DIR)/lib2.o"
	+else
	+ BC_LIB2_O=""
	+fi
	+
	+GEN="strgen"
	+GEN_EXEC_TARGET="\$(HOSTCC) \$(HOSTCFLAGS) -o \$(GEN_EXEC) \$(GEN_C)"
	+CLEAN_PREREQS=" clean_gen"
	+
	+if [ -z "${GEN_HOST+set}" ]; then
	+ GEN_HOST=1
	+else
	+ if [ "$GEN_HOST" -eq 0 ]; then
	+ GEN="strgen.sh"
	+ GEN_EXEC_TARGET="@printf 'Do not need to build gen/strgen.c\\\\n'"
	+ CLEAN_PREREQS=""
	+ fi
	+fi
	+
	+manpage_args=""
	+unneeded=""
	+headers="\$(HEADERS)"
	+
	+if [ "$extra_math" -eq 0 ]; then
	+ manpage_args="E"
	+ unneeded="$unneeded rand.c"
	+else
	+ headers="$headers \$(EXTRA_MATH_HEADERS)"
	+fi
	+
	+if [ "$hist" -eq 0 ]; then
	+ manpage_args="${manpage_args}H"
	+ unneeded="$unneeded history.c"
	+else
	+ headers="$headers \$(HISTORY_HEADERS)"
	+fi
	+
	+if [ "$nls" -eq 0 ]; then
	+ manpage_args="${manpage_args}N"
	+fi
	+
	+if [ "$prompt" -eq 0 ]; then
	+ manpage_args="${manpage_args}P"
	+fi
	+
	+if [ "$bc" -eq 0 ]; then
	+ unneeded="$unneeded bc.c bc_lex.c bc_parse.c"
	+else
	+ headers="$headers \$(BC_HEADERS)"
	+fi
	+
	+if [ "$dc" -eq 0 ]; then
	+ unneeded="$unneeded dc.c dc_lex.c dc_parse.c"
	+else
	+ headers="$headers \$(DC_HEADERS)"
	+fi
	+
	+if [ "$library" -ne 0 ]; then
	+ unneeded="$unneeded args.c opt.c read.c file.c main.c"
	+ unneeded="$unneeded lang.c lex.c parse.c program.c"
	+ unneeded="$unneeded bc.c bc_lex.c bc_parse.c"
	+ unneeded="$unneeded dc.c dc_lex.c dc_parse.c"
	+ headers="$headers \$(LIBRARY_HEADERS)"
	+else
	+ unneeded="$unneeded library.c"
	+fi
	+
	+if [ "$manpage_args" = "" ]; then
	+ manpage_args="A"
	+fi
	+
	+if [ "$vg" -ne 0 ]; then
	+ memcheck=1
	+fi
	+
	+bc_tests=$(gen_test_targets bc)
	+bc_script_tests=$(gen_script_test_targets bc)
	+dc_tests=$(gen_test_targets dc)
	+dc_script_tests=$(gen_script_test_targets dc)
	+
	+# Print out the values; this is for debugging.
	+if [ "$bc" -ne 0 ]; then
	+ printf 'Building bc\n'
	+else
	+ printf 'Not building bc\n'
	+fi
	+if [ "$dc" -ne 0 ]; then
	+ printf 'Building dc\n'
	+else
	+ printf 'Not building dc\n'
	+fi
	+printf '\n'
	+printf 'BC_ENABLE_LIBRARY=%s\n\n' "$library"
	+printf 'BC_ENABLE_HISTORY=%s\n' "$hist"
	+printf 'BC_ENABLE_EXTRA_MATH=%s\n' "$extra_math"
	+printf 'BC_ENABLE_NLS=%s\n' "$nls"
	+printf 'BC_ENABLE_PROMPT=%s\n' "$prompt"
	+printf 'BC_ENABLE_AFL=%s\n' "$fuzz"
	+printf '\n'
	+printf 'BC_NUM_KARATSUBA_LEN=%s\n' "$karatsuba_len"
	+printf '\n'
	+printf 'CC=%s\n' "$CC"
	+printf 'CFLAGS=%s\n' "$CFLAGS"
	+printf 'HOSTCC=%s\n' "$HOSTCC"
	+printf 'HOSTCFLAGS=%s\n' "$HOSTCFLAGS"
	+printf 'CPPFLAGS=%s\n' "$CPPFLAGS"
	+printf 'LDFLAGS=%s\n' "$LDFLAGS"
	+printf 'PREFIX=%s\n' "$PREFIX"
	+printf 'BINDIR=%s\n' "$BINDIR"
	+printf 'INCLUDEDIR=%s\n' "$INCLUDEDIR"
	+printf 'LIBDIR=%s\n' "$LIBDIR"
	+printf 'DATAROOTDIR=%s\n' "$DATAROOTDIR"
	+printf 'DATADIR=%s\n' "$DATADIR"
	+printf 'MANDIR=%s\n' "$MANDIR"
	+printf 'MAN1DIR=%s\n' "$MAN1DIR"
	+printf 'MAN3DIR=%s\n' "$MAN3DIR"
	+printf 'NLSPATH=%s\n' "$NLSPATH"
	+printf 'EXECSUFFIX=%s\n' "$EXECSUFFIX"
	+printf 'EXECPREFIX=%s\n' "$EXECPREFIX"
	+printf 'DESTDIR=%s\n' "$DESTDIR"
	+printf 'LONG_BIT=%s\n' "$LONG_BIT"
	+printf 'GEN_HOST=%s\n' "$GEN_HOST"
	+printf 'GEN_EMU=%s\n' "$GEN_EMU"
	+
	+contents=$(cat "$scriptdir/Makefile.in")
	+
	+needle="WARNING"
	+replacement='* WARNING: Autogenerated from Makefile.in. DO NOT MODIFY *'
	+
	+contents=$(replace "$contents" "$needle" "$replacement")
	+
	+if [ "$unneeded" = "" ]; then
	+ unneeded="library.c"
	+fi
	+
	+contents=$(gen_file_list "$contents" $unneeded)
	+
	+SRC_TARGETS=""
	+
	+src_files=$(find_src_files $unneeded)
	+
	+for f in $src_files; do
	+ o=$(replace_ext "$f" "c" "o")
	+ SRC_TARGETS=$(printf '%s\n\n%s: %s %s\n\t$(CC) $(CFLAGS) -o %s -c %s\n' \
	+ "$SRC_TARGETS" "$o" "$headers" "$f" "$o" "$f")
	+done
	+
	+contents=$(replace "$contents" "HEADERS" "$headers")
	+
	+contents=$(replace "$contents" "BC_ENABLED" "$bc")
	+contents=$(replace "$contents" "DC_ENABLED" "$dc")
	+
	+contents=$(replace "$contents" "BC_ALL_TESTS" "$bc_test")
	+contents=$(replace "$contents" "BC_TESTS" "$bc_tests")
	+contents=$(replace "$contents" "BC_SCRIPT_TESTS" "$bc_script_tests")
	+contents=$(replace "$contents" "BC_TEST_EXEC" "$bc_test_exec")
	+contents=$(replace "$contents" "TIMECONST_ALL_TESTS" "$timeconst")
	+
	+contents=$(replace "$contents" "DC_ALL_TESTS" "$dc_test")
	+contents=$(replace "$contents" "DC_TESTS" "$dc_tests")
	+contents=$(replace "$contents" "DC_SCRIPT_TESTS" "$dc_script_tests")
	+contents=$(replace "$contents" "DC_TEST_EXEC" "$dc_test_exec")
	+
	+contents=$(replace "$contents" "BUILD_TYPE" "$manpage_args")
	+
	+contents=$(replace "$contents" "LIBRARY" "$library")
	+contents=$(replace "$contents" "HISTORY" "$hist")
	+contents=$(replace "$contents" "EXTRA_MATH" "$extra_math")
	+contents=$(replace "$contents" "NLS" "$nls")
	+contents=$(replace "$contents" "PROMPT" "$prompt")
	+contents=$(replace "$contents" "FUZZ" "$fuzz")
	+contents=$(replace "$contents" "MEMCHECK" "$memcheck")
	+
	+contents=$(replace "$contents" "BC_LIB_O" "$bc_lib")
	+contents=$(replace "$contents" "BC_HELP_O" "$bc_help")
	+contents=$(replace "$contents" "DC_HELP_O" "$dc_help")
	+contents=$(replace "$contents" "BC_LIB2_O" "$BC_LIB2_O")
	+contents=$(replace "$contents" "KARATSUBA_LEN" "$karatsuba_len")
	+
	+contents=$(replace "$contents" "NLSPATH" "$NLSPATH")
	+contents=$(replace "$contents" "DESTDIR" "$destdir")
	+contents=$(replace "$contents" "EXECSUFFIX" "$EXECSUFFIX")
	+contents=$(replace "$contents" "EXECPREFIX" "$EXECPREFIX")
	+contents=$(replace "$contents" "BINDIR" "$BINDIR")
	+contents=$(replace "$contents" "INCLUDEDIR" "$INCLUDEDIR")
	+contents=$(replace "$contents" "LIBDIR" "$LIBDIR")
	+contents=$(replace "$contents" "MAN1DIR" "$MAN1DIR")
	+contents=$(replace "$contents" "MAN3DIR" "$MAN3DIR")
	+contents=$(replace "$contents" "CFLAGS" "$CFLAGS")
	+contents=$(replace "$contents" "HOSTCFLAGS" "$HOSTCFLAGS")
	+contents=$(replace "$contents" "CPPFLAGS" "$CPPFLAGS")
	+contents=$(replace "$contents" "LDFLAGS" "$LDFLAGS")
	+contents=$(replace "$contents" "CC" "$CC")
	+contents=$(replace "$contents" "HOSTCC" "$HOSTCC")
	+contents=$(replace "$contents" "COVERAGE_OUTPUT" "$COVERAGE_OUTPUT")
	+contents=$(replace "$contents" "COVERAGE_PREREQS" "$COVERAGE_PREREQS")
	+contents=$(replace "$contents" "INSTALL_PREREQS" "$install_prereqs")
	+contents=$(replace "$contents" "INSTALL_MAN_PREREQS" "$install_man_prereqs")
	+contents=$(replace "$contents" "INSTALL_LOCALES" "$install_locales")
	+contents=$(replace "$contents" "INSTALL_LOCALES_PREREQS" "$install_locales_prereqs")
	+contents=$(replace "$contents" "UNINSTALL_MAN_PREREQS" "$uninstall_man_prereqs")
	+contents=$(replace "$contents" "UNINSTALL_PREREQS" "$uninstall_prereqs")
	+contents=$(replace "$contents" "UNINSTALL_LOCALES_PREREQS" "$uninstall_locales_prereqs")
	+
	+contents=$(replace "$contents" "DEFAULT_TARGET" "$default_target")
	+contents=$(replace "$contents" "DEFAULT_TARGET_PREREQS" "$default_target_prereqs")
	+contents=$(replace "$contents" "DEFAULT_TARGET_CMD" "$default_target_cmd")
	+contents=$(replace "$contents" "SECOND_TARGET" "$second_target")
	+contents=$(replace "$contents" "SECOND_TARGET_PREREQS" "$second_target_prereqs")
	+contents=$(replace "$contents" "SECOND_TARGET_CMD" "$second_target_cmd")
	+
	+contents=$(replace "$contents" "ALL_PREREQ" "$ALL_PREREQ")
	+contents=$(replace "$contents" "BC_EXEC_PREREQ" "$bc_exec_prereq")
	+contents=$(replace "$contents" "BC_EXEC_CMD" "$bc_exec_cmd")
	+contents=$(replace "$contents" "DC_EXEC_PREREQ" "$dc_exec_prereq")
	+contents=$(replace "$contents" "DC_EXEC_CMD" "$dc_exec_cmd")
	+
	+contents=$(replace "$contents" "EXECUTABLES" "$executables")
	+contents=$(replace "$contents" "MAIN_EXEC" "$main_exec")
	+contents=$(replace "$contents" "EXEC" "$executable")
	+contents=$(replace "$contents" "TESTS" "$tests")
	+
	+contents=$(replace "$contents" "BC_TEST" "$bc_test")
	+contents=$(replace "$contents" "DC_TEST" "$dc_test")
	+
	+contents=$(replace "$contents" "VG_BC_TEST" "$vg_bc_test")
	+contents=$(replace "$contents" "VG_DC_TEST" "$vg_dc_test")
	+
	+contents=$(replace "$contents" "TIMECONST" "$timeconst")
	+
	+contents=$(replace "$contents" "KARATSUBA" "$karatsuba")
	+contents=$(replace "$contents" "KARATSUBA_TEST" "$karatsuba_test")
	+
	+contents=$(replace "$contents" "LONG_BIT" "$LONG_BIT")
	+contents=$(replace "$contents" "LONG_BIT_DEFINE" "$LONG_BIT_DEFINE")
	+
	+contents=$(replace "$contents" "GEN" "$GEN")
	+contents=$(replace "$contents" "GEN_EXEC_TARGET" "$GEN_EXEC_TARGET")
	+contents=$(replace "$contents" "CLEAN_PREREQS" "$CLEAN_PREREQS")
	+contents=$(replace "$contents" "GEN_EMU" "$GEN_EMU")
	+
	+printf '%s\n%s\n\n' "$contents" "$SRC_TARGETS" > "$scriptdir/Makefile"
	+
	+if [ "$bc" -ne 0 ]; then
	+ gen_tests bc BC "$extra_math" "$time_tests" $bc_test_exec
	+ gen_script_tests bc "$extra_math" "$generate_tests" "$time_tests" $bc_test_exec
	+fi
	+
	+if [ "$dc" -ne 0 ]; then
	+ gen_tests dc DC "$extra_math" "$time_tests" $dc_test_exec
	+ gen_script_tests dc "$extra_math" "$generate_tests" "$time_tests" $dc_test_exec
	+fi
	+
	+cd "$scriptdir"
	+
	+cp -f manuals/bc/$manpage_args.1.md manuals/bc.1.md
	+cp -f manuals/bc/$manpage_args.1 manuals/bc.1
	+cp -f manuals/dc/$manpage_args.1.md manuals/dc.1.md
	+cp -f manuals/dc/$manpage_args.1 manuals/dc.1
	+
	+make clean > /dev/null
	diff --git a/contrib/bc/configure.sh b/contrib/bc/configure.sh
	index 310c26882906..af96564e7702 100755
	--- a/contrib/bc/configure.sh
	+++ b/contrib/bc/configure.sh
	@@ -1,1319 +1,1321 @@
	#! /bin/sh
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#

	script="$0"
	scriptdir=$(dirname "$script")
	script=$(basename "$script")

	. "$scriptdir/functions.sh"

	cd "$scriptdir"

	usage() {

	if [ $# -gt 0 ]; then

	_usage_val=1

	printf "%s\n\n" "$1"

	else
	_usage_val=0
	fi

	printf 'usage:\n'
	printf ' %s -h\n' "$script"
	printf ' %s --help\n' "$script"
	printf ' %s [-a\|-bD\|-dB\|-c] [-CEfgGHlmMNPtTvz] [-O OPT_LEVEL] [-k KARATSUBA_LEN]\n' "$script"
	printf ' %s \\\n' "$script"
	printf ' [--library\|--bc-only --disable-dc\|--dc-only --disable-bc\|--coverage]\\\n'
	printf ' [--force --debug --disable-extra-math --disable-generated-tests] \\\n'
	printf ' [--disable-history --disable-man-pages --disable-nls] \\\n'
	printf ' [--disable-prompt --disable-strip] [--install-all-locales] \\\n'
	printf ' [--opt=OPT_LEVEL] [--karatsuba-len=KARATSUBA_LEN] \\\n'
	printf ' [--prefix=PREFIX] [--bindir=BINDIR] [--datarootdir=DATAROOTDIR] \\\n'
	printf ' [--datadir=DATADIR] [--mandir=MANDIR] [--man1dir=MAN1DIR] \\\n'
	printf '\n'
	printf ' -a, --library\n'
	printf ' Build the libbc instead of the programs. This is meant to be used with\n'
	printf ' Other software like programming languages that want to make use of the\n'
	printf ' parsing and math capabilities. This option will install headers using\n'
	printf ' `make install`.\n'
	printf ' -b, --bc-only\n'
	printf ' Build bc only. It is an error if "-d", "--dc-only", "-B", or\n'
	printf ' "--disable-bc" are specified too.\n'
	printf ' -B, --disable-bc\n'
	printf ' Disable bc. It is an error if "-b", "--bc-only", "-D", or "--disable-dc"\n'
	printf ' are specified too.\n'
	printf ' -c, --coverage\n'
	printf ' Generate test coverage code. Requires gcov and regcovr.\n'
	printf ' It is an error if either "-b" ("-D") or "-d" ("-B") is specified.\n'
	printf ' Requires a compiler that use gcc-compatible coverage options\n'
	printf ' -C, --disable-clean\n'
	printf ' Disable the clean that configure.sh does before configure.\n'
	printf ' -d, --dc-only\n'
	printf ' Build dc only. It is an error if "-b", "--bc-only", "-D", or\n'
	printf ' "--disable-dc" are specified too.\n'
	printf ' -D, --disable-dc\n'
	printf ' Disable dc. It is an error if "-d", "--dc-only", "-B", or "--disable-bc"\n'
	printf ' are specified too.\n'
	printf ' -E, --disable-extra-math\n'
	printf ' Disable extra math. This includes: "$" operator (truncate to integer),\n'
	printf ' "@" operator (set number of decimal places), and r(x, p) (rounding\n'
	printf ' function). Additionally, this option disables the extra printing\n'
	printf ' functions in the math library.\n'
	printf ' -f, --force\n'
	printf ' Force use of all enabled options, even if they do not work. This\n'
	printf ' option is to allow the maintainer a way to test that certain options\n'
	printf ' are not failing invisibly. (Development only.)'
	printf ' -g, --debug\n'
	printf ' Build in debug mode. Adds the "-g" flag, and if there are no\n'
	printf ' other CFLAGS, and "-O" was not given, this also adds the "-O0"\n'
	printf ' flag. If this flag is not given, "-DNDEBUG" is added to CPPFLAGS\n'
	printf ' and a strip flag is added to the link stage.\n'
	printf ' -G, --disable-generated-tests\n'
	printf ' Disable generating tests. This is for platforms that do not have a\n'
	printf ' GNU bc-compatible bc to generate tests.\n'
	printf ' -h, --help\n'
	printf ' Print this help message and exit.\n'
	printf ' -H, --disable-history\n'
	printf ' Disable history.\n'
	printf ' -k KARATSUBA_LEN, --karatsuba-len KARATSUBA_LEN\n'
	printf ' Set the karatsuba length to KARATSUBA_LEN (default is 64).\n'
	printf ' It is an error if KARATSUBA_LEN is not a number or is less than 16.\n'
	printf ' -l, --install-all-locales\n'
	printf ' Installs all locales, regardless of how many are on the system. This\n'
	printf ' option is useful for package maintainers who want to make sure that\n'
	printf ' a package contains all of the locales that end users might need.\n'
	printf ' -m, --enable-memcheck\n'
	printf ' Enable memcheck mode, to ensure no memory leaks. For development only.\n'
	printf ' -M, --disable-man-pages\n'
	printf ' Disable installing manpages.\n'
	printf ' -N, --disable-nls\n'
	printf ' Disable POSIX locale (NLS) support.\n'
	printf ' -O OPT_LEVEL, --opt OPT_LEVEL\n'
	printf ' Set the optimization level. This can also be included in the CFLAGS,\n'
	printf ' but it is provided, so maintainers can build optimized debug builds.\n'
	printf ' This is passed through to the compiler, so it must be supported.\n'
	printf ' -P, --disable-prompt\n'
	printf ' Disables the prompt in the built bc. The prompt will never show up,\n'
	printf ' or in other words, it will be permanently disabled and cannot be\n'
	printf ' enabled.\n'
	printf ' -t, --enable-test-timing\n'
	printf ' Enable the timing of tests. This is for development only.\n'
	printf ' -T, --disable-strip\n'
	printf ' Disable stripping symbols from the compiled binary or binaries.\n'
	printf ' Stripping symbols only happens when debug mode is off.\n'
	printf ' -v, --enable-valgrind\n'
	printf ' Enable a build appropriate for valgrind. For development only.\n'
	printf ' -z, --enable-fuzz-mode\n'
	printf ' Enable fuzzing mode. THIS IS FOR DEVELOPMENT ONLY.\n'
	printf ' --prefix PREFIX\n'
	printf ' The prefix to install to. Overrides "$PREFIX" if it exists.\n'
	printf ' If PREFIX is "/usr", install path will be "/usr/bin".\n'
	printf ' Default is "/usr/local".\n'
	printf ' --bindir BINDIR\n'
	printf ' The directory to install binaries in. Overrides "$BINDIR" if it exists.\n'
	printf ' Default is "$PREFIX/bin".\n'
	printf ' --includedir INCLUDEDIR\n'
	printf ' The directory to install headers in. Overrides "$INCLUDEDIR" if it\n'
	printf ' exists. Default is "$PREFIX/include".\n'
	printf ' --libdir LIBDIR\n'
	printf ' The directory to install libraries in. Overrides "$LIBDIR" if it exists.\n'
	printf ' Default is "$PREFIX/lib".\n'
	printf ' --datarootdir DATAROOTDIR\n'
	printf ' The root location for data files. Overrides "$DATAROOTDIR" if it exists.\n'
	printf ' Default is "$PREFIX/share".\n'
	printf ' --datadir DATADIR\n'
	printf ' The location for data files. Overrides "$DATADIR" if it exists.\n'
	printf ' Default is "$DATAROOTDIR".\n'
	printf ' --mandir MANDIR\n'
	printf ' The location to install manpages to. Overrides "$MANDIR" if it exists.\n'
	printf ' Default is "$DATADIR/man".\n'
	printf ' --man1dir MAN1DIR\n'
	printf ' The location to install Section 1 manpages to. Overrides "$MAN1DIR" if\n'
	printf ' it exists. Default is "$MANDIR/man1".\n'
	printf ' --man3dir MAN3DIR\n'
	printf ' The location to install Section 3 manpages to. Overrides "$MAN3DIR" if\n'
	printf ' it exists. Default is "$MANDIR/man3".\n'
	printf '\n'
	printf 'In addition, the following environment variables are used:\n'
	printf '\n'
	printf ' CC C compiler. Must be compatible with POSIX c99. If there is a\n'
	printf ' space in the basename of the compiler, the items after the\n'
	printf ' first space are assumed to be compiler flags, and in that case,\n'
	printf ' the flags are automatically moved into CFLAGS. Default is\n'
	printf ' "c99".\n'
	printf ' HOSTCC Host C compiler. Must be compatible with POSIX c99. If there is\n'
	printf ' a space in the basename of the compiler, the items after the\n'
	printf ' first space are assumed to be compiler flags, and in the case,\n'
	printf ' the flags are automatically moved into HOSTCFLAGS. Default is\n'
	printf ' "$CC".\n'
	printf ' HOST_CC Same as HOSTCC. If HOSTCC also exists, it is used.\n'
	printf ' CFLAGS C compiler flags.\n'
	printf ' HOSTCFLAGS CFLAGS for HOSTCC. Default is "$CFLAGS".\n'
	printf ' HOST_CFLAGS Same as HOST_CFLAGS. If HOST_CFLAGS also exists, it is used.\n'
	printf ' CPPFLAGS C preprocessor flags. Default is "".\n'
	printf ' LDFLAGS Linker flags. Default is "".\n'
	printf ' PREFIX The prefix to install to. Default is "/usr/local".\n'
	printf ' If PREFIX is "/usr", install path will be "/usr/bin".\n'
	printf ' BINDIR The directory to install binaries in. Default is "$PREFIX/bin".\n'
	printf ' INCLUDEDIR The directory to install header files in. Default is\n'
	printf ' "$PREFIX/include".\n'
	printf ' LIBDIR The directory to install libraries in. Default is\n'
	printf ' "$PREFIX/lib".\n'
	printf ' DATAROOTDIR The root location for data files. Default is "$PREFIX/share".\n'
	printf ' DATADIR The location for data files. Default is "$DATAROOTDIR".\n'
	printf ' MANDIR The location to install manpages to. Default is "$DATADIR/man".\n'
	printf ' MAN1DIR The location to install Section 1 manpages to. Default is\n'
	printf ' "$MANDIR/man1".\n'
	printf ' MAN3DIR The location to install Section 3 manpages to. Default is\n'
	printf ' "$MANDIR/man3".\n'
	printf ' NLSPATH The location to install locale catalogs to. Must be an absolute\n'
	printf ' path (or contain one). This is treated the same as the POSIX\n'
	printf ' definition of $NLSPATH (see POSIX environment variables for\n'
	printf ' more information). Default is "/usr/share/locale/%%L/%%N".\n'
	printf ' EXECSUFFIX The suffix to append to the executable names, used to not\n'
	printf ' interfere with other installed bc executables. Default is "".\n'
	printf ' EXECPREFIX The prefix to append to the executable names, used to not\n'
	printf ' interfere with other installed bc executables. Default is "".\n'
	printf ' DESTDIR For package creation. Default is "". If it is empty when\n'
	printf ' `%s` is run, it can also be passed to `make install`\n' "$script"
	printf ' later as an environment variable. If both are specified,\n'
	printf ' the one given to `%s` takes precedence.\n' "$script"
	printf ' LONG_BIT The number of bits in a C `long` type. This is mostly for the\n'
	printf ' embedded space since this `bc` uses `long`s internally for\n'
	printf ' overflow checking. In C99, a `long` is required to be 32 bits.\n'
	printf ' For most normal desktop systems, setting this is unnecessary,\n'
	printf ' except that 32-bit platforms with 64-bit longs may want to set\n'
	printf ' it to `32`. Default is the default of `LONG_BIT` for the target\n'
	printf ' platform. Minimum allowed is `32`. It is a build time error if\n'
	printf ' the specified value of `LONG_BIT` is greater than the default\n'
	printf ' value of `LONG_BIT` for the target platform.\n'
	printf ' GEN_HOST Whether to use `gen/strgen.c`, instead of `gen/strgen.sh`, to\n'
	printf ' produce the C files that contain the help texts as well as the\n'
	printf ' math libraries. By default, `gen/strgen.c` is used, compiled by\n'
	printf ' "$HOSTCC" and run on the host machine. Using `gen/strgen.sh`\n'
	printf ' removes the need to compile and run an executable on the host\n'
	printf ' machine since `gen/strgen.sh` is a POSIX shell script. However,\n'
	printf ' `gen/lib2.bc` is perilously close to 4095 characters, the max\n'
	printf ' supported length of a string literal in C99 (and it could be\n'
	printf ' added to in the future), and `gen/strgen.sh` generates a string\n'
	printf ' literal instead of an array, as `gen/strgen.c` does. For most\n'
	printf ' production-ready compilers, this limit probably is not\n'
	printf ' enforced, but it could be. Both options are still available for\n'
	printf ' this reason. If you are sure your compiler does not have the\n'
	printf ' limit and do not want to compile and run a binary on the host\n'
	printf ' machine, set this variable to "0". Any other value, or a\n'
	printf ' non-existent value, will cause the build system to compile and\n'
	printf ' run `gen/strgen.c`. Default is "".\n'
	printf ' GEN_EMU Emulator to run string generator code under (leave empty if not\n'
	printf ' necessary). This is not necessary when using `gen/strgen.sh`.\n'
	printf ' Default is "".\n'
	printf '\n'
	printf 'WARNING: even though `configure.sh` supports both option types, short and\n'
	printf 'long, it does not support handling both at the same time. Use only one type.\n'

	exit "$_usage_val"
	}

	replace_ext() {

	if [ "$#" -ne 3 ]; then
	err_exit "Invalid number of args to $0"
	fi

	_replace_ext_file="$1"
	_replace_ext_ext1="$2"
	_replace_ext_ext2="$3"

	_replace_ext_result="${_replace_ext_file%.$_replace_ext_ext1}.$_replace_ext_ext2"

	printf '%s\n' "$_replace_ext_result"
	}

	replace_exts() {

	if [ "$#" -ne 3 ]; then
	err_exit "Invalid number of args to $0"
	fi

	_replace_exts_files="$1"
	_replace_exts_ext1="$2"
	_replace_exts_ext2="$3"

	for _replace_exts_file in $_replace_exts_files; do
	_replace_exts_new_name=$(replace_ext "$_replace_exts_file" "$_replace_exts_ext1" "$_replace_exts_ext2")
	_replace_exts_result="$_replace_exts_result $_replace_exts_new_name"
	done

	printf '%s\n' "$_replace_exts_result"
	}

	replace() {

	if [ "$#" -ne 3 ]; then
	err_exit "Invalid number of args to $0"
	fi

	_replace_str="$1"
	_replace_needle="$2"
	_replace_replacement="$3"

	substring_replace "$_replace_str" "%%$_replace_needle%%" "$_replace_replacement"
	}

	find_src_files() {

	if [ "$#" -ge 1 ] && [ "$1" != "" ]; then

	while [ "$#" -ge 1 ]; do
	_find_src_files_a="${1## }"
	shift
	_find_src_files_args="$_find_src_files_args ! -path src/${_find_src_files_a}"
	done

	else
	_find_src_files_args="-print"
	fi

	printf '%s\n' $(find src/ -depth -name "*.c" $_find_src_files_args)
	}

	gen_file_list() {

	if [ "$#" -lt 1 ]; then
	err_exit "Invalid number of args to $0"
	fi

	_gen_file_list_contents="$1"
	shift

	p=$(pwd)

	cd "$scriptdir"

	if [ "$#" -ge 1 ]; then
	_gen_file_list_unneeded="$@"
	else
	_gen_file_list_unneeded=""
	fi

	_gen_file_list_needle_src="SRC"
	_gen_file_list_needle_obj="OBJ"
	_gen_file_list_needle_gcda="GCDA"
	_gen_file_list_needle_gcno="GCNO"

	_gen_file_list_replacement=$(find_src_files $_gen_file_list_unneeded \| tr '\n' ' ')
	_gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	"$_gen_file_list_needle_src" "$_gen_file_list_replacement")

	_gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "c" "o")
	_gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	"$_gen_file_list_needle_obj" "$_gen_file_list_replacement")

	_gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "o" "gcda")
	_gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	"$_gen_file_list_needle_gcda" "$_gen_file_list_replacement")

	_gen_file_list_replacement=$(replace_exts "$_gen_file_list_replacement" "gcda" "gcno")
	_gen_file_list_contents=$(replace "$_gen_file_list_contents" \
	"$_gen_file_list_needle_gcno" "$_gen_file_list_replacement")

	cd "$p"

	printf '%s\n' "$_gen_file_list_contents"
	}

	gen_tests() {

	_gen_tests_name="$1"
	shift

	_gen_tests_uname="$1"
	shift

	_gen_tests_extra_math="$1"
	shift

	_gen_tests_time_tests="$1"
	shift

	_gen_tests_extra_required=$(cat tests/extra_required.txt)

	for _gen_tests_t in $(cat "$scriptdir/tests/$_gen_tests_name/all.txt"); do

	if [ "$_gen_tests_extra_math" -eq 0 ]; then

	if [ -z "${_gen_tests_extra_required##$_gen_tests_t}" ]; then
	printf 'test_%s_%s:\n\t@printf "Skipping %s %s\\n"\n\n' \
	"$_gen_tests_name" "$_gen_tests_t" "$_gen_tests_name" \
	"$_gen_tests_t" >> "$scriptdir/Makefile"
	continue
	fi

	fi

	printf 'test_%s_%s:\n\t@sh tests/test.sh %s %s %s %s %s\n\n' \
	"$_gen_tests_name" "$_gen_tests_t" "$_gen_tests_name" \
	"$_gen_tests_t" "$generate_tests" "$time_tests" \
	"$*" >> "$scriptdir/Makefile"

	done
	}

	gen_test_targets() {

	_gen_test_targets_name="$1"
	shift

	_gen_test_targets_tests=$(cat "$scriptdir/tests/${_gen_test_targets_name}/all.txt")

	for _gen_test_targets_t in $_gen_test_targets_tests; do
	printf ' test_%s_%s' "$_gen_test_targets_name" "$_gen_test_targets_t"
	done

	printf '\n'
	}

	gen_script_tests() {

	_gen_script_tests_name="$1"
	shift

	_gen_script_tests_extra_math="$1"
	shift

	_gen_script_tests_generate="$1"
	shift

	_gen_script_tests_time="$1"
	shift

	_gen_script_tests_tests=$(cat "$scriptdir/tests/$_gen_script_tests_name/scripts/all.txt")

	for _gen_script_tests_f in $_gen_script_tests_tests; do

	_gen_script_tests_b=$(basename "$_gen_script_tests_f" ".${_gen_script_tests_name}")

	printf 'test_%s_script_%s:\n\t@sh tests/script.sh %s %s %s 1 %s %s %s\n\n' \
	"$_gen_script_tests_name" "$_gen_script_tests_b" "$_gen_script_tests_name" \
	"$_gen_script_tests_f" "$_gen_script_tests_extra_math" "$_gen_script_tests_generate" \
	"$_gen_script_tests_time" "$*" >> "$scriptdir/Makefile"
	done
	}

	gen_script_test_targets() {

	_gen_script_test_targets_name="$1"
	shift

	_gen_script_test_targets_tests=$(cat "$scriptdir/tests/$_gen_script_test_targets_name/scripts/all.txt")

	for _gen_script_test_targets_f in $_gen_script_test_targets_tests; do
	_gen_script_test_targets_b=$(basename "$_gen_script_test_targets_f" \
	".$_gen_script_test_targets_name")
	printf ' test_%s_script_%s' "$_gen_script_test_targets_name" \
	"$_gen_script_test_targets_b"
	done

	printf '\n'
	}

	bc_only=0
	dc_only=0
	coverage=0
	karatsuba_len=32
	debug=0
	hist=1
	extra_math=1
	optimization=""
	generate_tests=1
	install_manpages=1
	nls=1
	prompt=1
	force=0
	strip_bin=1
	all_locales=0
	library=0
	fuzz=0
	time_tests=0
	vg=0
	memcheck=0
	clean=1

	while getopts "abBcdDEfgGhHk:lMmNO:PStTvz-" opt; do

	case "$opt" in
	a) library=1 ;;
	b) bc_only=1 ;;
	B) dc_only=1 ;;
	c) coverage=1 ;;
	C) clean=0 ;;
	d) dc_only=1 ;;
	D) bc_only=1 ;;
	E) extra_math=0 ;;
	f) force=1 ;;
	g) debug=1 ;;
	G) generate_tests=0 ;;
	h) usage ;;
	H) hist=0 ;;
	k) karatsuba_len="$OPTARG" ;;
	l) all_locales=1 ;;
	m) memcheck=1 ;;
	M) install_manpages=0 ;;
	N) nls=0 ;;
	O) optimization="$OPTARG" ;;
	P) prompt=0 ;;
	t) time_tests=1 ;;
	T) strip_bin=0 ;;
	v) vg=1 ;;
	z) fuzz=1 ;;
	-)
	arg="$1"
	arg="${arg#--}"
	LONG_OPTARG="${arg#*=}"
	case $arg in
	help) usage ;;
	library) library=1 ;;
	bc-only) bc_only=1 ;;
	dc-only) dc_only=1 ;;
	coverage) coverage=1 ;;
	debug) debug=1 ;;
	force) force=1 ;;
	prefix=?*) PREFIX="$LONG_OPTARG" ;;
	prefix)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	PREFIX="$2"
	shift ;;
	bindir=?*) BINDIR="$LONG_OPTARG" ;;
	bindir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	BINDIR="$2"
	shift ;;
	includedir=?*) INCLUDEDIR="$LONG_OPTARG" ;;
	includedir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	INCLUDEDIR="$2"
	shift ;;
	libdir=?*) LIBDIR="$LONG_OPTARG" ;;
	libdir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	LIBDIR="$2"
	shift ;;
	datarootdir=?*) DATAROOTDIR="$LONG_OPTARG" ;;
	datarootdir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	DATAROOTDIR="$2"
	shift ;;
	datadir=?*) DATADIR="$LONG_OPTARG" ;;
	datadir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	DATADIR="$2"
	shift ;;
	mandir=?*) MANDIR="$LONG_OPTARG" ;;
	mandir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	MANDIR="$2"
	shift ;;
	man1dir=?*) MAN1DIR="$LONG_OPTARG" ;;
	man1dir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	MAN1DIR="$2"
	shift ;;
	man3dir=?*) MAN3DIR="$LONG_OPTARG" ;;
	man3dir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	MAN3DIR="$2"
	shift ;;
	localedir=?*) LOCALEDIR="$LONG_OPTARG" ;;
	localedir)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	LOCALEDIR="$2"
	shift ;;
	karatsuba-len=?*) karatsuba_len="$LONG_OPTARG" ;;
	karatsuba-len)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	karatsuba_len="$1"
	shift ;;
	opt=?*) optimization="$LONG_OPTARG" ;;
	opt)
	if [ "$#" -lt 2 ]; then
	usage "No argument given for '--$arg' option"
	fi
	optimization="$1"
	shift ;;
	disable-bc) dc_only=1 ;;
	disable-dc) bc_only=1 ;;
	disable-clean) clean=0 ;;
	disable-extra-math) extra_math=0 ;;
	disable-generated-tests) generate_tests=0 ;;
	disable-history) hist=0 ;;
	disable-man-pages) install_manpages=0 ;;
	disable-nls) nls=0 ;;
	disable-prompt) prompt=0 ;;
	disable-strip) strip_bin=0 ;;
	enable-test-timing) time_tests=1 ;;
	enable-valgrind) vg=1 ;;
	enable-fuzz-mode) fuzz=1 ;;
	enable-memcheck) memcheck=1 ;;
	install-all-locales) all_locales=1 ;;
	help* \| bc-only* \| dc-only* \| coverage* \| debug*)
	usage "No arg allowed for --$arg option" ;;
	disable-bc* \| disable-dc* \| disable-clean*)
	usage "No arg allowed for --$arg option" ;;
	disable-extra-math*)
	usage "No arg allowed for --$arg option" ;;
	disable-generated-tests* \| disable-history*)
	usage "No arg allowed for --$arg option" ;;
	disable-man-pages* \| disable-nls* \| disable-strip*)
	usage "No arg allowed for --$arg option" ;;
	enable-fuzz-mode* \| enable-test-timing* \| enable-valgrind*)
	usage "No arg allowed for --$arg option" ;;
	enable-memcheck* \| install-all-locales*)
	usage "No arg allowed for --$arg option" ;;
	'') break ;; # "--" terminates argument processing
	* ) usage "Invalid option $LONG_OPTARG" ;;
	esac
	shift
	OPTIND=1 ;;
	?) usage "Invalid option $opt" ;;
	esac

	done

	if [ "$clean" -ne 0 ]; then
	if [ -f ./Makefile ]; then
	make clean_config > /dev/null
	fi
	fi

	if [ "$bc_only" -eq 1 ] && [ "$dc_only" -eq 1 ]; then
	usage "Can only specify one of -b(-D) or -d(-B)"
	fi

	if [ "$library" -ne 0 ]; then
	if [ "$bc_only" -eq 1 ] \|\| [ "$dc_only" -eq 1 ]; then
	usage "Must not specify -b(-D) or -d(-B) when building the library"
	fi
	fi

	case $karatsuba_len in
	([!0-9]\|'') usage "KARATSUBA_LEN is not a number" ;;
	(*) ;;
	esac

	if [ "$karatsuba_len" -lt 16 ]; then
	usage "KARATSUBA_LEN is less than 16"
	fi

	set -e

	if [ -z "${LONG_BIT+set}" ]; then
	LONG_BIT_DEFINE=""
	elif [ "$LONG_BIT" -lt 32 ]; then
	usage "LONG_BIT is less than 32"
	else
	LONG_BIT_DEFINE="-DBC_LONG_BIT=\$(BC_LONG_BIT)"
	fi

	if [ -z "$CC" ]; then
	CC="c99"
	else
	ccbase=$(basename "$CC")
	suffix=" *"
	prefix="* "

	if [ "${ccbase%%$suffix}" != "$ccbase" ]; then
	ccflags="${ccbase#$prefix}"
	cc="${ccbase%%$suffix}"
	ccdir=$(dirname "$CC")
	if [ "$ccdir" = "." ] && [ "${CC#.}" = "$CC" ]; then
	ccdir=""
	else
	ccdir="$ccdir/"
	fi
	CC="${ccdir}${cc}"
	CFLAGS="$CFLAGS $ccflags"
	fi
	fi

	if [ -z "$HOSTCC" ] && [ -z "$HOST_CC" ]; then
	HOSTCC="$CC"
	elif [ -z "$HOSTCC" ]; then
	HOSTCC="$HOST_CC"
	fi

	if [ "$HOSTCC" != "$CC" ]; then
	ccbase=$(basename "$HOSTCC")
	suffix=" *"
	prefix="* "

	if [ "${ccbase%%$suffix}" != "$ccbase" ]; then
	ccflags="${ccbase#$prefix}"
	cc="${ccbase%%$suffix}"
	ccdir=$(dirname "$HOSTCC")
	if [ "$ccdir" = "." ] && [ "${HOSTCC#.}" = "$HOSTCC" ]; then
	ccdir=""
	else
	ccdir="$ccdir/"
	fi
	HOSTCC="${ccdir}${cc}"
	HOSTCFLAGS="$HOSTCFLAGS $ccflags"
	fi
	fi

	if [ -z "${HOSTCFLAGS+set}" ] && [ -z "${HOST_CFLAGS+set}" ]; then
	HOSTCFLAGS="$CFLAGS"
	elif [ -z "${HOSTCFLAGS+set}" ]; then
	HOSTCFLAGS="$HOST_CFLAGS"
	fi

	link="@printf 'No link necessary\\\\n'"
	main_exec="BC"
	executable="BC_EXEC"

	tests="test_bc timeconst test_dc"

	bc_test="@tests/all.sh bc $extra_math 1 $generate_tests 0 \$(BC_EXEC)"
	dc_test="@tests/all.sh dc $extra_math 1 $generate_tests 0 \$(DC_EXEC)"

	timeconst="@tests/bc/timeconst.sh tests/bc/scripts/timeconst.bc \$(BC_EXEC)"

	# In order to have cleanup at exit, we need to be in
	# debug mode, so don't run valgrind without that.
	if [ "$vg" -ne 0 ]; then
	debug=1
	bc_test_exec='valgrind $(VALGRIND_ARGS) $(BC_EXEC)'
	dc_test_exec='valgrind $(VALGRIND_ARGS) $(DC_EXEC)'
	else
	bc_test_exec='$(BC_EXEC)'
	dc_test_exec='$(DC_EXEC)'
	fi

	karatsuba="@printf 'karatsuba cannot be run because one of bc or dc is not built\\\\n'"
	karatsuba_test="@printf 'karatsuba cannot be run because one of bc or dc is not built\\\\n'"

	bc_lib="\$(GEN_DIR)/lib.o"
	bc_help="\$(GEN_DIR)/bc_help.o"
	dc_help="\$(GEN_DIR)/dc_help.o"

	default_target_prereqs="\$(BIN) \$(OBJS)"
	default_target_cmd="\$(CC) \$(CFLAGS) \$(OBJS) \$(LDFLAGS) -o \$(EXEC)"
	default_target="\$(DC_EXEC)"

	second_target_prereqs=""
	second_target_cmd="$default_target_cmd"
	second_target="\$(BC_EXEC)"

	if [ "$library" -ne 0 ]; then

	extra_math=1
	nls=0
	hist=0
	prompt=0
	bc=1
	dc=1

	default_target_prereqs="\$(BIN) \$(OBJ)"
	default_target_cmd="ar -r -cu \$(LIBBC) \$(OBJ)"
	default_target="\$(LIBBC)"
	tests="test_library"

	elif [ "$bc_only" -eq 1 ]; then

	bc=1
	dc=0

	dc_help=""

	executables="bc"

	dc_test="@printf 'No dc tests to run\\\\n'"

	install_prereqs=" install_execs"
	install_man_prereqs=" install_bc_manpage"
	uninstall_prereqs=" uninstall_bc"
	uninstall_man_prereqs=" uninstall_bc_manpage"

	default_target="\$(BC_EXEC)"
	second_target="\$(DC_EXEC)"
	tests="test_bc timeconst"

	elif [ "$dc_only" -eq 1 ]; then

	bc=0
	dc=1

	bc_lib=""
	bc_help=""

	executables="dc"

	main_exec="DC"
	executable="DC_EXEC"

	bc_test="@printf 'No bc tests to run\\\\n'"

	timeconst="@printf 'timeconst cannot be run because bc is not built\\\\n'"

	install_prereqs=" install_execs"
	install_man_prereqs=" install_dc_manpage"
	uninstall_prereqs=" uninstall_dc"
	uninstall_man_prereqs=" uninstall_dc_manpage"

	tests="test_dc"

	else

	bc=1
	dc=1

	executables="bc and dc"

	karatsuba="@\$(KARATSUBA) 30 0 \$(BC_EXEC)"
	karatsuba_test="@\$(KARATSUBA) 1 100 \$(BC_EXEC)"

	if [ "$library" -eq 0 ]; then
	install_prereqs=" install_execs"
	install_man_prereqs=" install_bc_manpage install_dc_manpage"
	uninstall_prereqs=" uninstall_bc uninstall_dc"
	uninstall_man_prereqs=" uninstall_bc_manpage uninstall_dc_manpage"
	else
	install_prereqs=" install_library install_bcl_header"
	install_man_prereqs=" install_bcl_manpage"
	uninstall_prereqs=" uninstall_library uninstall_bcl_header"
	uninstall_man_prereqs=" uninstall_bcl_manpage"
	tests="test_library"
	fi

	second_target_prereqs="$default_target_prereqs"
	default_target_prereqs="$second_target"
	default_target_cmd="\$(LINK) \$(BIN) \$(EXEC_PREFIX)\$(DC)"

	fi

	if [ "$fuzz" -ne 0 ]; then
	debug=1
	hist=0
	prompt=0
	nls=0
	optimization="3"
	fi

	if [ "$debug" -eq 1 ]; then

	if [ -z "$CFLAGS" ] && [ -z "$optimization" ]; then
	CFLAGS="-O0"
	fi

	CFLAGS="-g $CFLAGS"

	else
	CPPFLAGS="-DNDEBUG $CPPFLAGS"
	if [ "$strip_bin" -ne 0 ]; then
	LDFLAGS="-s $LDFLAGS"
	fi
	fi

	if [ -n "$optimization" ]; then
	CFLAGS="-O$optimization $CFLAGS"
	fi

	if [ "$coverage" -eq 1 ]; then

	if [ "$bc_only" -eq 1 ] \|\| [ "$dc_only" -eq 1 ]; then
	usage "Can only specify -c without -b or -d"
	fi

	CFLAGS="-fprofile-arcs -ftest-coverage -g -O0 $CFLAGS"
	CPPFLAGS="-DNDEBUG $CPPFLAGS"

	COVERAGE_OUTPUT="@gcov -pabcdf \$(GCDA) \$(BC_GCDA) \$(DC_GCDA) \$(HISTORY_GCDA) \$(RAND_GCDA)"
	COVERAGE_OUTPUT="$COVERAGE_OUTPUT;\$(RM) -f \$(GEN).gc"
	COVERAGE_OUTPUT="$COVERAGE_OUTPUT;gcovr --html-details --output index.html"
	COVERAGE_PREREQS=" test coverage_output"

	else
	COVERAGE_OUTPUT="@printf 'Coverage not generated\\\\n'"
	COVERAGE_PREREQS=""
	fi

	if [ -z "${DESTDIR+set}" ]; then
	destdir=""
	else
	destdir="DESTDIR = $DESTDIR"
	fi

	if [ -z "${PREFIX+set}" ]; then
	PREFIX="/usr/local"
	fi

	if [ -z "${BINDIR+set}" ]; then
	BINDIR="$PREFIX/bin"
	fi

	if [ -z "${INCLUDEDIR+set}" ]; then
	INCLUDEDIR="$PREFIX/include"
	fi

	if [ -z "${LIBDIR+set}" ]; then
	LIBDIR="$PREFIX/lib"
	fi

	if [ "$install_manpages" -ne 0 ] \|\| [ "$nls" -ne 0 ]; then
	if [ -z "${DATAROOTDIR+set}" ]; then
	DATAROOTDIR="$PREFIX/share"
	fi
	fi

	if [ "$install_manpages" -ne 0 ]; then

	if [ -z "${DATADIR+set}" ]; then
	DATADIR="$DATAROOTDIR"
	fi

	if [ -z "${MANDIR+set}" ]; then
	MANDIR="$DATADIR/man"
	fi

	if [ -z "${MAN1DIR+set}" ]; then
	MAN1DIR="$MANDIR/man1"
	fi

	if [ -z "${MAN3DIR+set}" ]; then
	MAN3DIR="$MANDIR/man3"
	fi

	else
	install_man_prereqs=""
	uninstall_man_prereqs=""
	fi

	if [ "$nls" -ne 0 ]; then

	set +e

	printf 'Testing NLS...\n'

	flags="-DBC_ENABLE_NLS=1 -DBC_ENABLED=$bc -DDC_ENABLED=$dc"
	flags="$flags -DBC_ENABLE_HISTORY=$hist"
	flags="$flags -DBC_ENABLE_EXTRA_MATH=$extra_math -I./include/"
	flags="$flags -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700"

	"$CC" $CPPFLAGS $CFLAGS $flags -c "src/vm.c" -o "$scriptdir/vm.o" > /dev/null 2>&1

	err="$?"

	rm -rf "$scriptdir/vm.o"

	# If this errors, it is probably because of building on Windows,
	# and NLS is not supported on Windows, so disable it.
	if [ "$err" -ne 0 ]; then
	printf 'NLS does not work.\n'
	if [ $force -eq 0 ]; then
	printf 'Disabling NLS...\n\n'
	nls=0
	else
	printf 'Forcing NLS...\n\n'
	fi
	else
	printf 'NLS works.\n\n'

	printf 'Testing gencat...\n'
	gencat "$scriptdir/en_US.cat" "$scriptdir/locales/en_US.msg" > /dev/null 2>&1

	err="$?"

	rm -rf "$scriptdir/en_US.cat"

	if [ "$err" -ne 0 ]; then
	printf 'gencat does not work.\n'
	if [ $force -eq 0 ]; then
	printf 'Disabling NLS...\n\n'
	nls=0
	else
	printf 'Forcing NLS...\n\n'
	fi
	else

	printf 'gencat works.\n\n'

	if [ "$HOSTCC" != "$CC" ]; then
	printf 'Cross-compile detected.\n\n'
	printf 'WARNING: Catalog files generated with gencat may not be portable\n'
	printf ' across different architectures.\n\n'
	fi

	if [ -z "$NLSPATH" ]; then
	NLSPATH="/usr/share/locale/%L/%N"
	fi

	install_locales_prereqs=" install_locales"
	uninstall_locales_prereqs=" uninstall_locales"

	fi

	fi

	set -e

	else
	install_locales_prereqs=""
	uninstall_locales_prereqs=""
	all_locales=0
	fi

	if [ "$nls" -ne 0 ] && [ "$all_locales" -ne 0 ]; then
	install_locales="\$(LOCALE_INSTALL) -l \$(NLSPATH) \$(MAIN_EXEC) \$(DESTDIR)"
	else
	install_locales="\$(LOCALE_INSTALL) \$(NLSPATH) \$(MAIN_EXEC) \$(DESTDIR)"
	fi

	if [ "$hist" -eq 1 ]; then

	set +e

	printf 'Testing history...\n'

	flags="-DBC_ENABLE_HISTORY=1 -DBC_ENABLED=$bc -DDC_ENABLED=$dc"
	flags="$flags -DBC_ENABLE_NLS=$nls -DBC_ENABLE_LIBRARY=0"
	flags="$flags -DBC_ENABLE_EXTRA_MATH=$extra_math -I./include/"
	flags="$flags -D_POSIX_C_SOURCE=200809L -D_XOPEN_SOURCE=700"

	"$CC" $CPPFLAGS $CFLAGS $flags -c "src/history.c" -o "$scriptdir/history.o" > /dev/null 2>&1

	err="$?"

	rm -rf "$scriptdir/history.o"

	# If this errors, it is probably because of building on Windows,
	# and history is not supported on Windows, so disable it.
	if [ "$err" -ne 0 ]; then
	printf 'History does not work.\n'
	if [ $force -eq 0 ]; then
	printf 'Disabling history...\n\n'
	hist=0
	else
	printf 'Forcing history...\n\n'
	fi
	else
	printf 'History works.\n\n'
	fi

	set -e

	fi

	if [ "$library" -eq 1 ]; then
	bc_lib=""
	fi

	if [ "$extra_math" -eq 1 ] && [ "$bc" -ne 0 ] && [ "$library" -eq 0 ]; then
	BC_LIB2_O="\$(GEN_DIR)/lib2.o"
	else
	BC_LIB2_O=""
	fi

	GEN="strgen"
	GEN_EXEC_TARGET="\$(HOSTCC) \$(HOSTCFLAGS) -o \$(GEN_EXEC) \$(GEN_C)"
	CLEAN_PREREQS=" clean_gen"

	if [ -z "${GEN_HOST+set}" ]; then
	GEN_HOST=1
	else
	if [ "$GEN_HOST" -eq 0 ]; then
	GEN="strgen.sh"
	GEN_EXEC_TARGET="@printf 'Do not need to build gen/strgen.c\\\\n'"
	CLEAN_PREREQS=""
	fi
	fi

	manpage_args=""
	unneeded=""
	headers="\$(HEADERS)"

	if [ "$extra_math" -eq 0 ]; then
	manpage_args="E"
	unneeded="$unneeded rand.c"
	else
	headers="$headers \$(EXTRA_MATH_HEADERS)"
	fi

	if [ "$hist" -eq 0 ]; then
	manpage_args="${manpage_args}H"
	unneeded="$unneeded history.c"
	else
	headers="$headers \$(HISTORY_HEADERS)"
	fi

	if [ "$nls" -eq 0 ]; then
	manpage_args="${manpage_args}N"
	fi

	if [ "$prompt" -eq 0 ]; then
	manpage_args="${manpage_args}P"
	fi

	if [ "$bc" -eq 0 ]; then
	unneeded="$unneeded bc.c bc_lex.c bc_parse.c"
	else
	headers="$headers \$(BC_HEADERS)"
	fi

	if [ "$dc" -eq 0 ]; then
	unneeded="$unneeded dc.c dc_lex.c dc_parse.c"
	else
	headers="$headers \$(DC_HEADERS)"
	fi

	if [ "$library" -ne 0 ]; then
	unneeded="$unneeded args.c opt.c read.c file.c main.c"
	unneeded="$unneeded lang.c lex.c parse.c program.c"
	unneeded="$unneeded bc.c bc_lex.c bc_parse.c"
	unneeded="$unneeded dc.c dc_lex.c dc_parse.c"
	headers="$headers \$(LIBRARY_HEADERS)"
	else
	unneeded="$unneeded library.c"
	fi

	if [ "$manpage_args" = "" ]; then
	manpage_args="A"
	fi

	if [ "$vg" -ne 0 ]; then
	memcheck=1
	fi

	bc_tests=$(gen_test_targets bc)
	bc_script_tests=$(gen_script_test_targets bc)
	dc_tests=$(gen_test_targets dc)
	dc_script_tests=$(gen_script_test_targets dc)

	# Print out the values; this is for debugging.
	if [ "$bc" -ne 0 ]; then
	printf 'Building bc\n'
	else
	printf 'Not building bc\n'
	fi
	if [ "$dc" -ne 0 ]; then
	printf 'Building dc\n'
	else
	printf 'Not building dc\n'
	fi
	printf '\n'
	printf 'BC_ENABLE_LIBRARY=%s\n\n' "$library"
	printf 'BC_ENABLE_HISTORY=%s\n' "$hist"
	printf 'BC_ENABLE_EXTRA_MATH=%s\n' "$extra_math"
	printf 'BC_ENABLE_NLS=%s\n' "$nls"
	printf 'BC_ENABLE_PROMPT=%s\n' "$prompt"
	printf 'BC_ENABLE_AFL=%s\n' "$fuzz"
	printf '\n'
	printf 'BC_NUM_KARATSUBA_LEN=%s\n' "$karatsuba_len"
	printf '\n'
	printf 'CC=%s\n' "$CC"
	printf 'CFLAGS=%s\n' "$CFLAGS"
	printf 'HOSTCC=%s\n' "$HOSTCC"
	printf 'HOSTCFLAGS=%s\n' "$HOSTCFLAGS"
	printf 'CPPFLAGS=%s\n' "$CPPFLAGS"
	printf 'LDFLAGS=%s\n' "$LDFLAGS"
	printf 'PREFIX=%s\n' "$PREFIX"
	printf 'BINDIR=%s\n' "$BINDIR"
	printf 'INCLUDEDIR=%s\n' "$INCLUDEDIR"
	printf 'LIBDIR=%s\n' "$LIBDIR"
	printf 'DATAROOTDIR=%s\n' "$DATAROOTDIR"
	printf 'DATADIR=%s\n' "$DATADIR"
	printf 'MANDIR=%s\n' "$MANDIR"
	printf 'MAN1DIR=%s\n' "$MAN1DIR"
	printf 'MAN3DIR=%s\n' "$MAN3DIR"
	printf 'NLSPATH=%s\n' "$NLSPATH"
	printf 'EXECSUFFIX=%s\n' "$EXECSUFFIX"
	printf 'EXECPREFIX=%s\n' "$EXECPREFIX"
	printf 'DESTDIR=%s\n' "$DESTDIR"
	printf 'LONG_BIT=%s\n' "$LONG_BIT"
	printf 'GEN_HOST=%s\n' "$GEN_HOST"
	printf 'GEN_EMU=%s\n' "$GEN_EMU"

	contents=$(cat "$scriptdir/Makefile.in")

	needle="WARNING"
	replacement='* WARNING: Autogenerated from Makefile.in. DO NOT MODIFY *'

	contents=$(replace "$contents" "$needle" "$replacement")

	if [ "$unneeded" = "" ]; then
	unneeded="library.c"
	fi

	contents=$(gen_file_list "$contents" $unneeded)

	SRC_TARGETS=""

	src_files=$(find_src_files $unneeded)

	for f in $src_files; do
	o=$(replace_ext "$f" "c" "o")
	SRC_TARGETS=$(printf '%s\n\n%s: %s %s\n\t$(CC) $(CFLAGS) -o %s -c %s\n' \
	"$SRC_TARGETS" "$o" "$headers" "$f" "$o" "$f")
	done

	contents=$(replace "$contents" "HEADERS" "$headers")

	contents=$(replace "$contents" "BC_ENABLED" "$bc")
	contents=$(replace "$contents" "DC_ENABLED" "$dc")

	contents=$(replace "$contents" "BC_ALL_TESTS" "$bc_test")
	contents=$(replace "$contents" "BC_TESTS" "$bc_tests")
	contents=$(replace "$contents" "BC_SCRIPT_TESTS" "$bc_script_tests")
	contents=$(replace "$contents" "BC_TEST_EXEC" "$bc_test_exec")
	contents=$(replace "$contents" "TIMECONST_ALL_TESTS" "$timeconst")

	contents=$(replace "$contents" "DC_ALL_TESTS" "$dc_test")
	contents=$(replace "$contents" "DC_TESTS" "$dc_tests")
	contents=$(replace "$contents" "DC_SCRIPT_TESTS" "$dc_script_tests")
	contents=$(replace "$contents" "DC_TEST_EXEC" "$dc_test_exec")

	+contents=$(replace "$contents" "BUILD_TYPE" "$manpage_args")
	+
	contents=$(replace "$contents" "LIBRARY" "$library")
	contents=$(replace "$contents" "HISTORY" "$hist")
	contents=$(replace "$contents" "EXTRA_MATH" "$extra_math")
	contents=$(replace "$contents" "NLS" "$nls")
	contents=$(replace "$contents" "PROMPT" "$prompt")
	contents=$(replace "$contents" "FUZZ" "$fuzz")
	contents=$(replace "$contents" "MEMCHECK" "$memcheck")

	contents=$(replace "$contents" "BC_LIB_O" "$bc_lib")
	contents=$(replace "$contents" "BC_HELP_O" "$bc_help")
	contents=$(replace "$contents" "DC_HELP_O" "$dc_help")
	contents=$(replace "$contents" "BC_LIB2_O" "$BC_LIB2_O")
	contents=$(replace "$contents" "KARATSUBA_LEN" "$karatsuba_len")

	contents=$(replace "$contents" "NLSPATH" "$NLSPATH")
	contents=$(replace "$contents" "DESTDIR" "$destdir")
	contents=$(replace "$contents" "EXECSUFFIX" "$EXECSUFFIX")
	contents=$(replace "$contents" "EXECPREFIX" "$EXECPREFIX")
	contents=$(replace "$contents" "BINDIR" "$BINDIR")
	contents=$(replace "$contents" "INCLUDEDIR" "$INCLUDEDIR")
	contents=$(replace "$contents" "LIBDIR" "$LIBDIR")
	contents=$(replace "$contents" "MAN1DIR" "$MAN1DIR")
	contents=$(replace "$contents" "MAN3DIR" "$MAN3DIR")
	contents=$(replace "$contents" "CFLAGS" "$CFLAGS")
	contents=$(replace "$contents" "HOSTCFLAGS" "$HOSTCFLAGS")
	contents=$(replace "$contents" "CPPFLAGS" "$CPPFLAGS")
	contents=$(replace "$contents" "LDFLAGS" "$LDFLAGS")
	contents=$(replace "$contents" "CC" "$CC")
	contents=$(replace "$contents" "HOSTCC" "$HOSTCC")
	contents=$(replace "$contents" "COVERAGE_OUTPUT" "$COVERAGE_OUTPUT")
	contents=$(replace "$contents" "COVERAGE_PREREQS" "$COVERAGE_PREREQS")
	contents=$(replace "$contents" "INSTALL_PREREQS" "$install_prereqs")
	contents=$(replace "$contents" "INSTALL_MAN_PREREQS" "$install_man_prereqs")
	contents=$(replace "$contents" "INSTALL_LOCALES" "$install_locales")
	contents=$(replace "$contents" "INSTALL_LOCALES_PREREQS" "$install_locales_prereqs")
	contents=$(replace "$contents" "UNINSTALL_MAN_PREREQS" "$uninstall_man_prereqs")
	contents=$(replace "$contents" "UNINSTALL_PREREQS" "$uninstall_prereqs")
	contents=$(replace "$contents" "UNINSTALL_LOCALES_PREREQS" "$uninstall_locales_prereqs")

	contents=$(replace "$contents" "DEFAULT_TARGET" "$default_target")
	contents=$(replace "$contents" "DEFAULT_TARGET_PREREQS" "$default_target_prereqs")
	contents=$(replace "$contents" "DEFAULT_TARGET_CMD" "$default_target_cmd")
	contents=$(replace "$contents" "SECOND_TARGET" "$second_target")
	contents=$(replace "$contents" "SECOND_TARGET_PREREQS" "$second_target_prereqs")
	contents=$(replace "$contents" "SECOND_TARGET_CMD" "$second_target_cmd")

	contents=$(replace "$contents" "ALL_PREREQ" "$ALL_PREREQ")
	contents=$(replace "$contents" "BC_EXEC_PREREQ" "$bc_exec_prereq")
	contents=$(replace "$contents" "BC_EXEC_CMD" "$bc_exec_cmd")
	contents=$(replace "$contents" "DC_EXEC_PREREQ" "$dc_exec_prereq")
	contents=$(replace "$contents" "DC_EXEC_CMD" "$dc_exec_cmd")

	contents=$(replace "$contents" "EXECUTABLES" "$executables")
	contents=$(replace "$contents" "MAIN_EXEC" "$main_exec")
	contents=$(replace "$contents" "EXEC" "$executable")
	contents=$(replace "$contents" "TESTS" "$tests")

	contents=$(replace "$contents" "BC_TEST" "$bc_test")
	contents=$(replace "$contents" "DC_TEST" "$dc_test")

	contents=$(replace "$contents" "VG_BC_TEST" "$vg_bc_test")
	contents=$(replace "$contents" "VG_DC_TEST" "$vg_dc_test")

	contents=$(replace "$contents" "TIMECONST" "$timeconst")

	contents=$(replace "$contents" "KARATSUBA" "$karatsuba")
	contents=$(replace "$contents" "KARATSUBA_TEST" "$karatsuba_test")

	contents=$(replace "$contents" "LONG_BIT" "$LONG_BIT")
	contents=$(replace "$contents" "LONG_BIT_DEFINE" "$LONG_BIT_DEFINE")

	contents=$(replace "$contents" "GEN" "$GEN")
	contents=$(replace "$contents" "GEN_EXEC_TARGET" "$GEN_EXEC_TARGET")
	contents=$(replace "$contents" "CLEAN_PREREQS" "$CLEAN_PREREQS")
	contents=$(replace "$contents" "GEN_EMU" "$GEN_EMU")

	printf '%s\n%s\n\n' "$contents" "$SRC_TARGETS" > "$scriptdir/Makefile"

	if [ "$bc" -ne 0 ]; then
	gen_tests bc BC "$extra_math" "$time_tests" $bc_test_exec
	gen_script_tests bc "$extra_math" "$generate_tests" "$time_tests" $bc_test_exec
	fi

	if [ "$dc" -ne 0 ]; then
	gen_tests dc DC "$extra_math" "$time_tests" $dc_test_exec
	gen_script_tests dc "$extra_math" "$generate_tests" "$time_tests" $dc_test_exec
	fi

	cd "$scriptdir"

	cp -f manuals/bc/$manpage_args.1.md manuals/bc.1.md
	cp -f manuals/bc/$manpage_args.1 manuals/bc.1
	cp -f manuals/dc/$manpage_args.1.md manuals/dc.1.md
	cp -f manuals/dc/$manpage_args.1 manuals/dc.1

	make clean > /dev/null
	diff --git a/contrib/bc/gen/bc_help.txt b/contrib/bc/gen/bc_help.txt
	index 3f5aac892268..c9b0482d8c42 100644
	--- a/contrib/bc/gen/bc_help.txt
	+++ b/contrib/bc/gen/bc_help.txt
	@@ -1,120 +1,125 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* The bc help text.
	*
	*/

	usage: %s [options] [file...]

	bc is a command-line, arbitrary-precision calculator with a Turing-complete
	-language. For details, use `man %s`.
	+language. For details, use `man %s` or see the online documentation at
	+https://git.yzena.com/gavin/bc/src/tag/%s/manuals/bc/%s.1.md.

	This bc is compatible with both the GNU bc and the POSIX bc spec. See the GNU bc
	manual (https://www.gnu.org/software/bc/manual/bc.html) and bc spec
	(http://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	for details.

	This bc has three differences to the GNU bc:

	1) Arrays can be passed to the builtin "length" function to get the number of
	elements currently in the array. The following example prints "1":

	a[0] = 0
	length(a[])

	2) The precedence of the boolean "not" operator (!) is equal to that of the
	unary minus (-), or negation, operator. This still allows POSIX-compliant
	scripts to work while somewhat preserving expected behavior (versus C) and
	making parsing easier.
	3) This bc has many more extensions than the GNU bc does. For details, see the
	- man page.
	+ man page or online documentation.

	This bc also implements the dot (.) extension of the BSD bc.

	Options:

	-e expr --expression=expr

	Run "expr" and quit. If multiple expressions or files (see below) are
	given, they are all run before executing from stdin.

	-f file --file=file

	Run the bc code in "file" and exit. See above as well.

	-g --global-stacks

	Turn scale, ibase, and obase into stacks. This makes the value of each be
	- be restored on returning from functions. See the man page for more
	- details.
	+ be restored on returning from functions. See the man page or online
	+ documentation for more details.

	-h --help

	Print this usage message and exit.

	-i --interactive

	Force interactive mode.

	-l --mathlib

	Use predefined math routines:

	s(expr) = sine of expr in radians
	c(expr) = cosine of expr in radians
	a(expr) = arctangent of expr, returning radians
	l(expr) = natural log of expr
	e(expr) = raises e to the power of expr
	j(n, x) = Bessel function of integer order n of x

	- This bc may load more functions with these options. See the manpage for
	- details.
	+ This bc may load more functions with these options. See the manpage or
	+ online documentation for details.

	-P --no-prompt

	- Disable the prompt in interactive mode.
	+ Disable the prompts in interactive mode.
	+
	+ -R --no-read-prompt
	+
	+ Disable the read prompt in interactive mode.

	-q --quiet

	Don't print version and copyright.

	-s --standard

	Error if any non-POSIX extensions are used.

	-w --warn

	Warn if any non-POSIX extensions are used.

	-v --version

	Print version information and copyright and exit.
	diff --git a/contrib/bc/gen/dc_help.txt b/contrib/bc/gen/dc_help.txt
	index 4b6a61c872f6..c573b96791e7 100644
	--- a/contrib/bc/gen/dc_help.txt
	+++ b/contrib/bc/gen/dc_help.txt
	@@ -1,101 +1,106 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* The dc help text.
	*
	*/

	usage: %s [options] [file...]

	dc is a reverse-polish notation command-line calculator which supports unlimited
	-precision arithmetic. For details, use `man %s`.
	+precision arithmetic. For details, use `man %s` or see the online documentation
	+at https://git.yzena.com/gavin/bc/src/tag/%s/manuals/bc/%s.1.md.

	-This dc is (mostly) compatible with the FreeBSD dc and the GNU dc. See the
	-FreeBSD man page (https://www.unix.com/man-page/FreeBSD/1/dc/) and the GNU dc
	-manual (https://www.gnu.org/software/bc/manual/dc-1.05/html_mono/dc.html) for
	-details.
	+This dc is (mostly) compatible with the OpenBSD dc and the GNU dc. See the
	+OpenBSD man page (http://man.openbsd.org/OpenBSD-current/man1/dc.1) and the GNU
	+dc manual (https://www.gnu.org/software/bc/manual/dc-1.05/html_mono/dc.html)
	+for details.

	This dc has a few differences from the two above:

	1) When printing a byte stream (command "P"), this bc follows what the FreeBSD
	dc does.
	2) This dc implements the GNU extensions for divmod ("~") and modular
	exponentiation ("\|").
	3) This dc implements all FreeBSD extensions, except for "J" and "M".
	4) This dc does not implement the run command ("!"), for security reasons.
	5) Like the FreeBSD dc, this dc supports extended registers. However, they are
	implemented differently. When it encounters whitespace where a register
	should be, it skips the whitespace. If the character following is not
	a lowercase letter, an error is issued. Otherwise, the register name is
	parsed by the following regex:

	[a-z][a-z0-9_]*

	This generally means that register names will be surrounded by whitespace.

	Examples:

	l idx s temp L index S temp2 < do_thing

	Also note that, unlike the FreeBSD dc, extended registers are not even
	parsed unless the "-x" option is given. Instead, the space after a command
	that requires a register name is taken as the register name.

	Options:

	-e expr --expression=expr

	Run "expr" and quit. If multiple expressions or files (see below) are
	given, they are all run. After running, dc will exit.

	-f file --file=file

	Run the dc code in "file" and exit. See above.

	-h --help

	Print this usage message and exit.

	-i --interactive

	Put dc into interactive mode. See the man page for more details.

	-P --no-prompt

	- Disable the prompt in interactive mode.
	+ Disable the prompts in interactive mode.
	+
	+ -R --no-read-prompt
	+
	+ Disable the read prompt in interactive mode.

	-V --version

	Print version and copyright and exit.

	-x --extended-register

	Enable extended register mode.
	diff --git a/contrib/bc/gen/strgen.c b/contrib/bc/gen/strgen.c
	index 2d133ba51e68..fbc694a37622 100644
	--- a/contrib/bc/gen/strgen.c
	+++ b/contrib/bc/gen/strgen.c
	@@ -1,144 +1,194 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Generates a const array from a bc script.
	*
	*/

	#include <stdbool.h>
	#include <stdio.h>
	#include <stdlib.h>
	#include <string.h>

	#include <errno.h>

	+#ifndef _WIN32
	#include <libgen.h>
	+#endif // _WIN32

	static const char* const bc_gen_header =
	"// Copyright (c) 2018-2021 Gavin D. Howard and contributors.\n"
	"// Licensed under the 2-clause BSD license.\n"
	"// * AUTOMATICALLY GENERATED FROM %s. DO NOT MODIFY. *\n\n";

	static const char* const bc_gen_label = "const char *%s = \"%s\";\n\n";
	static const char* const bc_gen_label_extern = "extern const char *%s;\n\n";
	static const char* const bc_gen_ifdef = "#if %s\n";
	static const char* const bc_gen_endif = "#endif // %s\n";
	static const char* const bc_gen_name = "const char %s[] = {\n";
	static const char* const bc_gen_name_extern = "extern const char %s[];\n\n";

	#define IO_ERR (1)
	#define INVALID_INPUT_FILE (2)
	#define INVALID_PARAMS (3)

	#define MAX_WIDTH (74)

	+static void open_file(FILE** f, const char* filename, const char* mode) {
	+
	+#ifndef _WIN32
	+ *f = fopen(filename, mode);
	+#else // _WIN32
	+ *f = NULL;
	+ fopen_s(f, filename, mode);
	+#endif // _WIN32
	+}
	+
	+static int output_label(FILE* out, const char* label, const char* name) {
	+
	+#ifndef _WIN32
	+ return fprintf(out, bc_gen_label, label, name);
	+#else // _WIN32
	+
	+ size_t i, count = 0, len = strlen(name);
	+ char* buf;
	+ int ret;
	+
	+ for (i = 0; i < len; ++i) {
	+ count += (name[i] == '\\');
	+ }
	+
	+ buf = (char*) malloc(len + 1 + count);
	+ if (buf == NULL) return -1;
	+
	+ count = 0;
	+
	+ for (i = 0; i < len; ++i) {
	+ buf[i + count] = name[i];
	+ if (name[i] == '\\') {
	+ count += 1;
	+ buf[i + count] = name[i];
	+ }
	+ }
	+
	+ buf[i + count] = '\0';
	+
	+ ret = fprintf(out, bc_gen_label, label, buf);
	+
	+ free(buf);
	+
	+ return ret;
	+
	+#endif // _WIN32
	+}
	+
	int main(int argc, char *argv[]) {

	FILE in, out;
	char label, define, *name;
	int c, count, slashes, err = IO_ERR;
	bool has_label, has_define, remove_tabs;

	if (argc < 5) {
	printf("usage: %s input output name header [label [define [remove_tabs]]]\n", argv[0]);
	return INVALID_PARAMS;
	}

	name = argv[3];

	has_label = (argc > 4 && strcmp("", argv[4]) != 0);
	label = has_label ? argv[4] : "";

	has_define = (argc > 5 && strcmp("", argv[5]) != 0);
	define = has_define ? argv[5] : "";

	remove_tabs = (argc > 6);

	- in = fopen(argv[1], "r");
	+ open_file(&in, argv[1], "r");
	if (!in) return INVALID_INPUT_FILE;

	- out = fopen(argv[2], "w");
	+ open_file(&out, argv[2], "w");
	if (!out) goto out_err;

	if (fprintf(out, bc_gen_header, argv[1]) < 0) goto err;
	if (has_label && fprintf(out, bc_gen_label_extern, label) < 0) goto err;
	if (fprintf(out, bc_gen_name_extern, name) < 0) goto err;
	if (has_define && fprintf(out, bc_gen_ifdef, define) < 0) goto err;
	- if (has_label && fprintf(out, bc_gen_label, label, argv[1]) < 0) goto err;
	+ if (has_label && output_label(out, label, argv[1]) < 0) goto err;
	if (fprintf(out, bc_gen_name, name) < 0) goto err;

	c = count = slashes = 0;

	while (slashes < 2 && (c = fgetc(in)) >= 0) {
	slashes += (slashes == 1 && c == '/' && fgetc(in) == '\n');
	slashes += (!slashes && c == '/' && fgetc(in) == '*');
	}

	if (c < 0) {
	err = INVALID_INPUT_FILE;
	goto err;
	}

	while ((c = fgetc(in)) == '\n');

	while (c >= 0) {

	int val;

	if (!remove_tabs \|\| c != '\t') {

	if (!count && fputc('\t', out) == EOF) goto err;

	val = fprintf(out, "%d,", c);
	if (val < 0) goto err;

	count += val;

	if (count > MAX_WIDTH) {
	count = 0;
	if (fputc('\n', out) == EOF) goto err;
	}
	}

	c = fgetc(in);
	}

	if (!count && (fputc(' ', out) == EOF \|\| fputc(' ', out) == EOF)) goto err;
	if (fprintf(out, "0\n};\n") < 0) goto err;

	err = (has_define && fprintf(out, bc_gen_endif, define) < 0);

	err:
	fclose(out);
	out_err:
	fclose(in);
	return err;
	}
	diff --git a/contrib/bc/include/bcl.h b/contrib/bc/include/bcl.h
	index 3c67beb23122..3efb028bab62 100644
	--- a/contrib/bc/include/bcl.h
	+++ b/contrib/bc/include/bcl.h
	@@ -1,184 +1,286 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* The public header for the bc library.
	*
	*/

	#ifndef BC_BCL_H
	#define BC_BCL_H

	+#ifdef _WIN32
	+#include <Windows.h>
	+#include <BaseTsd.h>
	+#include <stdio.h>
	+#include <io.h>
	+#endif // _WIN32
	+
	#include <stdbool.h>
	#include <stdlib.h>
	#include <limits.h>
	#include <stdint.h>
	#include <sys/types.h>

	#define BC_SEED_ULONGS (4)
	#define BC_SEED_SIZE (sizeof(long) * BC_SEED_ULONGS)

	// For some reason, LONG_BIT is not defined in some versions of gcc.
	// I define it here to the minimum accepted value in the POSIX standard.
	#ifndef LONG_BIT
	#define LONG_BIT (32)
	#endif // LONG_BIT

	#ifndef BC_LONG_BIT
	#define BC_LONG_BIT LONG_BIT
	#endif // BC_LONG_BIT

	#if BC_LONG_BIT > LONG_BIT
	#error BC_LONG_BIT cannot be greater than LONG_BIT
	#endif // BC_LONG_BIT > LONG_BIT

	#if BC_LONG_BIT >= 64

	typedef uint64_t BclBigDig;
	typedef uint64_t BclRandInt;

	#elif BC_LONG_BIT >= 32

	typedef uint32_t BclBigDig;
	typedef uint32_t BclRandInt;

	#else

	#error BC_LONG_BIT must be at least 32

	#endif // BC_LONG_BIT >= 64
	+#define BC_UNUSED(e) ((void) (e))
	+
	+#ifndef BC_LIKELY
	+#define BC_LIKELY(e) (e)
	+#endif // BC_LIKELY
	+
	+#ifndef BC_UNLIKELY
	+#define BC_UNLIKELY(e) (e)
	+#endif // BC_UNLIKELY
	+
	+#define BC_ERR(e) BC_UNLIKELY(e)
	+#define BC_NO_ERR(s) BC_LIKELY(s)
	+
	+#ifndef BC_DEBUG_CODE
	+#define BC_DEBUG_CODE (0)
	+#endif // BC_DEBUG_CODE
	+
	+#if __STDC_VERSION__ >= 201100L
	+#include <stdnoreturn.h>
	+#define BC_NORETURN _Noreturn
	+#else // __STDC_VERSION__
	+#define BC_NORETURN
	+#define BC_MUST_RETURN
	+#endif // __STDC_VERSION__
	+
	+#if defined(__clang__) \|\| defined(__GNUC__)
	+#if defined(__has_attribute)
	+#if __has_attribute(fallthrough)
	+#define BC_FALLTHROUGH __attribute__((fallthrough));
	+#else // __has_attribute(fallthrough)
	+#define BC_FALLTHROUGH
	+#endif // __has_attribute(fallthrough)
	+#else // defined(__has_attribute)
	+#define BC_FALLTHROUGH
	+#endif // defined(__has_attribute)
	+#else // defined(__clang__) \|\| defined(__GNUC__)
	+#define BC_FALLTHROUGH
	+#endif // defined(__clang__) \|\| defined(__GNUC__)
	+
	+// Workarounds for AIX's POSIX incompatibility.
	+#ifndef SIZE_MAX
	+#define SIZE_MAX __SIZE_MAX__
	+#endif // SIZE_MAX
	+#ifndef UINTMAX_C
	+#define UINTMAX_C __UINTMAX_C
	+#endif // UINTMAX_C
	+#ifndef UINT32_C
	+#define UINT32_C __UINT32_C
	+#endif // UINT32_C
	+#ifndef UINT_FAST32_MAX
	+#define UINT_FAST32_MAX __UINT_FAST32_MAX__
	+#endif // UINT_FAST32_MAX
	+#ifndef UINT16_MAX
	+#define UINT16_MAX __UINT16_MAX__
	+#endif // UINT16_MAX
	+#ifndef SIG_ATOMIC_MAX
	+#define SIG_ATOMIC_MAX __SIG_ATOMIC_MAX__
	+#endif // SIG_ATOMIC_MAX
	+
	+// Windows has deprecated isatty() and the rest of these.
	+// Or doesn't have them.
	+#ifdef _WIN32
	+
	+// This one is special. Windows did not like me defining an
	+// inline function that was not given a definition in a header
	+// file. This suppresses that by making inline functions non-inline.
	+#define inline
	+
	+#define restrict __restrict
	+#define strdup _strdup
	+#define write(f, b, s) _write((f), (b), (unsigned int) (s))
	+#define read(f, b, s) _read((f), (b), (unsigned int) (s))
	+#define close _close
	+#define open(f, n, m) _sopen_s(f, n, m, _SH_DENYNO, _S_IREAD \| _S_IWRITE)
	+#define sigjmp_buf jmp_buf
	+#define sigsetjmp(j, s) setjmp(j)
	+#define siglongjmp longjmp
	+#define isatty _isatty
	+#define STDIN_FILENO (0)
	+#define STDOUT_FILENO (1)
	+#define STDERR_FILENO (2)
	+#define ssize_t SSIZE_T
	+#define S_ISDIR(m) ((m) & _S_IFDIR)
	+#define O_RDONLY _O_RDONLY
	+#define stat _stat
	+#define fstat _fstat
	+#define BC_FILE_SEP '\\'
	+
	+#else // _WIN32
	+#define BC_FILE_SEP '/'
	+#endif // _WIN32
	+
	+#if BC_ENABLE_LIBRARY

	typedef enum BclError {

	BCL_ERROR_NONE,

	BCL_ERROR_INVALID_NUM,
	BCL_ERROR_INVALID_CONTEXT,
	BCL_ERROR_SIGNAL,

	BCL_ERROR_MATH_NEGATIVE,
	BCL_ERROR_MATH_NON_INTEGER,
	BCL_ERROR_MATH_OVERFLOW,
	BCL_ERROR_MATH_DIVIDE_BY_ZERO,

	BCL_ERROR_PARSE_INVALID_STR,

	BCL_ERROR_FATAL_ALLOC_ERR,
	BCL_ERROR_FATAL_UNKNOWN_ERR,

	BCL_ERROR_NELEMS,

	} BclError;

	typedef struct BclNumber {

	size_t i;

	} BclNumber;

	struct BclCtxt;

	typedef struct BclCtxt* BclContext;

	void bcl_handleSignal(void);
	bool bcl_running(void);

	BclError bcl_init(void);
	void bcl_free(void);

	bool bcl_abortOnFatalError(void);
	void bcl_setAbortOnFatalError(bool abrt);

	void bcl_gc(void);

	BclError bcl_pushContext(BclContext ctxt);
	void bcl_popContext(void);
	BclContext bcl_context(void);

	BclContext bcl_ctxt_create(void);
	void bcl_ctxt_free(BclContext ctxt);
	void bcl_ctxt_freeNums(BclContext ctxt);

	size_t bcl_ctxt_scale(BclContext ctxt);
	void bcl_ctxt_setScale(BclContext ctxt, size_t scale);
	size_t bcl_ctxt_ibase(BclContext ctxt);
	void bcl_ctxt_setIbase(BclContext ctxt, size_t ibase);
	size_t bcl_ctxt_obase(BclContext ctxt);
	void bcl_ctxt_setObase(BclContext ctxt, size_t obase);

	BclError bcl_err(BclNumber n);

	BclNumber bcl_num_create(void);
	void bcl_num_free(BclNumber n);

	bool bcl_num_neg(BclNumber n);
	void bcl_num_setNeg(BclNumber n, bool neg);
	size_t bcl_num_scale(BclNumber n);
	BclError bcl_num_setScale(BclNumber n, size_t scale);
	size_t bcl_num_len(BclNumber n);

	BclError bcl_copy(BclNumber d, BclNumber s);
	BclNumber bcl_dup(BclNumber s);

	BclError bcl_bigdig(BclNumber n, BclBigDig *result);
	BclNumber bcl_bigdig2num(BclBigDig val);

	BclNumber bcl_add(BclNumber a, BclNumber b);
	BclNumber bcl_sub(BclNumber a, BclNumber b);
	BclNumber bcl_mul(BclNumber a, BclNumber b);
	BclNumber bcl_div(BclNumber a, BclNumber b);
	BclNumber bcl_mod(BclNumber a, BclNumber b);
	BclNumber bcl_pow(BclNumber a, BclNumber b);
	BclNumber bcl_lshift(BclNumber a, BclNumber b);
	BclNumber bcl_rshift(BclNumber a, BclNumber b);
	BclNumber bcl_sqrt(BclNumber a);
	BclError bcl_divmod(BclNumber a, BclNumber b, BclNumber c, BclNumber d);
	BclNumber bcl_modexp(BclNumber a, BclNumber b, BclNumber c);

	ssize_t bcl_cmp(BclNumber a, BclNumber b);

	void bcl_zero(BclNumber n);
	void bcl_one(BclNumber n);

	BclNumber bcl_parse(const char *restrict val);
	char* bcl_string(BclNumber n);

	BclNumber bcl_irand(BclNumber a);
	BclNumber bcl_frand(size_t places);
	BclNumber bcl_ifrand(BclNumber a, size_t places);

	BclError bcl_rand_seedWithNum(BclNumber n);
	BclError bcl_rand_seed(unsigned char seed[BC_SEED_SIZE]);
	void bcl_rand_reseed(void);
	BclNumber bcl_rand_seed2num(void);
	BclRandInt bcl_rand_int(void);
	BclRandInt bcl_rand_bounded(BclRandInt bound);

	+#endif // BC_ENABLE_LIBRARY
	+
	#endif // BC_BCL_H
	diff --git a/contrib/bc/include/file.h b/contrib/bc/include/file.h
	index 1c3273b7a756..fbd4b9b9f9b3 100644
	--- a/contrib/bc/include/file.h
	+++ b/contrib/bc/include/file.h
	@@ -1,65 +1,89 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Definitions for implementing buffered I/O on my own terms.
	*
	*/

	#ifndef BC_FILE_H
	#define BC_FILE_H

	#include <stdarg.h>

	#include <vector.h>

	#define BC_FILE_ULL_LENGTH (21)

	typedef struct BcFile {

	int fd;
	char *buf;
	size_t len;
	size_t cap;

	} BcFile;

	+#if BC_ENABLE_HISTORY
	+typedef enum BcFlushType {
	+
	+ BC_FLUSH_NO_EXTRAS_NO_CLEAR,
	+ BC_FLUSH_SAVE_EXTRAS_NO_CLEAR,
	+ BC_FLUSH_NO_EXTRAS_CLEAR,
	+ BC_FLUSH_SAVE_EXTRAS_CLEAR,
	+
	+} BcFlushType;
	+#else // BC_ENABLE_HISTORY
	+#define bc_file_putchar(f, t, c) bc_file_putchar(f, c)
	+#define bc_file_flushErr(f, t) bc_file_flushErr(f)
	+#define bc_file_flush(f, t) bc_file_flush(f)
	+#define bc_file_write(f, t, b, n) bc_file_write(f, b, n)
	+#define bc_file_puts(f, t, s) bc_file_puts(f, s)
	+#endif // BC_ENABLE_HISTORY
	+
	void bc_file_init(BcFile f, int fd, char buf, size_t cap);
	void bc_file_free(BcFile *f);

	-void bc_file_putchar(BcFile *restrict f, uchar c);
	-BcStatus bc_file_flushErr(BcFile *restrict f);
	-void bc_file_flush(BcFile *restrict f);
	-void bc_file_write(BcFile restrict f, const char buf, size_t n);
	+void bc_file_putchar(BcFile *restrict f, BcFlushType type, uchar c);
	+BcStatus bc_file_flushErr(BcFile *restrict f, BcFlushType type);
	+void bc_file_flush(BcFile *restrict f, BcFlushType type);
	+void bc_file_write(BcFile *restrict f, BcFlushType type,
	+ const char *buf, size_t n);
	void bc_file_printf(BcFile restrict f, const char fmt, ...);
	void bc_file_vprintf(BcFile restrict f, const char fmt, va_list args);
	-void bc_file_puts(BcFile restrict f, const char str);
	+void bc_file_puts(BcFile restrict f, BcFlushType type, const char str);
	+
	+#if BC_ENABLE_HISTORY
	+extern const BcFlushType bc_flush_none;
	+extern const BcFlushType bc_flush_err;
	+extern const BcFlushType bc_flush_save;
	+#endif // BC_ENABLE_HISTORY

	#endif // BC_FILE_H
	diff --git a/contrib/bc/include/history.h b/contrib/bc/include/history.h
	index d3622ae15a30..469785a118a9 100644
	--- a/contrib/bc/include/history.h
	+++ b/contrib/bc/include/history.h
	@@ -1,258 +1,261 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Adapted from the following:
	*
	* linenoise.c -- guerrilla line editing library against the idea that a
	* line editing lib needs to be 20,000 lines of C code.
	*
	* You can find the original source code at:
	* http://github.com/antirez/linenoise
	*
	* You can find the fork that this code is based on at:
	* https://github.com/rain-1/linenoise-mob
	*
	* ------------------------------------------------------------------------
	*
	* This code is also under the following license:
	*
	* Copyright (c) 2010-2016, Salvatore Sanfilippo <antirez at gmail dot com>
	* Copyright (c) 2010-2013, Pieter Noordhuis <pcnoordhuis at gmail dot com>
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are
	* met:
	*
	* * Redistributions of source code must retain the above copyright
	* notice, this list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT
	* HOLDER 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.
	*
	* *****************************************************************************
	*
	* Definitions for line history.
	*
	*/

	#ifndef BC_HISTORY_H
	#define BC_HISTORY_H

	#ifndef BC_ENABLE_HISTORY
	#define BC_ENABLE_HISTORY (1)
	#endif // BC_ENABLE_HISTORY

	#if BC_ENABLE_HISTORY

	#ifdef _WIN32
	#error History is not supported on Windows.
	#endif // _WIN32

	#include <stdbool.h>
	#include <stddef.h>

	#include <signal.h>

	#include <termios.h>
	#include <time.h>
	#include <unistd.h>
	#include <sys/select.h>

	#include <status.h>
	#include <vector.h>
	#include <read.h>

	#if BC_DEBUG_CODE
	#include <file.h>
	#endif // BC_DEBUG_CODE

	#define BC_HIST_DEF_COLS (80)
	#define BC_HIST_MAX_LEN (128)
	#define BC_HIST_MAX_LINE (4095)
	#define BC_HIST_SEQ_SIZE (64)

	#define BC_HIST_BUF_LEN(h) ((h)->buf.len - 1)
	#define BC_HIST_READ(s, n) (bc_history_read((s), (n)) == -1)

	#define BC_HIST_NEXT (false)
	#define BC_HIST_PREV (true)

	#if BC_DEBUG_CODE

	#define BC_HISTORY_DEBUG_BUF_SIZE (1024)

	#define lndebug(...) \
	do { \
	if (bc_history_debug_fp.fd == 0) { \
	bc_history_debug_buf = bc_vm_malloc(BC_HISTORY_DEBUG_BUF_SIZE); \
	bc_file_init(&bc_history_debug_fp, \
	open("/tmp/lndebug.txt", O_APPEND), \
	BC_HISTORY_DEBUG_BUF_SIZE); \
	bc_file_printf(&bc_history_debug_fp, \
	"[%zu %zu %zu] p: %d, rows: %d, " \
	"rpos: %d, max: %zu, oldmax: %d\n", \
	l->len, l->pos, l->oldcolpos, plen, rows, rpos, \
	l->maxrows, old_rows); \
	} \
	bc_file_printf(&bc_history_debug_fp, ", " __VA_ARGS__); \
	bc_file_flush(&bc_history_debug_fp); \
	} while (0)
	#else // BC_DEBUG_CODE
	#define lndebug(fmt, ...)
	#endif // BC_DEBUG_CODE

	#if !BC_ENABLE_PROMPT
	#define bc_history_line(h, vec, prompt) bc_history_line(h, vec)
	#define bc_history_raw(h, prompt) bc_history_raw(h)
	#define bc_history_edit(h, prompt) bc_history_edit(h)
	#endif // BC_ENABLE_PROMPT

	typedef enum BcHistoryAction {

	BC_ACTION_NULL = 0,
	BC_ACTION_CTRL_A = 1,
	BC_ACTION_CTRL_B = 2,
	BC_ACTION_CTRL_C = 3,
	BC_ACTION_CTRL_D = 4,
	BC_ACTION_CTRL_E = 5,
	BC_ACTION_CTRL_F = 6,
	BC_ACTION_CTRL_H = 8,
	BC_ACTION_TAB = 9,
	BC_ACTION_LINE_FEED = 10,
	BC_ACTION_CTRL_K = 11,
	BC_ACTION_CTRL_L = 12,
	BC_ACTION_ENTER = 13,
	BC_ACTION_CTRL_N = 14,
	BC_ACTION_CTRL_P = 16,
	BC_ACTION_CTRL_T = 20,
	BC_ACTION_CTRL_U = 21,
	BC_ACTION_CTRL_W = 23,
	BC_ACTION_CTRL_Z = 26,
	BC_ACTION_ESC = 27,
	BC_ACTION_BACKSPACE = 127

	} BcHistoryAction;

	/**
	* This represents the state during line editing. We pass this state
	* to functions implementing specific editing functionalities.
	*/
	typedef struct BcHistory {

	/// Edited line buffer.
	BcVec buf;

	/// The history.
	BcVec history;

	+ /// Any material printed without a trailing newline.
	+ BcVec extras;
	+
	#if BC_ENABLE_PROMPT
	/// Prompt to display.
	const char *prompt;

	/// Prompt length.
	size_t plen;
	#endif // BC_ENABLE_PROMPT

	/// Prompt column length.
	size_t pcol;

	/// Current cursor position.
	size_t pos;

	/// Previous refresh cursor column position.
	size_t oldcolpos;

	/// Number of columns in terminal.
	size_t cols;

	/// The history index we are currently editing.
	size_t idx;

	/// The original terminal state.
	struct termios orig_termios;

	/// These next three are here because pahole found a 4 byte hole here.

	/// This is to signal that there is more, so we don't process yet.
	bool stdin_has_data;

	/// Whether we are in rawmode.
	bool rawMode;

	/// Whether the terminal is bad.
	bool badTerm;

	/// This is to check if stdin has more data.
	fd_set rdset;

	/// This is to check if stdin has more data.
	struct timespec ts;

	/// This is to check if stdin has more data.
	sigset_t sigmask;

	} BcHistory;

	BcStatus bc_history_line(BcHistory h, BcVec vec, const char *prompt);

	void bc_history_init(BcHistory *h);
	void bc_history_free(BcHistory *h);

	extern const char *bc_history_bad_terms[];
	extern const char bc_history_tab[];
	extern const size_t bc_history_tab_len;
	extern const char bc_history_ctrlc[];
	extern const uint32_t bc_history_wchars[][2];
	extern const size_t bc_history_wchars_len;
	extern const uint32_t bc_history_combo_chars[];
	extern const size_t bc_history_combo_chars_len;
	#if BC_DEBUG_CODE
	extern BcFile bc_history_debug_fp;
	extern char *bc_history_debug_buf;
	void bc_history_printKeyCodes(BcHistory* l);
	#endif // BC_DEBUG_CODE

	#endif // BC_ENABLE_HISTORY

	#endif // BC_HISTORY_H
	diff --git a/contrib/bc/include/num.h b/contrib/bc/include/num.h
	index 2104f8b8acad..8beea00189db 100644
	--- a/contrib/bc/include/num.h
	+++ b/contrib/bc/include/num.h
	@@ -1,263 +1,264 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Definitions for the num type.
	*
	*/

	#ifndef BC_NUM_H
	#define BC_NUM_H

	#include <limits.h>
	#include <stdbool.h>
	#include <stddef.h>
	#include <stdint.h>

	#include <sys/types.h>

	#include <status.h>
	#include <vector.h>
	#include <bcl.h>

	#ifndef BC_ENABLE_EXTRA_MATH
	#define BC_ENABLE_EXTRA_MATH (1)
	#endif // BC_ENABLE_EXTRA_MATH

	#define BC_BASE (10)

	typedef unsigned long ulong;

	typedef BclBigDig BcBigDig;

	#if BC_LONG_BIT >= 64

	#define BC_NUM_BIGDIG_MAX ((BcBigDig) UINT64_MAX)

	#define BC_BASE_DIGS (9)
	#define BC_BASE_POW (1000000000)

	#define BC_NUM_BIGDIG_C UINT64_C

	typedef int_least32_t BcDig;

	#elif BC_LONG_BIT >= 32

	#define BC_NUM_BIGDIG_MAX ((BcBigDig) UINT32_MAX)

	#define BC_BASE_DIGS (4)
	#define BC_BASE_POW (10000)

	#define BC_NUM_BIGDIG_C UINT32_C

	typedef int_least16_t BcDig;

	#else

	#error BC_LONG_BIT must be at least 32

	#endif // BC_LONG_BIT >= 64

	#define BC_NUM_DEF_SIZE (8)

	typedef struct BcNum {
	BcDig *restrict num;
	size_t rdx;
	size_t scale;
	size_t len;
	size_t cap;
	} BcNum;

	#if BC_ENABLE_EXTRA_MATH

	#ifndef BC_ENABLE_RAND
	#define BC_ENABLE_RAND (1)
	#endif // BC_ENABLE_RAND

	#if BC_ENABLE_RAND
	// Forward declaration
	struct BcRNG;
	#endif // BC_ENABLE_RAND

	#endif // BC_ENABLE_EXTRA_MATH

	#define BC_NUM_MIN_BASE (BC_NUM_BIGDIG_C(2))
	#define BC_NUM_MAX_POSIX_IBASE (BC_NUM_BIGDIG_C(16))
	#define BC_NUM_MAX_IBASE (BC_NUM_BIGDIG_C(36))
	// This is the max base allowed by bc_num_parseChar().
	#define BC_NUM_MAX_LBASE (BC_NUM_BIGDIG_C('Z' + BC_BASE + 1))
	#define BC_NUM_PRINT_WIDTH (BC_NUM_BIGDIG_C(69))

	#ifndef BC_NUM_KARATSUBA_LEN
	#define BC_NUM_KARATSUBA_LEN (BC_NUM_BIGDIG_C(32))
	#elif BC_NUM_KARATSUBA_LEN < 16
	#error BC_NUM_KARATSUBA_LEN must be at least 16.
	#endif // BC_NUM_KARATSUBA_LEN

	// A crude, but always big enough, calculation of
	// the size required for ibase and obase BcNum's.
	#define BC_NUM_BIGDIG_LOG10 (BC_NUM_DEF_SIZE)

	#define BC_NUM_NONZERO(n) ((n)->len)
	#define BC_NUM_ZERO(n) (!BC_NUM_NONZERO(n))
	#define BC_NUM_ONE(n) ((n)->len == 1 && (n)->rdx == 0 && (n)->num[0] == 1)

	#define BC_NUM_NUM_LETTER(c) ((c) - 'A' + BC_BASE)

	#define BC_NUM_KARATSUBA_ALLOCS (6)

	#define BC_NUM_ROUND_POW(s) (bc_vm_growSize((s), BC_BASE_DIGS - 1))
	#define BC_NUM_RDX(s) (BC_NUM_ROUND_POW(s) / BC_BASE_DIGS)

	#define BC_NUM_RDX_VAL(n) ((n)->rdx >> 1)
	#define BC_NUM_RDX_VAL_NP(n) ((n).rdx >> 1)
	#define BC_NUM_RDX_SET(n, v) \
	((n)->rdx = (((v) << 1) \| ((n)->rdx & (BcBigDig) 1)))
	#define BC_NUM_RDX_SET_NP(n, v) \
	((n).rdx = (((v) << 1) \| ((n).rdx & (BcBigDig) 1)))
	#define BC_NUM_RDX_SET_NEG(n, v, neg) \
	((n)->rdx = (((v) << 1) \| (neg)))

	#define BC_NUM_RDX_VALID(n) \
	(BC_NUM_ZERO(n) \|\| BC_NUM_RDX_VAL(n) * BC_BASE_DIGS >= (n)->scale)
	#define BC_NUM_RDX_VALID_NP(n) \
	((!(n).len) \|\| BC_NUM_RDX_VAL_NP(n) * BC_BASE_DIGS >= (n).scale)

	#define BC_NUM_NEG(n) ((n)->rdx & ((BcBigDig) 1))
	#define BC_NUM_NEG_NP(n) ((n).rdx & ((BcBigDig) 1))
	#define BC_NUM_NEG_CLR(n) ((n)->rdx &= ~((BcBigDig) 1))
	#define BC_NUM_NEG_CLR_NP(n) ((n).rdx &= ~((BcBigDig) 1))
	#define BC_NUM_NEG_SET(n) ((n)->rdx \|= ((BcBigDig) 1))
	#define BC_NUM_NEG_TGL(n) ((n)->rdx ^= ((BcBigDig) 1))
	#define BC_NUM_NEG_TGL_NP(n) ((n).rdx ^= ((BcBigDig) 1))
	#define BC_NUM_NEG_VAL(n, v) (((n)->rdx & ~((BcBigDig) 1)) \| (v))
	#define BC_NUM_NEG_VAL_NP(n, v) (((n).rdx & ~((BcBigDig) 1)) \| (v))

	#define BC_NUM_SIZE(n) ((n) * sizeof(BcDig))

	#if BC_DEBUG_CODE
	#define BC_NUM_PRINT(x) fprintf(stderr, "%s = %lu\n", #x, (unsigned long)(x))
	#define DUMP_NUM bc_num_dump
	#else // BC_DEBUG_CODE
	#undef DUMP_NUM
	#define DUMP_NUM(x,y)
	#define BC_NUM_PRINT(x)
	#endif // BC_DEBUG_CODE

	typedef void (BcNumBinaryOp)(BcNum, BcNum, BcNum, size_t);
	+typedef void (BcNumBinOp)(BcNum, BcNum, BcNum restrict, size_t);
	typedef size_t (BcNumBinaryOpReq)(const BcNum, const BcNum*, size_t);
	typedef void (*BcNumDigitOp)(size_t, size_t, bool);
	-typedef void (BcNumShiftAddOp)(BcDig, const BcDig*, size_t);
	+typedef void (BcNumShiftAddOp)(BcDig restrict, const BcDig* restrict, size_t);

	void bc_num_init(BcNum *restrict n, size_t req);
	void bc_num_setup(BcNum restrict n, BcDig restrict num, size_t cap);
	void bc_num_copy(BcNum d, const BcNum s);
	void bc_num_createCopy(BcNum d, const BcNum s);
	void bc_num_createFromBigdig(BcNum *n, BcBigDig val);
	void bc_num_clear(BcNum *restrict n);
	void bc_num_free(void *num);

	size_t bc_num_scale(const BcNum *restrict n);
	size_t bc_num_len(const BcNum *restrict n);

	void bc_num_bigdig(const BcNum restrict n, BcBigDig result);
	void bc_num_bigdig2(const BcNum restrict n, BcBigDig result);
	void bc_num_bigdig2num(BcNum *restrict n, BcBigDig val);

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	void bc_num_irand(const BcNum restrict a, BcNum restrict b,
	struct BcRNG *restrict rng);
	void bc_num_rng(const BcNum restrict n, struct BcRNG rng);
	void bc_num_createFromRNG(BcNum restrict n, struct BcRNG rng);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	void bc_num_add(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_sub(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_mul(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_div(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_mod(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_pow(BcNum a, BcNum b, BcNum *c, size_t scale);
	#if BC_ENABLE_EXTRA_MATH
	void bc_num_places(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_lshift(BcNum a, BcNum b, BcNum *c, size_t scale);
	void bc_num_rshift(BcNum a, BcNum b, BcNum *c, size_t scale);
	#endif // BC_ENABLE_EXTRA_MATH
	void bc_num_sqrt(BcNum restrict a, BcNum restrict b, size_t scale);
	void bc_num_sr(BcNum restrict a, BcNum restrict b, size_t scale);
	void bc_num_divmod(BcNum a, BcNum b, BcNum c, BcNum d, size_t scale);

	size_t bc_num_addReq(const BcNum* a, const BcNum* b, size_t scale);

	size_t bc_num_mulReq(const BcNum a, const BcNum b, size_t scale);
	size_t bc_num_divReq(const BcNum a, const BcNum b, size_t scale);
	size_t bc_num_powReq(const BcNum a, const BcNum b, size_t scale);
	#if BC_ENABLE_EXTRA_MATH
	size_t bc_num_placesReq(const BcNum a, const BcNum b, size_t scale);
	#endif // BC_ENABLE_EXTRA_MATH

	void bc_num_truncate(BcNum *restrict n, size_t places);
	void bc_num_extend(BcNum *restrict n, size_t places);
	void bc_num_shiftRight(BcNum *restrict n, size_t places);

	ssize_t bc_num_cmp(const BcNum a, const BcNum b);

	#if DC_ENABLED
	void bc_num_modexp(BcNum a, BcNum b, BcNum c, BcNum restrict d);
	#endif // DC_ENABLED

	void bc_num_zero(BcNum *restrict n);
	void bc_num_one(BcNum *restrict n);
	ssize_t bc_num_cmpZero(const BcNum *n);

	#if !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY
	bool bc_num_strValid(const char *restrict val);
	#endif // !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY
	void bc_num_parse(BcNum restrict n, const char restrict val, BcBigDig base);
	void bc_num_print(BcNum *restrict n, BcBigDig base, bool newline);
	#if DC_ENABLED
	void bc_num_stream(BcNum *restrict n, BcBigDig base);
	#endif // DC_ENABLED

	#if BC_DEBUG_CODE
	void bc_num_printDebug(const BcNum n, const char name, bool emptyline);
	void bc_num_printDigs(const BcDig* n, size_t len, bool emptyline);
	void bc_num_printWithDigs(const BcNum n, const char name, bool emptyline);
	void bc_num_dump(const char varname, const BcNum n);
	#endif // BC_DEBUG_CODE

	extern const char bc_num_hex_digits[];
	extern const BcBigDig bc_num_pow10[BC_BASE_DIGS + 1];

	extern const BcDig bc_num_bigdigMax[];
	extern const BcDig bc_num_bigdigMax2[];
	extern const size_t bc_num_bigdigMax_size;
	extern const size_t bc_num_bigdigMax2_size;

	#endif // BC_NUM_H
	diff --git a/contrib/bc/include/status.h b/contrib/bc/include/status.h
	index cf41a3ce4670..be2356497f94 100644
	--- a/contrib/bc/include/status.h
	+++ b/contrib/bc/include/status.h
	@@ -1,212 +1,153 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* All bc status codes.
	*
	*/

	#ifndef BC_STATUS_H
	#define BC_STATUS_H

	#include <stdint.h>

	#ifndef BC_ENABLED
	#define BC_ENABLED (1)
	#endif // BC_ENABLED

	#ifndef DC_ENABLED
	#define DC_ENABLED (1)
	#endif // DC_ENABLED

	#if BC_ENABLE_AFL
	#ifndef __AFL_HAVE_MANUAL_CONTROL
	#error Must compile with afl-clang-fast for fuzzing
	#endif // __AFL_HAVE_MANUAL_CONTROL
	#endif // BC_ENABLE_AFL

	#ifndef BC_ENABLE_MEMCHECK
	#define BC_ENABLE_MEMCHECK (0)
	#endif // BC_ENABLE_MEMCHECK

	#include <bcl.h>

	typedef enum BcStatus {

	BC_STATUS_SUCCESS = 0,
	BC_STATUS_ERROR_MATH,
	BC_STATUS_ERROR_PARSE,
	BC_STATUS_ERROR_EXEC,
	BC_STATUS_ERROR_FATAL,
	BC_STATUS_EOF,
	BC_STATUS_QUIT,

	} BcStatus;

	typedef enum BcErr {

	BC_ERR_MATH_NEGATIVE,
	BC_ERR_MATH_NON_INTEGER,
	BC_ERR_MATH_OVERFLOW,
	BC_ERR_MATH_DIVIDE_BY_ZERO,

	BC_ERR_FATAL_ALLOC_ERR,
	BC_ERR_FATAL_IO_ERR,
	BC_ERR_FATAL_FILE_ERR,
	BC_ERR_FATAL_BIN_FILE,
	BC_ERR_FATAL_PATH_DIR,
	BC_ERR_FATAL_OPTION,
	BC_ERR_FATAL_OPTION_NO_ARG,
	BC_ERR_FATAL_OPTION_ARG,

	BC_ERR_EXEC_IBASE,
	BC_ERR_EXEC_OBASE,
	BC_ERR_EXEC_SCALE,
	BC_ERR_EXEC_READ_EXPR,
	BC_ERR_EXEC_REC_READ,
	BC_ERR_EXEC_TYPE,

	BC_ERR_EXEC_STACK,

	BC_ERR_EXEC_PARAMS,
	BC_ERR_EXEC_UNDEF_FUNC,
	BC_ERR_EXEC_VOID_VAL,

	BC_ERR_PARSE_EOF,
	BC_ERR_PARSE_CHAR,
	BC_ERR_PARSE_STRING,
	BC_ERR_PARSE_COMMENT,
	BC_ERR_PARSE_TOKEN,
	#if BC_ENABLED
	BC_ERR_PARSE_EXPR,
	BC_ERR_PARSE_EMPTY_EXPR,
	BC_ERR_PARSE_PRINT,
	BC_ERR_PARSE_FUNC,
	BC_ERR_PARSE_ASSIGN,
	BC_ERR_PARSE_NO_AUTO,
	BC_ERR_PARSE_DUP_LOCAL,
	BC_ERR_PARSE_BLOCK,
	BC_ERR_PARSE_RET_VOID,
	BC_ERR_PARSE_REF_VAR,

	BC_ERR_POSIX_NAME_LEN,
	BC_ERR_POSIX_COMMENT,
	BC_ERR_POSIX_KW,
	BC_ERR_POSIX_DOT,
	BC_ERR_POSIX_RET,
	BC_ERR_POSIX_BOOL,
	BC_ERR_POSIX_REL_POS,
	BC_ERR_POSIX_MULTIREL,
	BC_ERR_POSIX_FOR,
	BC_ERR_POSIX_EXP_NUM,
	BC_ERR_POSIX_REF,
	BC_ERR_POSIX_VOID,
	BC_ERR_POSIX_BRACE,
	#endif // BC_ENABLED

	BC_ERR_NELEMS,

	#if BC_ENABLED
	BC_ERR_POSIX_START = BC_ERR_POSIX_NAME_LEN,
	BC_ERR_POSIX_END = BC_ERR_POSIX_BRACE,
	#endif // BC_ENABLED

	} BcErr;

	#define BC_ERR_IDX_MATH (0)
	#define BC_ERR_IDX_PARSE (1)
	#define BC_ERR_IDX_EXEC (2)
	#define BC_ERR_IDX_FATAL (3)
	#define BC_ERR_IDX_NELEMS (4)

	#if BC_ENABLED
	#define BC_ERR_IDX_WARN (BC_ERR_IDX_NELEMS)
	#endif // BC_ENABLED

	-#define BC_UNUSED(e) ((void) (e))
	-
	-#ifndef BC_LIKELY
	-#define BC_LIKELY(e) (e)
	-#endif // BC_LIKELY
	-
	-#ifndef BC_UNLIKELY
	-#define BC_UNLIKELY(e) (e)
	-#endif // BC_UNLIKELY
	-
	-#define BC_ERR(e) BC_UNLIKELY(e)
	-#define BC_NO_ERR(s) BC_LIKELY(s)
	-
	-#ifndef BC_DEBUG_CODE
	-#define BC_DEBUG_CODE (0)
	-#endif // BC_DEBUG_CODE
	-
	-#if __STDC_VERSION__ >= 201100L
	-#include <stdnoreturn.h>
	-#define BC_NORETURN _Noreturn
	-#else // __STDC_VERSION__
	-#define BC_NORETURN
	-#define BC_MUST_RETURN
	-#endif // __STDC_VERSION__
	-
	-#if defined(__clang__) \|\| defined(__GNUC__)
	-#if defined(__has_attribute)
	-#if __has_attribute(fallthrough)
	-#define BC_FALLTHROUGH __attribute__((fallthrough));
	-#else // __has_attribute(fallthrough)
	-#define BC_FALLTHROUGH
	-#endif // __has_attribute(fallthrough)
	-#else // defined(__has_attribute)
	-#define BC_FALLTHROUGH
	-#endif // defined(__has_attribute)
	-#else // defined(__clang__) \|\| defined(__GNUC__)
	-#define BC_FALLTHROUGH
	-#endif // defined(__clang__) \|\| defined(__GNUC__)
	-
	-// Workarounds for AIX's POSIX incompatibility.
	-#ifndef SIZE_MAX
	-#define SIZE_MAX __SIZE_MAX__
	-#endif // SIZE_MAX
	-#ifndef UINTMAX_C
	-#define UINTMAX_C __UINTMAX_C
	-#endif // UINTMAX_C
	-#ifndef UINT32_C
	-#define UINT32_C __UINT32_C
	-#endif // UINT32_C
	-#ifndef UINT_FAST32_MAX
	-#define UINT_FAST32_MAX __UINT_FAST32_MAX__
	-#endif // UINT_FAST32_MAX
	-#ifndef UINT16_MAX
	-#define UINT16_MAX __UINT16_MAX__
	-#endif // UINT16_MAX
	-#ifndef SIG_ATOMIC_MAX
	-#define SIG_ATOMIC_MAX __SIG_ATOMIC_MAX__
	-#endif // SIG_ATOMIC_MAX
	-
	#endif // BC_STATUS_H
	diff --git a/contrib/bc/include/file.h b/contrib/bc/include/version.h
	similarity index 67%
	copy from contrib/bc/include/file.h
	copy to contrib/bc/include/version.h
	index 1c3273b7a756..7f33df62312e 100644
	--- a/contrib/bc/include/file.h
	+++ b/contrib/bc/include/version.h
	@@ -1,65 +1,41 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	- * Definitions for implementing buffered I/O on my own terms.
	+ * Definitions for processing command-line arguments.
	*
	*/

	-#ifndef BC_FILE_H
	-#define BC_FILE_H
	+#ifndef BC_VERSION_H
	+#define BC_VERSION_H

	-#include <stdarg.h>
	+#define VERSION 4.0.0

	-#include <vector.h>
	-
	-#define BC_FILE_ULL_LENGTH (21)
	-
	-typedef struct BcFile {
	-
	- int fd;
	- char *buf;
	- size_t len;
	- size_t cap;
	-
	-} BcFile;
	-
	-void bc_file_init(BcFile f, int fd, char buf, size_t cap);
	-void bc_file_free(BcFile *f);
	-
	-void bc_file_putchar(BcFile *restrict f, uchar c);
	-BcStatus bc_file_flushErr(BcFile *restrict f);
	-void bc_file_flush(BcFile *restrict f);
	-void bc_file_write(BcFile restrict f, const char buf, size_t n);
	-void bc_file_printf(BcFile restrict f, const char fmt, ...);
	-void bc_file_vprintf(BcFile restrict f, const char fmt, va_list args);
	-void bc_file_puts(BcFile restrict f, const char str);
	-
	-#endif // BC_FILE_H
	+#endif // BC_VERSION_H
	diff --git a/contrib/bc/include/vm.h b/contrib/bc/include/vm.h
	index 80a060edd42f..8d726ffec1cc 100644
	--- a/contrib/bc/include/vm.h
	+++ b/contrib/bc/include/vm.h
	@@ -1,461 +1,475 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Definitions for bc's VM.
	*
	*/

	#ifndef BC_VM_H
	#define BC_VM_H

	#include <assert.h>
	#include <stddef.h>
	#include <limits.h>

	#include <signal.h>

	#if BC_ENABLE_NLS

	# ifdef _WIN32
	# error NLS is not supported on Windows.
	# endif // _WIN32

	#include <nl_types.h>

	#endif // BC_ENABLE_NLS

	+#include <version.h>
	#include <status.h>
	#include <num.h>
	#include <parse.h>
	#include <program.h>
	#include <history.h>

	#if !BC_ENABLE_LIBRARY
	#include <file.h>
	#endif // !BC_ENABLE_LIBRARY

	#if !BC_ENABLED && !DC_ENABLED
	#error Must define BC_ENABLED, DC_ENABLED, or both
	#endif

	// CHAR_BIT must be at least 6.
	#if CHAR_BIT < 6
	#error CHAR_BIT must be at least 6.
	#endif

	#ifndef BC_ENABLE_NLS
	#define BC_ENABLE_NLS (0)
	#endif // BC_ENABLE_NLS

	#ifndef MAINEXEC
	#define MAINEXEC bc
	-#endif
	+#endif // MAINEXEC

	+#ifndef _WIN32
	#ifndef EXECPREFIX
	#define EXECPREFIX
	-#endif
	+#endif // EXECPREFIX
	+#else // _WIN32
	+#undef EXECPREFIX
	+#endif // _WIN32

	#define GEN_STR(V) #V
	#define GEN_STR2(V) GEN_STR(V)

	#define BC_VERSION GEN_STR2(VERSION)
	-#define BC_EXECPREFIX GEN_STR2(EXECPREFIX)
	#define BC_MAINEXEC GEN_STR2(MAINEXEC)
	+#define BC_BUILD_TYPE GEN_STR2(BUILD_TYPE)

	-// Windows has deprecated isatty().
	-#ifdef _WIN32
	-#define isatty _isatty
	+#ifndef _WIN32
	+#define BC_EXECPREFIX GEN_STR2(EXECPREFIX)
	+#else // _WIN32
	+#define BC_EXECPREFIX ""
	#endif // _WIN32

	#if !BC_ENABLE_LIBRARY

	#if DC_ENABLED
	#define DC_FLAG_X (UINTMAX_C(1)<<0)
	#endif // DC_ENABLED

	#if BC_ENABLED
	#define BC_FLAG_W (UINTMAX_C(1)<<1)
	#define BC_FLAG_S (UINTMAX_C(1)<<2)
	#define BC_FLAG_L (UINTMAX_C(1)<<3)
	#define BC_FLAG_G (UINTMAX_C(1)<<4)
	#endif // BC_ENABLED

	#define BC_FLAG_I (UINTMAX_C(1)<<5)
	#define BC_FLAG_P (UINTMAX_C(1)<<6)
	-#define BC_FLAG_TTYIN (UINTMAX_C(1)<<7)
	-#define BC_FLAG_TTY (UINTMAX_C(1)<<8)
	+#define BC_FLAG_R (UINTMAX_C(1)<<7)
	+#define BC_FLAG_TTYIN (UINTMAX_C(1)<<8)
	+#define BC_FLAG_TTY (UINTMAX_C(1)<<9)
	#define BC_TTYIN (vm.flags & BC_FLAG_TTYIN)
	#define BC_TTY (vm.flags & BC_FLAG_TTY)

	#if BC_ENABLED

	#define BC_S (vm.flags & BC_FLAG_S)
	#define BC_W (vm.flags & BC_FLAG_W)
	#define BC_L (vm.flags & BC_FLAG_L)
	#define BC_G (vm.flags & BC_FLAG_G)

	#endif // BC_ENABLED

	#if DC_ENABLED
	#define DC_X (vm.flags & DC_FLAG_X)
	#endif // DC_ENABLED

	#define BC_I (vm.flags & BC_FLAG_I)
	#define BC_P (vm.flags & BC_FLAG_P)
	+#define BC_R (vm.flags & BC_FLAG_R)

	#if BC_ENABLED

	#define BC_IS_POSIX (BC_S \|\| BC_W)

	#if DC_ENABLED
	#define BC_IS_BC (vm.name[0] != 'd')
	#define BC_IS_DC (vm.name[0] == 'd')
	#else // DC_ENABLED
	#define BC_IS_BC (1)
	#define BC_IS_DC (0)
	#endif // DC_ENABLED

	#else // BC_ENABLED
	#define BC_IS_POSIX (0)
	#define BC_IS_BC (0)
	#define BC_IS_DC (1)
	#endif // BC_ENABLED

	#if BC_ENABLED
	#define BC_USE_PROMPT (!BC_P && BC_TTY && !BC_IS_POSIX)
	#else // BC_ENABLED
	#define BC_USE_PROMPT (!BC_P && BC_TTY)
	#endif // BC_ENABLED

	#endif // !BC_ENABLE_LIBRARY

	#define BC_MAX(a, b) ((a) > (b) ? (a) : (b))
	#define BC_MIN(a, b) ((a) < (b) ? (a) : (b))

	#define BC_MAX_OBASE ((BcBigDig) (BC_BASE_POW))
	#define BC_MAX_DIM ((BcBigDig) (SIZE_MAX - 1))
	#define BC_MAX_SCALE ((BcBigDig) (BC_NUM_BIGDIG_MAX - 1))
	#define BC_MAX_STRING ((BcBigDig) (BC_NUM_BIGDIG_MAX - 1))
	#define BC_MAX_NAME BC_MAX_STRING
	#define BC_MAX_NUM BC_MAX_SCALE

	#if BC_ENABLE_EXTRA_MATH
	#define BC_MAX_RAND ((BcBigDig) (((BcRand) 0) - 1))
	#endif // BC_ENABLE_EXTRA_MATH

	#define BC_MAX_EXP ((ulong) (BC_NUM_BIGDIG_MAX))
	#define BC_MAX_VARS ((ulong) (SIZE_MAX - 1))

	#if BC_DEBUG_CODE
	#define BC_VM_JMP bc_vm_jmp(__func__)
	#else // BC_DEBUG_CODE
	#define BC_VM_JMP bc_vm_jmp()
	#endif // BC_DEBUG_CODE

	#define BC_SIG_EXC \
	BC_UNLIKELY(vm.status != (sig_atomic_t) BC_STATUS_SUCCESS \|\| vm.sig)
	#define BC_NO_SIG_EXC \
	BC_LIKELY(vm.status == (sig_atomic_t) BC_STATUS_SUCCESS && !vm.sig)

	#ifndef NDEBUG
	#define BC_SIG_ASSERT_LOCKED do { assert(vm.sig_lock); } while (0)
	#define BC_SIG_ASSERT_NOT_LOCKED do { assert(vm.sig_lock == 0); } while (0)
	#else // NDEBUG
	#define BC_SIG_ASSERT_LOCKED
	#define BC_SIG_ASSERT_NOT_LOCKED
	#endif // NDEBUG

	#define BC_SIG_LOCK \
	do { \
	BC_SIG_ASSERT_NOT_LOCKED; \
	vm.sig_lock = 1; \
	} while (0)

	#define BC_SIG_UNLOCK \
	do { \
	BC_SIG_ASSERT_LOCKED; \
	vm.sig_lock = 0; \
	if (BC_SIG_EXC) BC_VM_JMP; \
	} while (0)

	#define BC_SIG_MAYLOCK \
	do { \
	vm.sig_lock = 1; \
	} while (0)

	#define BC_SIG_MAYUNLOCK \
	do { \
	vm.sig_lock = 0; \
	if (BC_SIG_EXC) BC_VM_JMP; \
	} while (0)

	#define BC_SIG_TRYLOCK(v) \
	do { \
	v = vm.sig_lock; \
	vm.sig_lock = 1; \
	} while (0)

	#define BC_SIG_TRYUNLOCK(v) \
	do { \
	vm.sig_lock = (v); \
	if (!(v) && BC_SIG_EXC) BC_VM_JMP; \
	} while (0)

	#define BC_SETJMP(l) \
	do { \
	sigjmp_buf sjb; \
	BC_SIG_LOCK; \
	if (sigsetjmp(sjb, 0)) { \
	assert(BC_SIG_EXC); \
	goto l; \
	} \
	bc_vec_push(&vm.jmp_bufs, &sjb); \
	BC_SIG_UNLOCK; \
	} while (0)

	#define BC_SETJMP_LOCKED(l) \
	do { \
	sigjmp_buf sjb; \
	BC_SIG_ASSERT_LOCKED; \
	if (sigsetjmp(sjb, 0)) { \
	assert(BC_SIG_EXC); \
	goto l; \
	} \
	bc_vec_push(&vm.jmp_bufs, &sjb); \
	} while (0)

	#define BC_LONGJMP_CONT \
	do { \
	BC_SIG_ASSERT_LOCKED; \
	if (!vm.sig_pop) bc_vec_pop(&vm.jmp_bufs); \
	BC_SIG_UNLOCK; \
	} while (0)

	#define BC_UNSETJMP \
	do { \
	BC_SIG_ASSERT_LOCKED; \
	bc_vec_pop(&vm.jmp_bufs); \
	} while (0)

	#define BC_LONGJMP_STOP \
	do { \
	vm.sig_pop = 0; \
	vm.sig = 0; \
	} while (0)

	#define BC_VM_BUF_SIZE (1<<12)
	#define BC_VM_STDOUT_BUF_SIZE (1<<11)
	#define BC_VM_STDERR_BUF_SIZE (1<<10)
	#define BC_VM_STDIN_BUF_SIZE (BC_VM_STDERR_BUF_SIZE - 1)

	#define BC_VM_SAFE_RESULT(r) ((r)->t >= BC_RESULT_TEMP)

	#if BC_ENABLE_LIBRARY
	#define bc_vm_error(e, l, ...) (bc_vm_handleError((e)))
	#define bc_vm_err(e) (bc_vm_handleError((e)))
	#define bc_vm_verr(e, ...) (bc_vm_handleError((e)))
	#else // BC_ENABLE_LIBRARY
	#define bc_vm_error(e, l, ...) (bc_vm_handleError((e), (l), __VA_ARGS__))
	#define bc_vm_err(e) (bc_vm_handleError((e), 0))
	#define bc_vm_verr(e, ...) (bc_vm_handleError((e), 0, __VA_ARGS__))
	#endif // BC_ENABLE_LIBRARY

	#define BC_STATUS_IS_ERROR(s) \
	((s) >= BC_STATUS_ERROR_MATH && (s) <= BC_STATUS_ERROR_FATAL)

	#define BC_VM_INVALID_CATALOG ((nl_catd) -1)

	#if BC_DEBUG_CODE
	#define BC_VM_FUNC_ENTER \
	do { \
	bc_file_printf(&vm.ferr, "Entering %s\n", __func__); \
	bc_file_flush(&vm.ferr); \
	} while (0);

	#define BC_VM_FUNC_EXIT \
	do { \
	bc_file_printf(&vm.ferr, "Leaving %s\n", __func__); \
	bc_file_flush(&vm.ferr); \
	} while (0);
	#else // BC_DEBUG_CODE
	#define BC_VM_FUNC_ENTER
	#define BC_VM_FUNC_EXIT
	#endif // BC_DEBUG_CODE

	typedef struct BcVm {

	volatile sig_atomic_t status;
	volatile sig_atomic_t sig_pop;

	#if !BC_ENABLE_LIBRARY
	BcParse prs;
	BcProgram prog;
	#endif // !BC_ENABLE_LIBRARY

	BcVec jmp_bufs;

	BcVec temps;

	#if BC_ENABLE_LIBRARY

	BcVec ctxts;
	BcVec out;

	BcRNG rng;

	BclError err;
	bool abrt;

	unsigned int refs;

	volatile sig_atomic_t running;
	#endif // BC_ENABLE_LIBRARY

	#if !BC_ENABLE_LIBRARY
	const char* file;

	const char *sigmsg;
	#endif // !BC_ENABLE_LIBRARY
	volatile sig_atomic_t sig_lock;
	volatile sig_atomic_t sig;
	#if !BC_ENABLE_LIBRARY
	uchar siglen;

	uchar read_ret;
	uint16_t flags;

	uint16_t nchars;
	uint16_t line_len;

	bool no_exit_exprs;
	bool exit_exprs;
	bool eof;
	#endif // !BC_ENABLE_LIBRARY

	BcBigDig maxes[BC_PROG_GLOBALS_LEN + BC_ENABLE_EXTRA_MATH];

	#if !BC_ENABLE_LIBRARY
	BcVec files;
	BcVec exprs;

	const char *name;
	const char *help;

	#if BC_ENABLE_HISTORY
	BcHistory history;
	#endif // BC_ENABLE_HISTORY

	BcLexNext next;
	BcParseParse parse;
	BcParseExpr expr;

	const char *func_header;

	const char *err_ids[BC_ERR_IDX_NELEMS + BC_ENABLED];
	const char *err_msgs[BC_ERR_NELEMS];

	const char *locale;
	#endif // !BC_ENABLE_LIBRARY

	BcBigDig last_base;
	BcBigDig last_pow;
	BcBigDig last_exp;
	BcBigDig last_rem;

	#if !BC_ENABLE_LIBRARY
	char *env_args_buffer;
	BcVec env_args;
	#endif // !BC_ENABLE_LIBRARY

	BcNum max;
	BcNum max2;
	BcDig max_num[BC_NUM_BIGDIG_LOG10];
	BcDig max2_num[BC_NUM_BIGDIG_LOG10];

	#if !BC_ENABLE_LIBRARY
	BcFile fout;
	BcFile ferr;

	#if BC_ENABLE_NLS
	nl_catd catalog;
	#endif // BC_ENABLE_NLS

	char *buf;
	size_t buf_len;
	#endif // !BC_ENABLE_LIBRARY

	} BcVm;

	void bc_vm_info(const char* const help);
	void bc_vm_boot(int argc, char argv[], const char env_len,
	const char* const env_args);
	void bc_vm_init(void);
	void bc_vm_shutdown(void);
	void bc_vm_freeTemps(void);

	+#if !BC_ENABLE_HISTORY
	+#define bc_vm_putchar(c, t) bc_vm_putchar(c)
	+#endif // !BC_ENABLE_HISTORY
	+
	void bc_vm_printf(const char *fmt, ...);
	-void bc_vm_putchar(int c);
	+void bc_vm_putchar(int c, BcFlushType type);
	size_t bc_vm_arraySize(size_t n, size_t size);
	size_t bc_vm_growSize(size_t a, size_t b);
	void* bc_vm_malloc(size_t n);
	void* bc_vm_realloc(void *ptr, size_t n);
	char* bc_vm_strdup(const char *str);
	+char* bc_vm_getenv(const char* var);
	+void bc_vm_getenvFree(char* var);

	#if BC_DEBUG_CODE
	void bc_vm_jmp(const char *f);
	#else // BC_DEBUG_CODE
	void bc_vm_jmp(void);
	#endif // BC_DEBUG_CODE

	#if BC_ENABLE_LIBRARY
	void bc_vm_handleError(BcErr e);
	void bc_vm_fatalError(BcErr e);
	void bc_vm_atexit(void);
	#else // BC_ENABLE_LIBRARY
	void bc_vm_handleError(BcErr e, size_t line, ...);
	#if !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	BC_NORETURN
	#endif // !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	void bc_vm_fatalError(BcErr e);
	int bc_vm_atexit(int status);
	#endif // BC_ENABLE_LIBRARY

	extern const char bc_copyright[];
	extern const char* const bc_err_line;
	extern const char* const bc_err_func_header;
	extern const char *bc_errs[];
	extern const uchar bc_err_ids[];
	extern const char* const bc_err_msgs[];

	extern BcVm vm;
	extern char output_bufs[BC_VM_BUF_SIZE];

	#endif // BC_VM_H
	diff --git a/contrib/bc/karatsuba.py b/contrib/bc/karatsuba.py
	index cfab4c4f4fbf..0a63cd58b08b 100755
	--- a/contrib/bc/karatsuba.py
	+++ b/contrib/bc/karatsuba.py
	@@ -1,232 +1,232 @@
	#! /usr/bin/python3 -B
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#

	import os
	import sys
	import subprocess
	import time

	def usage():
	print("usage: {} [num_iterations test_num exe]".format(script))
	print("\n num_iterations is the number of times to run each karatsuba number; default is 4")
	print("\n test_num is the last Karatsuba number to run through tests")
	sys.exit(1)

	def run(cmd, env=None):
	return subprocess.run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE, env=env)

	script = sys.argv[0]
	testdir = os.path.dirname(script)

	if testdir == "":
	testdir = os.getcwd()

	print("\nWARNING: This script is for distro and package maintainers.")
	print("It is for finding the optimal Karatsuba number.")
	print("Though it only needs to be run once per release/platform,")
	print("it takes forever to run.")
	print("You have been warned.\n")
	print("Note: If you send an interrupt, it will report the current best number.\n")

	if __name__ != "__main__":
	usage()

	mx = 520
	mx2 = mx // 2
	mn = 16

	num = "9" * mx

	args_idx = 4

	if len(sys.argv) >= 2:
	num_iterations = int(sys.argv[1])
	else:
	num_iterations = 4

	if len(sys.argv) >= 3:
	test_num = int(sys.argv[2])
	else:
	test_num = 0

	if len(sys.argv) >= args_idx:
	exe = sys.argv[3]
	else:
	exe = testdir + "/bin/bc"

	exedir = os.path.dirname(exe)

	indata = "for (i = 0; i < 100; ++i) {} * {}\n"
	indata += "1.23456789^100000\n1.23456789^100000\nhalt"
	indata = indata.format(num, num).encode()

	times = []
	nums = []
	runs = []
	nruns = num_iterations + 1

	for i in range(0, nruns):
	runs.append(0)

	tests = [ "multiply", "modulus", "power", "sqrt" ]
	scripts = [ "multiply" ]

	print("Testing CFLAGS=\"-flto\"...")

	flags = dict(os.environ)
	try:
	flags["CFLAGS"] = flags["CFLAGS"] + " " + "-flto"
	except KeyError:
	flags["CFLAGS"] = "-flto"

	p = run([ "./configure.sh", "-O3" ], flags)
	if p.returncode != 0:
	print("configure.sh returned an error ({}); exiting...".format(p.returncode))
	sys.exit(p.returncode)

	p = run([ "make" ])

	if p.returncode == 0:
	config_env = flags
	print("Using CFLAGS=\"-flto\"")
	else:
	config_env = os.environ
	print("Not using CFLAGS=\"-flto\"")

	p = run([ "make", "clean" ])

	-print("Testing \"make -j12\"")
	+print("Testing \"make -j16\"")

	if p.returncode != 0:
	print("make returned an error ({}); exiting...".format(p.returncode))
	sys.exit(p.returncode)

	-p = run([ "make", "-j12" ])
	+p = run([ "make", "-j16" ])

	if p.returncode == 0:
	- makecmd = [ "make", "-j12" ]
	- print("Using \"make -j12\"")
	+ makecmd = [ "make", "-j16" ]
	+ print("Using \"make -j16\"")
	else:
	makecmd = [ "make" ]
	- print("Not using \"make -j12\"")
	+ print("Not using \"make -j16\"")

	if test_num != 0:
	mx2 = test_num

	try:

	for i in range(mn, mx2 + 1):

	print("\nCompiling...\n")

	p = run([ "./configure.sh", "-O3", "-k{}".format(i) ], config_env)

	if p.returncode != 0:
	print("configure.sh returned an error ({}); exiting...".format(p.returncode))
	sys.exit(p.returncode)

	p = run(makecmd)

	if p.returncode != 0:
	print("make returned an error ({}); exiting...".format(p.returncode))
	sys.exit(p.returncode)

	if (test_num >= i):

	print("Running tests for Karatsuba Num: {}\n".format(i))

	for test in tests:

	cmd = [ "{}/tests/test.sh".format(testdir), "bc", test, "0", "0", exe ]

	p = subprocess.run(cmd + sys.argv[args_idx:], stderr=subprocess.PIPE)

	if p.returncode != 0:
	print("{} test failed:\n".format(test, p.returncode))
	print(p.stderr.decode())
	print("\nexiting...")
	sys.exit(p.returncode)

	print("")

	for script in scripts:

	cmd = [ "{}/tests/script.sh".format(testdir), "bc", script + ".bc",
	"0", "1", "1", "0", exe ]

	p = subprocess.run(cmd + sys.argv[args_idx:], stderr=subprocess.PIPE)

	if p.returncode != 0:
	print("{} test failed:\n".format(test, p.returncode))
	print(p.stderr.decode())
	print("\nexiting...")
	sys.exit(p.returncode)

	print("")

	elif test_num == 0:

	print("Timing Karatsuba Num: {}".format(i), end='', flush=True)

	for j in range(0, nruns):

	cmd = [ exe, "{}/tests/bc/power.txt".format(testdir) ]

	start = time.perf_counter()
	p = subprocess.run(cmd, input=indata, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
	end = time.perf_counter()

	if p.returncode != 0:
	print("bc returned an error; exiting...")
	sys.exit(p.returncode)

	runs[j] = end - start

	run_times = runs[1:]
	avg = sum(run_times) / len(run_times)

	times.append(avg)
	nums.append(i)
	print(", Time: {}".format(times[i - mn]))

	except KeyboardInterrupt:
	nums = nums[0:i]
	times = times[0:i]

	if test_num == 0:

	opt = nums[times.index(min(times))]

	print("\n\nOptimal Karatsuba Num (for this machine): {}".format(opt))
	print("Run the following:\n")
	if "-flto" in config_env["CFLAGS"]:
	print("CFLAGS=\"-flto\" ./configure.sh -O3 -k {}".format(opt))
	else:
	print("./configure.sh -O3 -k {}".format(opt))
	print("make")
	diff --git a/contrib/bc/manpage.sh b/contrib/bc/manpage.sh
	index f774bfdb3b20..b855b3092969 100755
	--- a/contrib/bc/manpage.sh
	+++ b/contrib/bc/manpage.sh
	@@ -1,131 +1,131 @@
	#! /bin/sh
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#

	usage() {
	printf "usage: %s manpage\n" "$0" 1>&2
	exit 1
	}

	print_manpage() {

	_print_manpage_md="$1"
	shift

	_print_manpage_out="$1"
	shift

	cat "$manualsdir/header.txt" > "$_print_manpage_out"
	cat "$manualsdir/header_${manpage}.txt" >> "$_print_manpage_out"

	- pandoc -f markdown -t man "$_print_manpage_md" >> "$_print_manpage_out"
	+ pandoc -f commonmark -t man "$_print_manpage_md" >> "$_print_manpage_out"

	}

	gen_manpage() {

	_gen_manpage_args="$1"
	shift

	_gen_manpage_status="$ALL"
	_gen_manpage_out="$manualsdir/$manpage/$_gen_manpage_args.1"
	_gen_manpage_md="$manualsdir/$manpage/$_gen_manpage_args.1.md"
	_gen_manpage_temp="$manualsdir/temp.1.md"
	_gen_manpage_ifs="$IFS"

	rm -rf "$_gen_manpage_out" "$_gen_manpage_md"

	while IFS= read -r line; do

	if [ "$line" = "{{ end }}" ]; then

	if [ "$_gen_manpage_status" -eq "$ALL" ]; then
	err_exit "{{ end }} tag without corresponding start tag" 2
	fi

	_gen_manpage_status="$ALL"

	elif [ "${line#\{\{* $_gen_manpage_args *\}\}}" != "$line" ]; then

	if [ "$_gen_manpage_status" -ne "$ALL" ]; then
	err_exit "start tag nested in start tag" 3
	fi

	_gen_manpage_status="$NOSKIP"

	elif [ "${line#\{\{*\}\}}" != "$line" ]; then

	if [ "$_gen_manpage_status" -ne "$ALL" ]; then
	err_exit "start tag nested in start tag" 3
	fi

	_gen_manpage_status="$SKIP"

	else
	if [ "$_gen_manpage_status" -ne "$SKIP" ]; then
	printf '%s\n' "$line" >> "$_gen_manpage_temp"
	fi
	fi

	done < "$manualsdir/${manpage}.1.md.in"

	uniq "$_gen_manpage_temp" "$_gen_manpage_md"
	rm -rf "$_gen_manpage_temp"

	IFS="$_gen_manpage_ifs"

	print_manpage "$_gen_manpage_md" "$_gen_manpage_out"
	}

	set -e

	script="$0"
	scriptdir=$(dirname "$script")
	manualsdir="$scriptdir/manuals"

	. "$scriptdir/functions.sh"

	ARGS="A E H N P EH EN EP HN HP NP EHN EHP ENP HNP EHNP"
	ALL=0
	NOSKIP=1
	SKIP=2

	test "$#" -eq 1 \|\| usage

	manpage="$1"
	shift

	if [ "$manpage" != "bcl" ]; then

	for a in $ARGS; do
	gen_manpage "$a"
	done

	else
	print_manpage "$manualsdir/${manpage}.3.md" "$manualsdir/${manpage}.3"
	fi
	diff --git a/contrib/bc/manuals/bc.1.md.in b/contrib/bc/manuals/bc.1.md.in
	index 661fcdd45ae4..d182dd7ab411 100644
	--- a/contrib/bc/manuals/bc.1.md.in
	+++ b/contrib/bc/manuals/bc.1.md.in
	@@ -1,1821 +1,1840 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	{{ A N P NP }}
	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1). It also has many extensions and extra features beyond
	other implementations.
	{{ end }}
	{{ E EN EP ENP }}
	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1).
	{{ end }}

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	{{ A H N P HN HP NP HNP }}
	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	{{ end }}
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	{{ A H N P HN HP NP HNP }}
	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.
	{{ end }}

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	{{ A H N P HN HP NP HNP }}
	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.
	{{ end }}

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	{{ A H N P HN HP NP HNP }}
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.
	{{ end }}

	-P, -\-no-prompt

	{{ A E H N EH EN HN EHN }}
	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).
	{{ end }}
	{{ P EP HP NP EHP ENP HNP EHNP }}
	: This option is a no-op.
	{{ end }}

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+{{ A E H N EH EN HN EHN }}
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+{{ end }}
	+{{ P EP HP NP EHP ENP HNP EHNP }}
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+{{ end }}
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	{{ A H N P HN HP NP HNP }}
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	min allowable value for obase is 2. Values are output in the specified
	base.
	{{ end }}

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	{{ A H N P HN HP NP HNP }}
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	6. last or a single dot (.)

	Number 6 is a non-portable extension.
	{{ end }}

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	{{ A H N P HN HP NP HNP }}
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.
	{{ end }}

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	{{ A H N P HN HP NP HNP }}
	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.
	{{ end }}

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	{{ A H N P HN HP NP HNP }}
	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision
	{{ end }}

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	{{ A H N P HN HP NP HNP }}
	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	= += -= *\= /= %= \^=**
	{{ end }}

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	{{ A H N P HN HP NP HNP }}
	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.
	{{ end }}

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	{{ A H N P HN HP NP HNP }}
	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.
	{{ end }}

	{{ A H N P HN HP NP HNP }}
	= \<\<= \>\>= += -= *\= /= %= \^= \@=**
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	= += -= *\= /= %= \^=**
	{{ end }}

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	{{ A H N P HN HP NP HNP }}
	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.
	{{ end }}

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	{{ A H N P HN HP NP HNP }}
	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.
	{{ end }}

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	{{ A H N P HN HP NP HNP }}
	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.
	{{ end }}

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	{{ A H N P HN HP NP HNP }}
	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).
	{{ end }}

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	{{ A H N P HN HP NP HNP }}
	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)
	{{ end }}

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	{{ A H N P HN HP NP HNP }}
	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.
	{{ end }}

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	{{ A H N P HN HP NP HNP }}
	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.
	{{ end }}

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	{{ A E N P EN EP NP ENP }}
	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.
	{{ end }}

	{{ A E H N EH EN HN EHN }}
	The prompt is enabled in TTY mode.
	{{ end }}

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	{{ A E N P EN EP NP ENP }}
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.
	{{ end }}
	{{ H EH HN HP EHN EHP HNP EHNP }}
	default handler for all other signals.
	{{ end }}

	{{ A E N P EN EP NP ENP }}
	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.
	{{ end }}

	{{ A E H P EH EP HP EHP }}
	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.
	{{ end }}

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	{{ A E H P EH EP HP EHP }}
	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.
	{{ end }}

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/A.1 b/contrib/bc/manuals/bc/A.1
	index b38d8d35e71b..2cb0a11943cc 100644
	--- a/contrib/bc/manuals/bc/A.1
	+++ b/contrib/bc/manuals/bc/A.1
	@@ -1,2057 +1,2266 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	It also has many extensions and extra features beyond other
	implementations.
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: 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
	+do not want a prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\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
	-do not want a prompt or are not used to having them in bc(1).
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	.PP
	-Any other character following a backslash causes the backslash and
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	+.PP
	+Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/A.1.md b/contrib/bc/manuals/bc/A.1.md
	index 04f37c6bb724..847d7c312310 100644
	--- a/contrib/bc/manuals/bc/A.1.md
	+++ b/contrib/bc/manuals/bc/A.1.md
	@@ -1,1704 +1,1718 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1). It also has many extensions and extra features beyond
	other implementations.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/E.1 b/contrib/bc/manuals/bc/E.1
	index 9023b07c6b87..6600e9da5eaa 100644
	--- a/contrib/bc/manuals/bc/E.1
	+++ b/contrib/bc/manuals/bc/E.1
	@@ -1,1313 +1,1416 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/E.1.md b/contrib/bc/manuals/bc/E.1.md
	index 589050cb89b5..478f298eeeb2 100644
	--- a/contrib/bc/manuals/bc/E.1.md
	+++ b/contrib/bc/manuals/bc/E.1.md
	@@ -1,1093 +1,1107 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1).

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EH.1 b/contrib/bc/manuals/bc/EH.1
	index 53f95b2f7c09..696e25c5a657 100644
	--- a/contrib/bc/manuals/bc/EH.1
	+++ b/contrib/bc/manuals/bc/EH.1
	@@ -1,1295 +1,1398 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EH.1.md b/contrib/bc/manuals/bc/EH.1.md
	index bfd08efb3830..51a9f93549fa 100644
	--- a/contrib/bc/manuals/bc/EH.1.md
	+++ b/contrib/bc/manuals/bc/EH.1.md
	@@ -1,1077 +1,1091 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EHN.1 b/contrib/bc/manuals/bc/EHN.1
	index 0870115dca2a..bbfeb207b35c 100644
	--- a/contrib/bc/manuals/bc/EHN.1
	+++ b/contrib/bc/manuals/bc/EHN.1
	@@ -1,1288 +1,1391 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EHN.1.md b/contrib/bc/manuals/bc/EHN.1.md
	index 15b851ee19b0..aab79e932b04 100644
	--- a/contrib/bc/manuals/bc/EHN.1.md
	+++ b/contrib/bc/manuals/bc/EHN.1.md
	@@ -1,1069 +1,1083 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EHNP.1 b/contrib/bc/manuals/bc/EHNP.1
	index f6728d5b2221..ade3294dd49a 100644
	--- a/contrib/bc/manuals/bc/EHNP.1
	+++ b/contrib/bc/manuals/bc/EHNP.1
	@@ -1,1281 +1,1375 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EHNP.1.md b/contrib/bc/manuals/bc/EHNP.1.md
	index a0e1b71f8d38..d7afa1ccc1af 100644
	--- a/contrib/bc/manuals/bc/EHNP.1.md
	+++ b/contrib/bc/manuals/bc/EHNP.1.md
	@@ -1,1063 +1,1069 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EHP.1 b/contrib/bc/manuals/bc/EHP.1
	index dc3476f68b92..b5cfe948d5e8 100644
	--- a/contrib/bc/manuals/bc/EHP.1
	+++ b/contrib/bc/manuals/bc/EHP.1
	@@ -1,1288 +1,1382 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EHP.1.md b/contrib/bc/manuals/bc/EHP.1.md
	index 976ae8eb11b7..e6338f70e396 100644
	--- a/contrib/bc/manuals/bc/EHP.1.md
	+++ b/contrib/bc/manuals/bc/EHP.1.md
	@@ -1,1071 +1,1077 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EN.1 b/contrib/bc/manuals/bc/EN.1
	index e6e7b3c5f145..3ea500b95b3f 100644
	--- a/contrib/bc/manuals/bc/EN.1
	+++ b/contrib/bc/manuals/bc/EN.1
	@@ -1,1306 +1,1409 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EN.1.md b/contrib/bc/manuals/bc/EN.1.md
	index 6dc19727c982..4e0a0f0fb8b4 100644
	--- a/contrib/bc/manuals/bc/EN.1.md
	+++ b/contrib/bc/manuals/bc/EN.1.md
	@@ -1,1085 +1,1099 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1).

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/ENP.1 b/contrib/bc/manuals/bc/ENP.1
	index f96fe194cda1..e4452bd876f5 100644
	--- a/contrib/bc/manuals/bc/ENP.1
	+++ b/contrib/bc/manuals/bc/ENP.1
	@@ -1,1299 +1,1393 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/ENP.1.md b/contrib/bc/manuals/bc/ENP.1.md
	index 20b60a7a9081..6c6dd2780e81 100644
	--- a/contrib/bc/manuals/bc/ENP.1.md
	+++ b/contrib/bc/manuals/bc/ENP.1.md
	@@ -1,1079 +1,1085 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1).

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/EP.1 b/contrib/bc/manuals/bc/EP.1
	index 62ee57bfccc7..453b768082ed 100644
	--- a/contrib/bc/manuals/bc/EP.1
	+++ b/contrib/bc/manuals/bc/EP.1
	@@ -1,1306 +1,1400 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	.IP
	.nf
	\f[C]
	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.
	\f[R]
	.fi
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library before running any code, including
	-any expressions or files specified on the command line.
	-.RS
	-.PP
	-To learn what is in the library, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	+.PP
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library before running any
	+code, including any expressions or files specified on the command line.
	+.IP
	+.nf
	+\f[C]
	+To learn what is in the library, see the LIBRARY section.
	+\f[R]
	+.fi
	+.PP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Number 6 is a \f[B]non-portable extension\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	-\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	.PP
	+\f[B]=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R]
	+\f[B]%=\f[R] \f[B]\[ha]=\f[R]
	+.PP
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+\f[R]
	+.fi
	+.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below are available when the \f[B]-l\f[R] or
	\f[B]--mathlib\f[R] command-line flags are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator and the corresponding assignment
	-operator.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator and the corresponding assignment operator.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/EP.1.md b/contrib/bc/manuals/bc/EP.1.md
	index 9a36b99bcb1c..62530a4a9744 100644
	--- a/contrib/bc/manuals/bc/EP.1.md
	+++ b/contrib/bc/manuals/bc/EP.1.md
	@@ -1,1087 +1,1093 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1).

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	Turns the globals ibase, obase, and scale into stacks.

	This has the effect that a copy of the current value of all three are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	However, since using this flag means that functions cannot set ibase,
	obase, or scale globally, functions that are made to do so cannot
	work anymore. There are two possible use cases for that, and each has a
	solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase, or
	scale globally for any other purpose, it could be split into one to
	three functions (based on how many globals it sets) and each of those
	functions could return the desired value for a global.

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library before running any code, including any expressions or files
	specified on the command line.

	To learn what is in the library, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 2. Values are output in the specified
	base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. last or a single dot (.)

	Number 6 is a non-portable extension.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	= += -= *\= /= %= \^=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	= += -= *\= /= %= \^=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below are available when the -l or -\-mathlib
	command-line flags are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator and the corresponding assignment operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/H.1 b/contrib/bc/manuals/bc/H.1
	index fe9ac1556522..890630c4243b 100644
	--- a/contrib/bc/manuals/bc/H.1
	+++ b/contrib/bc/manuals/bc/H.1
	@@ -1,2037 +1,2246 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: 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
	+do not want a prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\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
	-do not want a prompt or are not used to having them in bc(1).
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	.PP
	-Any other character following a backslash causes the backslash and
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	+.PP
	+Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/H.1.md b/contrib/bc/manuals/bc/H.1.md
	index 5ba65ba1f5d6..57a753a417e6 100644
	--- a/contrib/bc/manuals/bc/H.1.md
	+++ b/contrib/bc/manuals/bc/H.1.md
	@@ -1,1687 +1,1701 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/HN.1 b/contrib/bc/manuals/bc/HN.1
	index fe6043eb69d1..97965d7a8868 100644
	--- a/contrib/bc/manuals/bc/HN.1
	+++ b/contrib/bc/manuals/bc/HN.1
	@@ -1,2030 +1,2239 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: 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
	+do not want a prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\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
	-do not want a prompt or are not used to having them in bc(1).
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	.PP
	-Any other character following a backslash causes the backslash and
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	+.PP
	+Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/HN.1.md b/contrib/bc/manuals/bc/HN.1.md
	index adf1ffcc29fb..c81f7adcd7e3 100644
	--- a/contrib/bc/manuals/bc/HN.1.md
	+++ b/contrib/bc/manuals/bc/HN.1.md
	@@ -1,1679 +1,1693 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/HNP.1 b/contrib/bc/manuals/bc/HNP.1
	index f407050515b2..e51c6373e732 100644
	--- a/contrib/bc/manuals/bc/HNP.1
	+++ b/contrib/bc/manuals/bc/HNP.1
	@@ -1,2023 +1,2223 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: This option is a no-op.
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	-\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	+\f[B]s(x)\f[R]
	+.PP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]c(x)\f[R]
	+.PP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]a(x)\f[R]
	+.PP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/HNP.1.md b/contrib/bc/manuals/bc/HNP.1.md
	index cd6d2c4836e9..365ee36926a1 100644
	--- a/contrib/bc/manuals/bc/HNP.1.md
	+++ b/contrib/bc/manuals/bc/HNP.1.md
	@@ -1,1673 +1,1679 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/HP.1 b/contrib/bc/manuals/bc/HP.1
	index 33293307f8f3..71c79623abad 100644
	--- a/contrib/bc/manuals/bc/HP.1
	+++ b/contrib/bc/manuals/bc/HP.1
	@@ -1,2030 +1,2230 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: This option is a no-op.
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	-\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	+\f[B]s(x)\f[R]
	+.PP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]c(x)\f[R]
	+.PP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]a(x)\f[R]
	+.PP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/HP.1.md b/contrib/bc/manuals/bc/HP.1.md
	index 7273a346b758..06ad718d3679 100644
	--- a/contrib/bc/manuals/bc/HP.1.md
	+++ b/contrib/bc/manuals/bc/HP.1.md
	@@ -1,1681 +1,1687 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/N.1 b/contrib/bc/manuals/bc/N.1
	index faf35eb8b255..d5df71cb5a18 100644
	--- a/contrib/bc/manuals/bc/N.1
	+++ b/contrib/bc/manuals/bc/N.1
	@@ -1,2050 +1,2259 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	It also has many extensions and extra features beyond other
	implementations.
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: 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
	+do not want a prompt or are not used to having them in bc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\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
	-do not want a prompt or are not used to having them in bc(1).
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in bc(1).
	Most of those users would want to put this option in
	\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	-.RS
	+This option is also useful in hash bang lines of bc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the read() built-in function is called.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	.PP
	-Any other character following a backslash causes the backslash and
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	+.PP
	+Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	+.PP
	\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/N.1.md b/contrib/bc/manuals/bc/N.1.md
	index 5c877ef79823..1bb215640871 100644
	--- a/contrib/bc/manuals/bc/N.1.md
	+++ b/contrib/bc/manuals/bc/N.1.md
	@@ -1,1696 +1,1710 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1). It also has many extensions and extra features beyond
	other implementations.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in bc(1). Most of those users
	would want to put this option in BC_ENV_ARGS (see the
	ENVIRONMENT VARIABLES section).

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in bc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of bc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the read() built-in function is called.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/NP.1 b/contrib/bc/manuals/bc/NP.1
	index 149037fd9705..339ab9e214d9 100644
	--- a/contrib/bc/manuals/bc/NP.1
	+++ b/contrib/bc/manuals/bc/NP.1
	@@ -1,2043 +1,2243 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	It also has many extensions and extra features beyond other
	implementations.
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: This option is a no-op.
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	-\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	+\f[B]s(x)\f[R]
	+.PP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]c(x)\f[R]
	+.PP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]a(x)\f[R]
	+.PP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/NP.1.md b/contrib/bc/manuals/bc/NP.1.md
	index 518d237020df..c8ae18b194bf 100644
	--- a/contrib/bc/manuals/bc/NP.1.md
	+++ b/contrib/bc/manuals/bc/NP.1.md
	@@ -1,1690 +1,1696 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1). It also has many extensions and extra features beyond
	other implementations.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bc/P.1 b/contrib/bc/manuals/bc/P.1
	index cfe4afe1fdf3..ed539824b385 100644
	--- a/contrib/bc/manuals/bc/P.1
	+++ b/contrib/bc/manuals/bc/P.1
	@@ -1,2050 +1,2250 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	.SH NAME
	.PP
	bc - arbitrary-precision decimal arithmetic language and calculator
	.SH SYNOPSIS
	.PP
	-\f[B]bc\f[R] [\f[B]-ghilPqsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	+\f[B]bc\f[R] [\f[B]-ghilPqRsvVw\f[R]] [\f[B]--global-stacks\f[R]]
	[\f[B]--help\f[R]] [\f[B]--interactive\f[R]] [\f[B]--mathlib\f[R]]
	-[\f[B]--no-prompt\f[R]] [\f[B]--quiet\f[R]] [\f[B]--standard\f[R]]
	-[\f[B]--warn\f[R]] [\f[B]--version\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]\&...]
	+[\f[B]--no-prompt\f[R]] [\f[B]--no-read-prompt\f[R]] [\f[B]--quiet\f[R]]
	+[\f[B]--standard\f[R]] [\f[B]--warn\f[R]] [\f[B]--version\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
	bc(1) is an interactive processor for a language first standardized in
	1991 by POSIX.
	(The current standard is
	here (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).)
	The language provides unlimited precision decimal arithmetic and is
	somewhat C-like, but there are differences.
	Such differences will be noted in this document.
	.PP
	After parsing and handling options, this bc(1) reads any files given on
	the command line and executes them before reading from \f[B]stdin\f[R].
	.PP
	This bc(1) is a drop-in replacement for \f[I]any\f[R] bc(1), including
	(and especially) the GNU bc(1).
	It also has many extensions and extra features beyond other
	implementations.
	.SH OPTIONS
	.PP
	The following are the options that bc(1) accepts.
	-.TP
	+.PP
	\f[B]-g\f[R], \f[B]--global-stacks\f[R]
	-Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], and
	-\f[B]seed\f[R] into stacks.
	-.RS
	.PP
	-This has the effect that a copy of the current value of all four are
	-pushed onto a stack for every function call, as well as popped when
	-every function returns.
	-This means that functions can assign to any and all of those globals
	-without worrying that the change will affect other functions.
	-Thus, a hypothetical function named \f[B]output(x,b)\f[R] that simply
	-printed \f[B]x\f[R] in base \f[B]b\f[R] could be written like this:
	+: Turns the globals \f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R],
	+and \f[B]seed\f[R] into stacks.
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- obase=b
	- x
	-}
	+This has the effect that a copy of the current value of all four are pushed
	+onto a stack for every function call, as well as popped when every function
	+returns. This means that functions can assign to any and all of those
	+globals without worrying that the change will affect other functions.
	+Thus, a hypothetical function named output(x,b) that simply printed
	+x in base b could be written like this:
	+
	+ define void output(x, b) {
	+ obase=b
	+ x
	+ }
	+
	+instead of like this:
	+
	+ define void output(x, b) {
	+ auto c
	+ c=obase
	+ obase=b
	+ x
	+ obase=c
	+ }
	+
	+This makes writing functions much easier.
	+
	+(Note: the function output(x,b) exists in the extended math library.
	+ See the LIBRARY section.)
	+
	+However, since using this flag means that functions cannot set ibase,
	+obase, scale, or seed globally, functions that are made to do so
	+cannot work anymore. There are two possible use cases for that, and each has
	+a solution.
	+
	+First, if a function is called on startup to turn bc(1) into a number
	+converter, it is possible to replace that capability with various shell
	+aliases. Examples:
	+
	+ alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	+ alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+
	+Second, if the purpose of a function is to set ibase, obase,
	+scale, or seed globally for any other purpose, it could be split
	+into one to four functions (based on how many globals it sets) and each of
	+those functions could return the desired value for a global.
	+
	+For functions that set seed, the value assigned to seed is not
	+propagated to parent functions. This means that the sequence of
	+pseudo-random numbers that they see will not be the same sequence of
	+pseudo-random numbers that any parent sees. This is only the case once
	+seed has been set.
	+
	+If a function desires to not affect the sequence of pseudo-random numbers
	+of its parents, but wants to use the same seed, it can use the following
	+line:
	+
	+ seed = seed
	+
	+If the behavior of this option is desired for every run of bc(1), then users
	+could make sure to define BC_ENV_ARGS and include this option (see the
	+ENVIRONMENT VARIABLES section for more details).
	+
	+If -s, -w, or any equivalents are used, this option is ignored.
	+
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-instead of like this:
	+\f[B]-h\f[R], \f[B]--help\f[R]
	+.PP
	+: Prints a usage message and quits.
	+.PP
	+\f[B]-i\f[R], \f[B]--interactive\f[R]
	+.PP
	+: Forces interactive mode.
	+(See the \f[B]INTERACTIVE MODE\f[R] section.)
	.IP
	.nf
	\f[C]
	-define void output(x, b) {
	- auto c
	- c=obase
	- obase=b
	- x
	- obase=c
	-}
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-This makes writing functions much easier.
	-.PP
	-(\f[B]Note\f[R]: the function \f[B]output(x,b)\f[R] exists in the
	-extended math library.
	-See the \f[B]LIBRARY\f[R] section.)
	-.PP
	-However, since using this flag means that functions cannot set
	-\f[B]ibase\f[R], \f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R]
	-globally, functions that are made to do so cannot work anymore.
	-There are two possible use cases for that, and each has a solution.
	+\f[B]-l\f[R], \f[B]--mathlib\f[R]
	.PP
	-First, if a function is called on startup to turn bc(1) into a number
	-converter, it is possible to replace that capability with various shell
	-aliases.
	-Examples:
	+: Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to
	+\f[B]20\f[R] and loads the included math library and the extended math
	+library before running any code, including any expressions or files
	+specified on the command line.
	.IP
	.nf
	\f[C]
	-alias d2o=\[dq]bc -e ibase=A -e obase=8\[dq]
	-alias h2b=\[dq]bc -e ibase=G -e obase=2\[dq]
	+To learn what is in the libraries, see the LIBRARY section.
	\f[R]
	.fi
	.PP
	-Second, if the purpose of a function is to set \f[B]ibase\f[R],
	-\f[B]obase\f[R], \f[B]scale\f[R], or \f[B]seed\f[R] globally for any
	-other purpose, it could be split into one to four functions (based on
	-how many globals it sets) and each of those functions could return the
	-desired value for a global.
	-.PP
	-For functions that set \f[B]seed\f[R], the value assigned to
	-\f[B]seed\f[R] is not propagated to parent functions.
	-This means that the sequence of pseudo-random numbers that they see will
	-not be the same sequence of pseudo-random numbers that any parent sees.
	-This is only the case once \f[B]seed\f[R] has been set.
	+\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	.PP
	-If a function desires to not affect the sequence of pseudo-random
	-numbers of its parents, but wants to use the same \f[B]seed\f[R], it can
	-use the following line:
	+: This option is a no-op.
	.IP
	.nf
	\f[C]
	-seed = seed
	+This is a non-portable extension.
	\f[R]
	.fi
	.PP
	-If the behavior of this option is desired for every run of bc(1), then
	-users could make sure to define \f[B]BC_ENV_ARGS\f[R] and include this
	-option (see the \f[B]ENVIRONMENT VARIABLES\f[R] section for more
	-details).
	-.PP
	-If \f[B]-s\f[R], \f[B]-w\f[R], or any equivalents are used, this option
	-is ignored.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	-\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	-(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]-l\f[R], \f[B]--mathlib\f[R]
	-Sets \f[B]scale\f[R] (see the \f[B]SYNTAX\f[R] section) to \f[B]20\f[R]
	-and loads the included math library and the extended math library before
	-running any code, including any expressions or files specified on the
	-command line.
	-.RS
	-.PP
	-To learn what is in the libraries, see the \f[B]LIBRARY\f[R] section.
	-.RE
	-.TP
	-\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	+: Because bc(1) was built without support for prompts, this option is a
	+no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-q\f[R], \f[B]--quiet\f[R]
	-This option is for compatibility with the GNU
	+.PP
	+: This option is for compatibility with the GNU
	bc(1) (https://www.gnu.org/software/bc/); it is a no-op.
	Without this option, GNU bc(1) prints a copyright header.
	This bc(1) only prints the copyright header if one or more of the
	\f[B]-v\f[R], \f[B]-V\f[R], or \f[B]--version\f[R] options are given.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-s\f[R], \f[B]--standard\f[R]
	-Process exactly the language defined by the
	+.PP
	+: Process exactly the language defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	and error if any extensions are used.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Print the version information (copyright header) and exit.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-w\f[R], \f[B]--warn\f[R]
	-Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	+.PP
	+: Like \f[B]-s\f[R] and \f[B]--standard\f[R], except that warnings (and
	not errors) are printed for non-standard extensions and execution
	continues normally.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--file\f[R], whether on the command-line or in
	-\f[B]BC_ENV_ARGS\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, bc(1) will give a fatal error and
	-exit.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in BC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-If this option is given on the command-line (i.e., not in
	-\f[B]BC_ENV_ARGS\f[R], see the \f[B]ENVIRONMENT VARIABLES\f[R] section),
	-then after processing all expressions and files, bc(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]--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, bc(1) will give a fatal error and
	-exit.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, bc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, bc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]bc >&-\f[R], it will quit with an error.
	This is done so that bc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other bc(1) implementations, this bc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]bc 2>&-\f[R], it will quit with an error.
	This is done so that bc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other bc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	The syntax for bc(1) programs is mostly C-like, with some differences.
	This bc(1) follows the POSIX
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	which is a much more thorough resource for the language this bc(1)
	accepts.
	This section is meant to be a summary and a listing of all the
	extensions to the standard.
	.PP
	In the sections below, \f[B]E\f[R] means expression, \f[B]S\f[R] means
	statement, and \f[B]I\f[R] means identifier.
	.PP
	Identifiers (\f[B]I\f[R]) start with a lowercase letter and can be
	followed by any number (up to \f[B]BC_NAME_MAX-1\f[R]) of lowercase
	letters (\f[B]a-z\f[R]), digits (\f[B]0-9\f[R]), and underscores
	(\f[B]_\f[R]).
	The regex is \f[B][a-z][a-z0-9_]*\f[R].
	Identifiers with more than one character (letter) are a
	\f[B]non-portable extension\f[R].
	.PP
	\f[B]ibase\f[R] is a global variable determining how to interpret
	constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	If the \f[B]-s\f[R] (\f[B]--standard\f[R]) and \f[B]-w\f[R]
	(\f[B]--warn\f[R]) flags were not given on the command line, the max
	allowable value for \f[B]ibase\f[R] is \f[B]36\f[R].
	Otherwise, it is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in bc(1)
	programs with the \f[B]maxibase()\f[R] built-in function.
	.PP
	\f[B]obase\f[R] is a global variable determining how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]BC_BASE_MAX\f[R] and
	can be queried in bc(1) programs with the \f[B]maxobase()\f[R] built-in
	function.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a global variable that sets the precision of any operations, with
	exceptions.
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] is \f[B]BC_SCALE_MAX\f[R]
	and can be queried in bc(1) programs with the \f[B]maxscale()\f[R]
	built-in function.
	.PP
	bc(1) has both \f[I]global\f[R] variables and \f[I]local\f[R] variables.
	All \f[I]local\f[R] variables are local to the function; they are
	parameters or are introduced in the \f[B]auto\f[R] list of a function
	(see the \f[B]FUNCTIONS\f[R] section).
	If a variable is accessed which is not a parameter or in the
	\f[B]auto\f[R] list, it is assumed to be \f[I]global\f[R].
	If a parent function has a \f[I]local\f[R] variable version of a
	variable that a child function considers \f[I]global\f[R], the value of
	that \f[I]global\f[R] variable in the child function is the value of the
	variable in the parent function, not the value of the actual
	\f[I]global\f[R] variable.
	.PP
	All of the above applies to arrays as well.
	.PP
	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence
	operator is an assignment operator \f[I]and\f[R] the expression is
	notsurrounded by parentheses.
	.PP
	The value that is printed is also assigned to the special variable
	\f[B]last\f[R].
	A single dot (\f[B].\f[R]) may also be used as a synonym for
	\f[B]last\f[R].
	These are \f[B]non-portable extensions\f[R].
	.PP
	Either semicolons or newlines may separate statements.
	.SS Comments
	.PP
	There are two kinds of comments:
	.IP "1." 3
	Block comments are enclosed in \f[B]/\f[R] and \f[B]/\f[R].
	.IP "2." 3
	Line comments go from \f[B]#\f[R] until, and not including, the next
	newline.
	This is a \f[B]non-portable extension\f[R].
	.SS Named Expressions
	.PP
	The following are named expressions in bc(1):
	.IP "1." 3
	Variables: \f[B]I\f[R]
	.IP "2." 3
	Array Elements: \f[B]I[E]\f[R]
	.IP "3." 3
	\f[B]ibase\f[R]
	.IP "4." 3
	\f[B]obase\f[R]
	.IP "5." 3
	\f[B]scale\f[R]
	.IP "6." 3
	\f[B]seed\f[R]
	.IP "7." 3
	\f[B]last\f[R] or a single dot (\f[B].\f[R])
	.PP
	Numbers 6 and 7 are \f[B]non-portable extensions\f[R].
	.PP
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	.PP
	The \f[I]scale\f[R] and sign of the value may be significant.
	.PP
	If a previously used \f[B]seed\f[R] value is assigned to \f[B]seed\f[R]
	and used again, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers as it did when the
	\f[B]seed\f[R] value was previously used.
	.PP
	The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	returned if \f[B]seed\f[R] is queried again immediately.
	However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	same sequence of pseudo-random numbers.
	This means that certain values assigned to \f[B]seed\f[R] will
	\f[I]not\f[R] produce unique sequences of pseudo-random numbers.
	The value of \f[B]seed\f[R] will change after any use of the
	\f[B]rand()\f[R] and \f[B]irand(E)\f[R] operands (see the
	\f[I]Operands\f[R] subsection below), except if the parameter passed to
	\f[B]irand(E)\f[R] is \f[B]0\f[R], \f[B]1\f[R], or negative.
	.PP
	There is no limit to the length (number of significant decimal digits)
	or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	.PP
	Variables and arrays do not interfere; users can have arrays named the
	same as variables.
	This also applies to functions (see the \f[B]FUNCTIONS\f[R] section), so
	a user can have a variable, array, and function that all have the same
	name, and they will not shadow each other, whether inside of functions
	or not.
	.PP
	Named expressions are required as the operand of
	\f[B]increment\f[R]/\f[B]decrement\f[R] operators and as the left side
	of \f[B]assignment\f[R] operators (see the \f[I]Operators\f[R]
	subsection).
	.SS Operands
	.PP
	The following are valid operands in bc(1):
	.IP " 1." 4
	Numbers (see the \f[I]Numbers\f[R] subsection below).
	.IP " 2." 4
	Array indices (\f[B]I[E]\f[R]).
	.IP " 3." 4
	\f[B](E)\f[R]: The value of \f[B]E\f[R] (used to change precedence).
	.IP " 4." 4
	\f[B]sqrt(E)\f[R]: The square root of \f[B]E\f[R].
	\f[B]E\f[R] must be non-negative.
	.IP " 5." 4
	\f[B]length(E)\f[R]: The number of significant decimal digits in
	\f[B]E\f[R].
	.IP " 6." 4
	\f[B]length(I[])\f[R]: The number of elements in the array \f[B]I\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 7." 4
	\f[B]scale(E)\f[R]: The \f[I]scale\f[R] of \f[B]E\f[R].
	.IP " 8." 4
	\f[B]abs(E)\f[R]: The absolute value of \f[B]E\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP " 9." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a non-\f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.IP "10." 4
	\f[B]read()\f[R]: Reads a line from \f[B]stdin\f[R] and uses that as an
	expression.
	The result of that expression is the result of the \f[B]read()\f[R]
	operand.
	This is a \f[B]non-portable extension\f[R].
	.IP "11." 4
	\f[B]maxibase()\f[R]: The max allowable \f[B]ibase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "12." 4
	\f[B]maxobase()\f[R]: The max allowable \f[B]obase\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "13." 4
	\f[B]maxscale()\f[R]: The max allowable \f[B]scale\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "14." 4
	\f[B]rand()\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and \f[B]BC_RAND_MAX\f[R] (inclusive).
	Using this operand will change the value of \f[B]seed\f[R].
	This is a \f[B]non-portable extension\f[R].
	.IP "15." 4
	\f[B]irand(E)\f[R]: A pseudo-random integer between \f[B]0\f[R]
	(inclusive) and the value of \f[B]E\f[R] (exclusive).
	-If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[cq]s
	+If \f[B]E\f[R] is negative or is a non-integer (\f[B]E\f[R]\[aq]s
	\f[I]scale\f[R] is not \f[B]0\f[R]), an error is raised, and bc(1)
	resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R] remains
	unchanged.
	If \f[B]E\f[R] is larger than \f[B]BC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]BC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this operand is
	unbounded.
	Using this operand will change the value of \f[B]seed\f[R], unless the
	value of \f[B]E\f[R] is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is returned, and \f[B]seed\f[R] is
	\f[I]not\f[R] changed.
	This is a \f[B]non-portable extension\f[R].
	.IP "16." 4
	\f[B]maxrand()\f[R]: The max integer returned by \f[B]rand()\f[R].
	This is a \f[B]non-portable extension\f[R].
	.PP
	The integers generated by \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are
	guaranteed to be as unbiased as possible, subject to the limitations of
	the pseudo-random number generator.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	generator with \f[B]rand()\f[R] and \f[B]irand(E)\f[R] are guaranteed to
	\f[I]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from bc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.SS Numbers
	.PP
	Numbers are strings made up of digits, uppercase letters, and at most
	\f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]BC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]Z\f[R] alone always equals decimal \f[B]35\f[R].
	.PP
	In addition, bc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e-3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	Using scientific notation is an error or warning if the \f[B]-s\f[R] or
	\f[B]-w\f[R], respectively, command-line options (or equivalents) are
	given.
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if bc(1) is given the number string
	\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SS Operators
	.PP
	The following arithmetic and logical operators can be used.
	They are listed in order of decreasing precedence.
	Operators in the same group have the same precedence.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-Type: Prefix and Postfix
	-.RS
	.PP
	+: Type: Prefix and Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: increment, decrement
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]increment\f[R], \f[B]decrement\f[R]
	-.RE
	-.TP
	\f[B]-\f[R] \f[B]!\f[R]
	-Type: Prefix
	-.RS
	.PP
	+: Type: Prefix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: negation, boolean not
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]negation\f[R], \f[B]boolean not\f[R]
	-.RE
	-.TP
	\f[B]$\f[R]
	-Type: Postfix
	-.RS
	.PP
	+: Type: Postfix
	+.IP
	+.nf
	+\f[C]
	Associativity: None
	+
	+Description: truncation
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]truncation\f[R]
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: set precision
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]set precision\f[R]
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: power
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]power\f[R]
	-.RE
	-.TP
	\f[B]*\f[R] \f[B]/\f[R] \f[B]%\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: multiply, divide, modulus
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]multiply\f[R], \f[B]divide\f[R], \f[B]modulus\f[R]
	-.RE
	-.TP
	\f[B]+\f[R] \f[B]-\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: add, subtract
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]add\f[R], \f[B]subtract\f[R]
	-.RE
	-.TP
	\f[B]<<\f[R] \f[B]>>\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: shift left, shift right
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]shift left\f[R], \f[B]shift right\f[R]
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-Type: Binary
	-.RS
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Right
	+
	+Description: assignment
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]assignment\f[R]
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-Type: Binary
	-.RS
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: relational
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]relational\f[R]
	-.RE
	-.TP
	\f[B]&&\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	+
	+Description: boolean and
	+\f[R]
	+.fi
	.PP
	-Description: \f[B]boolean and\f[R]
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-Type: Binary
	-.RS
	.PP
	+: Type: Binary
	+.IP
	+.nf
	+\f[C]
	Associativity: Left
	-.PP
	-Description: \f[B]boolean or\f[R]
	-.RE
	+
	+Description: boolean or
	+\f[R]
	+.fi
	.PP
	The operators will be described in more detail below.
	-.TP
	+.PP
	\f[B]++\f[R] \f[B]--\f[R]
	-The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	+.PP
	+: The prefix and postfix \f[B]increment\f[R] and \f[B]decrement\f[R]
	operators behave exactly like they would in C.
	They require a named expression (see the \f[I]Named Expressions\f[R]
	subsection) as an operand.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The prefix versions of these operators are more efficient; use them where
	+possible.
	+\f[R]
	+.fi
	.PP
	-The prefix versions of these operators are more efficient; use them
	-where possible.
	-.RE
	-.TP
	\f[B]-\f[R]
	-The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	+.PP
	+: The \f[B]negation\f[R] operator returns \f[B]0\f[R] if a user attempts
	to negate any expression with the value \f[B]0\f[R].
	Otherwise, a copy of the expression with its sign flipped is returned.
	-.TP
	+.PP
	\f[B]!\f[R]
	-The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the expression
	-is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]boolean not\f[R] operator returns \f[B]1\f[R] if the
	+expression is \f[B]0\f[R], or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]$\f[R]
	-The \f[B]truncation\f[R] operator returns a copy of the given expression
	-with all of its \f[I]scale\f[R] removed.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The \f[B]truncation\f[R] operator returns a copy of the given
	+expression with all of its \f[I]scale\f[R] removed.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]\[at]\f[R]
	-The \f[B]set precision\f[R] operator takes two expressions and returns a
	-copy of the first with its \f[I]scale\f[R] equal to the value of the
	+.PP
	+: The \f[B]set precision\f[R] operator takes two expressions and returns
	+a copy of the first with its \f[I]scale\f[R] equal to the value of the
	second expression.
	That could either mean that the number is returned without change (if
	the \f[I]scale\f[R] of the first expression matches the value of the
	second expression), extended (if it is less), or truncated (if it is
	more).
	-.RS
	-.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	+.PP
	+: The \f[B]power\f[R] operator (not the \f[B]exclusive or\f[R] operator,
	as it would be in C) takes two expressions and raises the first to the
	power of the value of the second.
	The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale), and if it is
	+negative, the first value must be non-zero.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]), and if it
	-is negative, the first value must be non-zero.
	-.RE
	-.TP
	\f[B]*\f[R]
	-The \f[B]multiply\f[R] operator takes two expressions, multiplies them,
	-and returns the product.
	+.PP
	+: The \f[B]multiply\f[R] operator takes two expressions, multiplies
	+them, and returns the product.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The \f[B]divide\f[R] operator takes two expressions, divides them, and
	+.PP
	+: The \f[B]divide\f[R] operator takes two expressions, divides them, and
	returns the quotient.
	The \f[I]scale\f[R] of the result shall be the value of \f[B]scale\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]%\f[R]
	-The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]modulus\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and evaluates them by 1) Computing \f[B]a/b\f[R] to current
	\f[B]scale\f[R] and 2) Using the result of step 1 to calculate
	\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	\f[B]max(scale+scale(b),scale(a))\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The second expression must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]+\f[R]
	-The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]add\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the sum, with a \f[I]scale\f[R] equal to the
	max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]-\f[R]
	-The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	+.PP
	+: The \f[B]subtract\f[R] operator takes two expressions, \f[B]a\f[R] and
	\f[B]b\f[R], and returns the difference, with a \f[I]scale\f[R] equal to
	the max of the \f[I]scale\f[R]s of \f[B]a\f[R] and \f[B]b\f[R].
	-.TP
	+.PP
	\f[B]<<\f[R]
	-The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	-decimal point moved \f[B]b\f[R] places to the right.
	-.RS
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+: The \f[B]left shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	+decimal point moved \f[B]b\f[R] places to the right.
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]>>\f[R]
	-The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	+.PP
	+: The \f[B]right shift\f[R] operator takes two expressions, \f[B]a\f[R]
	and \f[B]b\f[R], and returns a copy of the value of \f[B]a\f[R] with its
	decimal point moved \f[B]b\f[R] places to the left.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The second expression must be an integer (no scale) and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The second expression must be an integer (no \f[I]scale\f[R]) and
	-non-negative.
	+\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R]
	+\f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]=\f[R] \f[B]<<=\f[R] \f[B]>>=\f[R] \f[B]+=\f[R] \f[B]-=\f[R] \f[B]*=\f[R] \f[B]/=\f[R] \f[B]%=\f[R] \f[B]\[ha]=\f[R] \f[B]\[at]=\f[R]
	-The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R] and
	-\f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the \f[I]Named
	-Expressions\f[R] subsection).
	-.RS
	-.PP
	-For \f[B]=\f[R], \f[B]b\f[R] is copied and the result is assigned to
	-\f[B]a\f[R].
	-For all others, \f[B]a\f[R] and \f[B]b\f[R] are applied as operands to
	-the corresponding arithmetic operator and the result is assigned to
	-\f[B]a\f[R].
	-.PP
	-The \f[B]assignment\f[R] operators that correspond to operators that are
	-extensions are themselves \f[B]non-portable extensions\f[R].
	-.RE
	-.TP
	-\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R] \f[B]>\f[R]
	-The \f[B]relational\f[R] operators compare two expressions, \f[B]a\f[R]
	-and \f[B]b\f[R], and if the relation holds, according to C language
	-semantics, the result is \f[B]1\f[R].
	-Otherwise, it is \f[B]0\f[R].
	-.RS
	+: The \f[B]assignment\f[R] operators take two expressions, \f[B]a\f[R]
	+and \f[B]b\f[R] where \f[B]a\f[R] is a named expression (see the
	+\f[I]Named Expressions\f[R] subsection).
	+.IP
	+.nf
	+\f[C]
	+For =, b is copied and the result is assigned to a. For all
	+others, a and b are applied as operands to the corresponding
	+arithmetic operator and the result is assigned to a.
	+
	+The assignment operators that correspond to operators that are
	+extensions are themselves non-portable extensions.
	+\f[R]
	+.fi
	.PP
	+\f[B]==\f[R] \f[B]<=\f[R] \f[B]>=\f[R] \f[B]!=\f[R] \f[B]<\f[R]
	+\f[B]>\f[R]
	+.PP
	+: The \f[B]relational\f[R] operators compare two expressions,
	+\f[B]a\f[R] and \f[B]b\f[R], and if the relation holds, according to C
	+language semantics, the result is \f[B]1\f[R].
	+Otherwise, it is \f[B]0\f[R].
	+.IP
	+.nf
	+\f[C]
	Note that unlike in C, these operators have a lower precedence than the
	-\f[B]assignment\f[R] operators, which means that \f[B]a=b>c\f[R] is
	-interpreted as \f[B](a=b)>c\f[R].
	+assignment operators, which means that a=b\[rs]>c is interpreted as
	+(a=b)\[rs]>c.
	+
	+Also, unlike the [standard][1] requires, these operators can appear anywhere
	+any other expressions can be used. This allowance is a
	+non-portable extension.
	+\f[R]
	+.fi
	.PP
	-Also, unlike the
	-standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	-requires, these operators can appear anywhere any other expressions can
	-be used.
	-This allowance is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]&&\f[R]
	-The \f[B]boolean and\f[R] operator takes two expressions and returns
	-\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	+: The \f[B]boolean and\f[R] operator takes two expressions and returns
	+\f[B]1\f[R] if both expressions are non-zero, \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\|\f[R]
	-The \f[B]boolean or\f[R] operator takes two expressions and returns
	+.PP
	+: The \f[B]boolean or\f[R] operator takes two expressions and returns
	\f[B]1\f[R] if one of the expressions is non-zero, \f[B]0\f[R]
	otherwise.
	-.RS
	-.PP
	-This is \f[I]not\f[R] a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is not a short-circuit operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Statements
	.PP
	The following items are statements:
	.IP " 1." 4
	\f[B]E\f[R]
	.IP " 2." 4
	-\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] \&... \f[B];\f[R] \f[B]S\f[R]
	-\f[B]}\f[R]
	+\f[B]{\f[R] \f[B]S\f[R] \f[B];\f[R] ...
	+\f[B];\f[R] \f[B]S\f[R] \f[B]}\f[R]
	.IP " 3." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 4." 4
	\f[B]if\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	\f[B]else\f[R] \f[B]S\f[R]
	.IP " 5." 4
	\f[B]while\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 6." 4
	\f[B]for\f[R] \f[B](\f[R] \f[B]E\f[R] \f[B];\f[R] \f[B]E\f[R]
	\f[B];\f[R] \f[B]E\f[R] \f[B])\f[R] \f[B]S\f[R]
	.IP " 7." 4
	An empty statement
	.IP " 8." 4
	\f[B]break\f[R]
	.IP " 9." 4
	\f[B]continue\f[R]
	.IP "10." 4
	\f[B]quit\f[R]
	.IP "11." 4
	\f[B]halt\f[R]
	.IP "12." 4
	\f[B]limits\f[R]
	.IP "13." 4
	A string of characters, enclosed in double quotes
	.IP "14." 4
	-\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] \&... \f[B],\f[R] \f[B]E\f[R]
	+\f[B]print\f[R] \f[B]E\f[R] \f[B],\f[R] ...
	+\f[B],\f[R] \f[B]E\f[R]
	.IP "15." 4
	\f[B]I()\f[R], \f[B]I(E)\f[R], \f[B]I(E, E)\f[R], and so on, where
	\f[B]I\f[R] is an identifier for a \f[B]void\f[R] function (see the
	\f[I]Void Functions\f[R] subsection of the \f[B]FUNCTIONS\f[R] section).
	The \f[B]E\f[R] argument(s) may also be arrays of the form
	\f[B]I[]\f[R], which will automatically be turned into array references
	(see the \f[I]Array References\f[R] subsection of the
	\f[B]FUNCTIONS\f[R] section) if the corresponding parameter in the
	function definition is an array reference.
	.PP
	Numbers 4, 9, 11, 12, 14, and 15 are \f[B]non-portable extensions\f[R].
	.PP
	Also, as a \f[B]non-portable extension\f[R], any or all of the
	expressions in the header of a for loop may be omitted.
	If the condition (second expression) is omitted, it is assumed to be a
	constant \f[B]1\f[R].
	.PP
	The \f[B]break\f[R] statement causes a loop to stop iterating and resume
	execution immediately following a loop.
	This is only allowed in loops.
	.PP
	The \f[B]continue\f[R] statement causes a loop iteration to stop early
	and returns to the start of the loop, including testing the loop
	condition.
	This is only allowed in loops.
	.PP
	The \f[B]if\f[R] \f[B]else\f[R] statement does the same thing as in C.
	.PP
	The \f[B]quit\f[R] statement causes bc(1) to quit, even if it is on a
	branch that will not be executed (it is a compile-time command).
	.PP
	The \f[B]halt\f[R] statement causes bc(1) to quit, if it is executed.
	(Unlike \f[B]quit\f[R] if it is on a branch of an \f[B]if\f[R] statement
	that is not executed, bc(1) does not quit.)
	.PP
	The \f[B]limits\f[R] statement prints the limits that this bc(1) is
	subject to.
	This is like the \f[B]quit\f[R] statement in that it is a compile-time
	command.
	.PP
	An expression by itself is evaluated and printed, followed by a newline.
	.PP
	Both scientific notation and engineering notation are available for
	printing the results of expressions.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R], and engineering notation is activated by assigning
	\f[B]1\f[R] to \f[B]obase\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Scientific notation and engineering notation are disabled if bc(1) is
	run with either the \f[B]-s\f[R] or \f[B]-w\f[R] command-line options
	(or equivalents).
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	.SS Print Statement
	.PP
	-The \[lq]expressions\[rq] in a \f[B]print\f[R] statement may also be
	+The \[dq]expressions\[dq] in a \f[B]print\f[R] statement may also be
	strings.
	If they are, there are backslash escape sequences that are interpreted
	specially.
	What those sequences are, and what they cause to be printed, are shown
	below:
	.PP
	-.TS
	-tab(@);
	-l l.
	-T{
	-\f[B]\[rs]a\f[R]
	-T}@T{
	-\f[B]\[rs]a\f[R]
	-T}
	-T{
	-\f[B]\[rs]b\f[R]
	-T}@T{
	-\f[B]\[rs]b\f[R]
	-T}
	-T{
	-\f[B]\[rs]\[rs]\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]e\f[R]
	-T}@T{
	-\f[B]\[rs]\f[R]
	-T}
	-T{
	-\f[B]\[rs]f\f[R]
	-T}@T{
	-\f[B]\[rs]f\f[R]
	-T}
	-T{
	-\f[B]\[rs]n\f[R]
	-T}@T{
	-\f[B]\[rs]n\f[R]
	-T}
	-T{
	-\f[B]\[rs]q\f[R]
	-T}@T{
	-\f[B]\[dq]\f[R]
	-T}
	-T{
	-\f[B]\[rs]r\f[R]
	-T}@T{
	-\f[B]\[rs]r\f[R]
	-T}
	-T{
	-\f[B]\[rs]t\f[R]
	-T}@T{
	-\f[B]\[rs]t\f[R]
	-T}
	-.TE
	+ * * * * *
	+.PP
	+\f[B]\[rs]a\f[R] \f[B]\[rs]a\f[R] \f[B]\[rs]b\f[R] \f[B]\[rs]b\f[R]
	+\f[B]\[rs]\[rs]\f[R] \f[B]\[rs]\f[R] \f[B]\[rs]e\f[R] \f[B]\[rs]\f[R]
	+\f[B]\[rs]f\f[R] \f[B]\[rs]f\f[R] \f[B]\[rs]n\f[R] \f[B]\[rs]n\f[R]
	+\f[B]\[rs]q\f[R] \f[B]\[dq]\f[R] \f[B]\[rs]r\f[R] \f[B]\[rs]r\f[R]
	+\f[B]\[rs]t\f[R] \f[B]\[rs]t\f[R]
	+.PP
	+ * * * * *
	.PP
	Any other character following a backslash causes the backslash and
	character to be printed as-is.
	.PP
	Any non-string expression in a print statement shall be assigned to
	\f[B]last\f[R], like any other expression that is printed.
	.SS Order of Evaluation
	.PP
	All expressions in a statment are evaluated left to right, except as
	necessary to maintain order of operations.
	This means, for example, assuming that \f[B]i\f[R] is equal to
	\f[B]0\f[R], in the expression
	.IP
	.nf
	\f[C]
	a[i++] = i++
	\f[R]
	.fi
	.PP
	the first (or 0th) element of \f[B]a\f[R] is set to \f[B]1\f[R], and
	\f[B]i\f[R] is equal to \f[B]2\f[R] at the end of the expression.
	.PP
	This includes function arguments.
	Thus, assuming \f[B]i\f[R] is equal to \f[B]0\f[R], this means that in
	the expression
	.IP
	.nf
	\f[C]
	x(i++, i++)
	\f[R]
	.fi
	.PP
	the first argument passed to \f[B]x()\f[R] is \f[B]0\f[R], and the
	second argument is \f[B]1\f[R], while \f[B]i\f[R] is equal to
	\f[B]2\f[R] before the function starts executing.
	.SH FUNCTIONS
	.PP
	Function definitions are as follows:
	.IP
	.nf
	\f[C]
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	\f[R]
	.fi
	.PP
	Any \f[B]I\f[R] in the parameter list or \f[B]auto\f[R] list may be
	replaced with \f[B]I[]\f[R] to make a parameter or \f[B]auto\f[R] var an
	array, and any \f[B]I\f[R] in the parameter list may be replaced with
	\f[B]*I[]\f[R] to make a parameter an array reference.
	Callers of functions that take array references should not put an
	asterisk in the call; they must be called with just \f[B]I[]\f[R] like
	normal array parameters and will be automatically converted into
	references.
	.PP
	As a \f[B]non-portable extension\f[R], the opening brace of a
	\f[B]define\f[R] statement may appear on the next line.
	.PP
	As a \f[B]non-portable extension\f[R], the return statement may also be
	in one of the following forms:
	.IP "1." 3
	\f[B]return\f[R]
	.IP "2." 3
	\f[B]return\f[R] \f[B](\f[R] \f[B])\f[R]
	.IP "3." 3
	\f[B]return\f[R] \f[B]E\f[R]
	.PP
	The first two, or not specifying a \f[B]return\f[R] statement, is
	equivalent to \f[B]return (0)\f[R], unless the function is a
	\f[B]void\f[R] function (see the \f[I]Void Functions\f[R] subsection
	below).
	.SS Void Functions
	.PP
	Functions can also be \f[B]void\f[R] functions, defined as follows:
	.IP
	.nf
	\f[C]
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	\f[R]
	.fi
	.PP
	They can only be used as standalone expressions, where such an
	expression would be printed alone, except in a print statement.
	.PP
	Void functions can only use the first two \f[B]return\f[R] statements
	listed above.
	They can also omit the return statement entirely.
	.PP
	-The word \[lq]void\[rq] is not treated as a keyword; it is still
	+The word \[dq]void\[dq] is not treated as a keyword; it is still
	possible to have variables, arrays, and functions named \f[B]void\f[R].
	-The word \[lq]void\[rq] is only treated specially right after the
	+The word \[dq]void\[dq] is only treated specially right after the
	\f[B]define\f[R] keyword.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SS Array References
	.PP
	For any array in the parameter list, if the array is declared in the
	form
	.IP
	.nf
	\f[C]
	*I[]
	\f[R]
	.fi
	.PP
	it is a \f[B]reference\f[R].
	Any changes to the array in the function are reflected, when the
	function returns, to the array that was passed in.
	.PP
	Other than this, all function arguments are passed by value.
	.PP
	This is a \f[B]non-portable extension\f[R].
	.SH LIBRARY
	.PP
	All of the functions below, including the functions in the extended math
	library (see the \f[I]Extended Library\f[R] subsection below), are
	available when the \f[B]-l\f[R] or \f[B]--mathlib\f[R] command-line
	flags are given, except that the extended math library is not available
	when the \f[B]-s\f[R] option, the \f[B]-w\f[R] option, or equivalents
	are given.
	.SS Standard Library
	.PP
	The
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	defines the following functions for the math library:
	-.TP
	-\f[B]s(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]c(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	-\f[B]a(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	+\f[B]s(x)\f[R]
	+.PP
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]c(x)\f[R]
	+.PP
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	+\f[B]a(x)\f[R]
	+.PP
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]l(x)\f[R]
	-Returns the natural logarithm of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the natural logarithm of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]e(x)\f[R]
	-Returns the mathematical constant \f[B]e\f[R] raised to the power of
	+.PP
	+: Returns the mathematical constant \f[B]e\f[R] raised to the power of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]j(x, n)\f[R]
	-Returns the bessel integer order \f[B]n\f[R] (truncated) of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	+: Returns the bessel integer order \f[B]n\f[R] (truncated) of
	+\f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.SS Extended Library
	.PP
	The extended library is \f[I]not\f[R] loaded when the
	\f[B]-s\f[R]/\f[B]--standard\f[R] or \f[B]-w\f[R]/\f[B]--warn\f[R]
	options are given since they are not part of the library defined by the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html).
	.PP
	The extended library is a \f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p(x, y)\f[R]
	-Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if \f[B]y\f[R]
	-is not an integer, and returns the result to the current
	-\f[B]scale\f[R].
	-.RS
	.PP
	-It is an error if \f[B]y\f[R] is negative and \f[B]x\f[R] is
	-\f[B]0\f[R].
	+: Calculates \f[B]x\f[R] to the power of \f[B]y\f[R], even if
	+\f[B]y\f[R] is not an integer, and returns the result to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+It is an error if y is negative and x is 0.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round half away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero).
	-.TP
	+.PP
	\f[B]ceil(x, p)\f[R]
	-Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	+.PP
	+: Returns \f[B]x\f[R] rounded to \f[B]p\f[R] decimal places according to
	the rounding mode round away from
	\f[B]0\f[R] (https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero).
	-.TP
	+.PP
	\f[B]f(x)\f[R]
	-Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the factorial of the truncated absolute value of \f[B]x\f[R].
	+.PP
	\f[B]perm(n, k)\f[R]
	-Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the permutation of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]comb(n, k)\f[R]
	-Returns the combination of the truncated absolute value of \f[B]n\f[R]
	+.PP
	+: Returns the combination of the truncated absolute value of \f[B]n\f[R]
	of the truncated absolute value of \f[B]k\f[R], if \f[B]k <= n\f[R].
	If not, it returns \f[B]0\f[R].
	-.TP
	+.PP
	\f[B]l2(x)\f[R]
	-Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]2\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]l10(x)\f[R]
	-Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]10\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]log(x, b)\f[R]
	-Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the logarithm base \f[B]b\f[R] of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]cbrt(x)\f[R]
	-Returns the cube root of \f[B]x\f[R].
	-.TP
	+.PP
	+: Returns the cube root of \f[B]x\f[R].
	+.PP
	\f[B]root(x, n)\f[R]
	-Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and returns
	-the \f[B]r\f[R]th root of \f[B]x\f[R] to the current \f[B]scale\f[R].
	-.RS
	-.PP
	-If \f[B]r\f[R] is \f[B]0\f[R] or negative, this raises an error and
	-causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	-It also raises an error and causes bc(1) to reset if \f[B]r\f[R] is even
	-and \f[B]x\f[R] is negative.
	-.RE
	-.TP
	+.PP
	+: Calculates the truncated value of \f[B]n\f[R], \f[B]r\f[R], and
	+returns the \f[B]r\f[R]th root of \f[B]x\f[R] to the current
	+\f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+If r is 0 or negative, this raises an error and causes bc(1) to
	+reset (see the RESET section). It also raises an error and causes bc(1)
	+to reset if r is even and x is negative.
	+\f[R]
	+.fi
	+.PP
	\f[B]pi(p)\f[R]
	-Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns \f[B]pi\f[R] to \f[B]p\f[R] decimal places.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]t(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]a2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]sin(x)\f[R]
	-Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]s(x)\f[R].
	+: Returns the sine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of s(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]cos(x)\f[R]
	-Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	.PP
	-This is an alias of \f[B]c(x)\f[R].
	+: Returns the cosine of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of c(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]tan(x)\f[R]
	-Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	-.RS
	-.PP
	-If \f[B]x\f[R] is equal to \f[B]1\f[R] or \f[B]-1\f[R], this raises an
	-error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	.PP
	-This is an alias of \f[B]t(x)\f[R].
	+: Returns the tangent of \f[B]x\f[R], which is assumed to be in radians.
	+.IP
	+.nf
	+\f[C]
	+If x is equal to 1 or -1, this raises an error and causes bc(1)
	+to reset (see the RESET section).
	+
	+This is an alias of t(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan(x)\f[R]
	-Returns the arctangent of \f[B]x\f[R], in radians.
	-.RS
	.PP
	-This is an alias of \f[B]a(x)\f[R].
	+: Returns the arctangent of \f[B]x\f[R], in radians.
	+.IP
	+.nf
	+\f[C]
	+This is an alias of a(x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]atan2(y, x)\f[R]
	-Returns the arctangent of \f[B]y/x\f[R], in radians.
	+.PP
	+: Returns the arctangent of \f[B]y/x\f[R], in radians.
	If both \f[B]y\f[R] and \f[B]x\f[R] are equal to \f[B]0\f[R], it raises
	an error and causes bc(1) to reset (see the \f[B]RESET\f[R] section).
	Otherwise, if \f[B]x\f[R] is greater than \f[B]0\f[R], it returns
	\f[B]a(y/x)\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is greater than
	or equal to \f[B]0\f[R], it returns \f[B]a(y/x)+pi\f[R].
	If \f[B]x\f[R] is less than \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]a(y/x)-pi\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is greater than
	\f[B]0\f[R], it returns \f[B]pi/2\f[R].
	If \f[B]x\f[R] is equal to \f[B]0\f[R], and \f[B]y\f[R] is less than
	\f[B]0\f[R], it returns \f[B]-pi/2\f[R].
	-.RS
	-.PP
	-This function is the same as the \f[B]atan2()\f[R] function in many
	-programming languages.
	-.PP
	-This is an alias of \f[B]a2(y, x)\f[R].
	+.IP
	+.nf
	+\f[C]
	+This function is the same as the atan2() function in many programming
	+languages.
	+
	+This is an alias of a2(y, x).
	+
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	\f[B]r2d(x)\f[R]
	-Converts \f[B]x\f[R] from radians to degrees and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from radians to degrees and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]d2r(x)\f[R]
	-Converts \f[B]x\f[R] from degrees to radians and returns the result.
	-.RS
	.PP
	-This is a transcendental function (see the \f[I]Transcendental
	-Functions\f[R] subsection below).
	-.RE
	-.TP
	+: Converts \f[B]x\f[R] from degrees to radians and returns the result.
	+.IP
	+.nf
	+\f[C]
	+This is a transcendental function (see the Transcendental Functions
	+subsection below).
	+\f[R]
	+.fi
	+.PP
	\f[B]frand(p)\f[R]
	-Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	+.PP
	+: Generates a pseudo-random number between \f[B]0\f[R] (inclusive) and
	\f[B]1\f[R] (exclusive) with the number of decimal digits after the
	decimal point equal to the truncated absolute value of \f[B]p\f[R].
	If \f[B]p\f[R] is not \f[B]0\f[R], then calling this function will
	change the value of \f[B]seed\f[R].
	If \f[B]p\f[R] is \f[B]0\f[R], then \f[B]0\f[R] is returned, and
	\f[B]seed\f[R] is \f[I]not\f[R] changed.
	-.TP
	+.PP
	\f[B]ifrand(i, p)\f[R]
	-Generates a pseudo-random number that is between \f[B]0\f[R] (inclusive)
	-and the truncated absolute value of \f[B]i\f[R] (exclusive) with the
	-number of decimal digits after the decimal point equal to the truncated
	-absolute value of \f[B]p\f[R].
	+.PP
	+: Generates a pseudo-random number that is between \f[B]0\f[R]
	+(inclusive) and the truncated absolute value of \f[B]i\f[R] (exclusive)
	+with the number of decimal digits after the decimal point equal to the
	+truncated absolute value of \f[B]p\f[R].
	If the absolute value of \f[B]i\f[R] is greater than or equal to
	\f[B]2\f[R], and \f[B]p\f[R] is not \f[B]0\f[R], then calling this
	function will change the value of \f[B]seed\f[R]; otherwise, \f[B]0\f[R]
	is returned and \f[B]seed\f[R] is not changed.
	-.TP
	+.PP
	\f[B]srand(x)\f[R]
	-Returns \f[B]x\f[R] with its sign flipped with probability
	+.PP
	+: Returns \f[B]x\f[R] with its sign flipped with probability
	\f[B]0.5\f[R].
	In other words, it randomizes the sign of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]brand()\f[R]
	-Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	-.TP
	+.PP
	+: Returns a random boolean value (either \f[B]0\f[R] or \f[B]1\f[R]).
	+.PP
	\f[B]ubytes(x)\f[R]
	-Returns the numbers of unsigned integer bytes required to hold the
	+.PP
	+: Returns the numbers of unsigned integer bytes required to hold the
	truncated absolute value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]sbytes(x)\f[R]
	-Returns the numbers of signed, two\[cq]s-complement integer bytes
	+.PP
	+: Returns the numbers of signed, two\[aq]s-complement integer bytes
	required to hold the truncated value of \f[B]x\f[R].
	-.TP
	+.PP
	\f[B]hex(x)\f[R]
	-Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	+.PP
	+: Outputs the hexadecimal (base \f[B]16\f[R]) representation of
	\f[B]x\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary(x)\f[R]
	-Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the binary (base \f[B]2\f[R]) representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]output(x, b)\f[R]
	-Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	-.RS
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	+: Outputs the base \f[B]b\f[R] representation of \f[B]x\f[R].
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	+.PP
	\f[B]uint(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in as few power of two bytes as possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or is negative, an error message is
	-printed instead, but bc(1) is not reset (see the \f[B]RESET\f[R]
	-section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in as few power of two bytes as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or is negative, an error message is printed
	+instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in as few power of two bytes as
	-possible.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, an error message is printed instead,
	-but bc(1) is not reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in as few power of two bytes
	+as possible.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, an error message is printed instead, but bc(1)
	+is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uintn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]n\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into n bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]intn(x, n)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]n\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]n\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]n\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into n bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]1\f[R] byte, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 1 byte, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int8(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]1\f[R] byte.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]1\f[R] byte, an
	-error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]1\f[R] byte.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 1 byte, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]2\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 2 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int16(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]2\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]2\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]2\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 2 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]4\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 4 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int32(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]4\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]4\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]4\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 4 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]uint64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-an unsigned integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer, is negative, or cannot fit into
	-\f[B]8\f[R] bytes, an error message is printed instead, but bc(1) is not
	-reset (see the \f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as an unsigned integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer, is negative, or cannot fit into 8 bytes, an
	+error message is printed instead, but bc(1) is not reset (see the RESET
	+section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]int64(x)\f[R]
	-Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R] as
	-a signed, two\[cq]s-complement integer in \f[B]8\f[R] bytes.
	-Both outputs are split into bytes separated by spaces.
	-.RS
	.PP
	-If \f[B]x\f[R] is not an integer or cannot fit into \f[B]8\f[R] bytes,
	-an error message is printed instead, but bc(1) is not reset (see the
	-\f[B]RESET\f[R] section).
	+: Outputs the representation, in binary and hexadecimal, of \f[B]x\f[R]
	+as a signed, two\[aq]s-complement integer in \f[B]8\f[R] bytes.
	+Both outputs are split into bytes separated by spaces.
	+.IP
	+.nf
	+\f[C]
	+If x is not an integer or cannot fit into 8 bytes, an error message
	+is printed instead, but bc(1) is not reset (see the RESET section).
	+
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]hex_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in hexadecimal using \f[B]n\f[R]
	bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]binary_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in binary using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_uint(x, n)\f[R]
	-Outputs the representation of the truncated absolute value of
	+.PP
	+: Outputs the representation of the truncated absolute value of
	\f[B]x\f[R] as an unsigned integer in the current \f[B]obase\f[R] (see
	the \f[B]SYNTAX\f[R] section) using \f[B]n\f[R] bytes.
	Not all of the value will be output if \f[B]n\f[R] is too small.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	-.TP
	\f[B]output_byte(x, i)\f[R]
	-Outputs byte \f[B]i\f[R] of the truncated absolute value of \f[B]x\f[R],
	-where \f[B]0\f[R] is the least significant byte and \f[B]number_of_bytes
	-- 1\f[R] is the most significant byte.
	-.RS
	-.PP
	-This is a \f[B]void\f[R] function (see the \f[I]Void Functions\f[R]
	-subsection of the \f[B]FUNCTIONS\f[R] section).
	-.RE
	+.PP
	+: Outputs byte \f[B]i\f[R] of the truncated absolute value of
	+\f[B]x\f[R], where \f[B]0\f[R] is the least significant byte and
	+\f[B]number_of_bytes - 1\f[R] is the most significant byte.
	+.IP
	+.nf
	+\f[C]
	+This is a void function (see the Void Functions subsection of the
	+FUNCTIONS section).
	+\f[R]
	+.fi
	.SS Transcendental Functions
	.PP
	All transcendental functions can return slightly inaccurate results (up
	to 1 ULP (https://en.wikipedia.org/wiki/Unit_in_the_last_place)).
	This is unavoidable, and this
	article (https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT) explains
	why it is impossible and unnecessary to calculate exact results for the
	transcendental functions.
	.PP
	Because of the possible inaccuracy, I recommend that users call those
	functions with the precision (\f[B]scale\f[R]) set to at least 1 higher
	than is necessary.
	If exact results are \f[I]absolutely\f[R] required, users can double the
	precision (\f[B]scale\f[R]) and then truncate.
	.PP
	The transcendental functions in the standard math library are:
	.IP \[bu] 2
	\f[B]s(x)\f[R]
	.IP \[bu] 2
	\f[B]c(x)\f[R]
	.IP \[bu] 2
	\f[B]a(x)\f[R]
	.IP \[bu] 2
	\f[B]l(x)\f[R]
	.IP \[bu] 2
	\f[B]e(x)\f[R]
	.IP \[bu] 2
	\f[B]j(x, n)\f[R]
	.PP
	The transcendental functions in the extended math library are:
	.IP \[bu] 2
	\f[B]l2(x)\f[R]
	.IP \[bu] 2
	\f[B]l10(x)\f[R]
	.IP \[bu] 2
	\f[B]log(x, b)\f[R]
	.IP \[bu] 2
	\f[B]pi(p)\f[R]
	.IP \[bu] 2
	\f[B]t(x)\f[R]
	.IP \[bu] 2
	\f[B]a2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]sin(x)\f[R]
	.IP \[bu] 2
	\f[B]cos(x)\f[R]
	.IP \[bu] 2
	\f[B]tan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan(x)\f[R]
	.IP \[bu] 2
	\f[B]atan2(y, x)\f[R]
	.IP \[bu] 2
	\f[B]r2d(x)\f[R]
	.IP \[bu] 2
	\f[B]d2r(x)\f[R]
	.SH RESET
	.PP
	When bc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any functions that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all functions returned) is skipped.
	.PP
	Thus, when bc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.PP
	Note that this reset behavior is different from the GNU bc(1), which
	attempts to start executing the statement right after the one that
	caused an error.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This bc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	The actual values of \f[B]BC_LONG_BIT\f[R] and \f[B]BC_BASE_DIGS\f[R]
	can be queried with the \f[B]limits\f[R] statement.
	.PP
	In addition, this bc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bc(1):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]rand()\f[R]
	operand.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	The actual values can be queried with the \f[B]limits\f[R] statement.
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	bc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]POSIXLY_CORRECT\f[R]
	-If this variable exists (no matter the contents), bc(1) behaves as if
	+.PP
	+: If this variable exists (no matter the contents), bc(1) behaves as if
	the \f[B]-s\f[R] option was given.
	-.TP
	+.PP
	\f[B]BC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to bc(1).
	+.PP
	+: This is another way to give command-line arguments to bc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]BC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.
	-.RS
	-.PP
	-The code that parses \f[B]BC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some bc file.bc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]bc\[dq] file.bc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `bc' file.bc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]BC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some bc file.bc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]bc\[rs]\[dq] file.bc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]bc\[aq] file.bc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in BC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]BC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), bc(1) will output lines to that length,
	including the backslash (\f[B]\[rs]\f[R]).
	The default line length is \f[B]70\f[R].
	.SH EXIT STATUS
	.PP
	bc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]<<\f[R]), and right shift (\f[B]>>\f[R]) operators and their
	-corresponding assignment operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (\[rs]<\[rs]<), and right shift (\[rs]>\[rs]>)
	+operators and their corresponding assignment operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, using a token
	-where it is invalid, giving an invalid expression, giving an invalid
	-print statement, giving an invalid function definition, attempting to
	-assign to an expression that is not a named expression (see the
	-\f[I]Named Expressions\f[R] subsection of the \f[B]SYNTAX\f[R] section),
	-giving an invalid \f[B]auto\f[R] list, having a duplicate
	-\f[B]auto\f[R]/function parameter, failing to find the end of a code
	-block, attempting to return a value from a \f[B]void\f[R] function,
	-attempting to use a variable as a reference, and using any extensions
	-when the option \f[B]-s\f[R] or any equivalents were given.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, using a token where it is invalid,
	+giving an invalid expression, giving an invalid print statement, giving an
	+invalid function definition, attempting to assign to an expression that is
	+not a named expression (see the Named Expressions subsection of the
	+SYNTAX section), giving an invalid auto list, having a duplicate
	+auto/function parameter, failing to find the end of a code block,
	+attempting to return a value from a void function, attempting to use a
	+variable as a reference, and using any extensions when the option -s or
	+any equivalents were given.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, passing the wrong number of
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	-attempting to use a \f[B]void\f[R] function call as a value in an
	-expression.
	-.RE
	-.TP
	+attempting to use a void function call as a value in an expression.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (bc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (bc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, bc(1)
	always exits and returns \f[B]4\f[R], no matter what mode bc(1) is in.
	.PP
	The other statuses will only be returned when bc(1) is not in
	interactive mode (see the \f[B]INTERACTIVE MODE\f[R] section), since
	bc(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]--interactive\f[R] option.
	.PP
	These exit statuses allow bc(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]--interactive\f[R] option.
	.SH INTERACTIVE MODE
	.PP
	Per the
	standard (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	bc(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]--interactive\f[R] option can turn it on in other cases.
	.PP
	In interactive mode, bc(1) attempts to recover from errors (see the
	\f[B]RESET\f[R] section), and in normal execution, flushes
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, bc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, bc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause bc(1) to stop execution of the
	current input.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If bc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If bc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to bc(1) as it is
	executing a file, it can seem as though bc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause bc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when bc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause bc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	bc(1) supports interactive command-line editing.
	If bc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This bc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGES\f[R].
	.SH SEE ALSO
	.PP
	dc(1)
	.SH STANDARDS
	.PP
	bc(1) is compliant with the IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	The flags \f[B]-efghiqsvVw\f[R], all long options, and the extensions
	noted above are extensions to that specification.
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	.PP
	This bc(1) supports error messages for different locales, and thus, it
	supports \f[B]LC_MESSAGES\f[R].
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/bc/P.1.md b/contrib/bc/manuals/bc/P.1.md
	index 489af865475c..4434f7c803a2 100644
	--- a/contrib/bc/manuals/bc/P.1.md
	+++ b/contrib/bc/manuals/bc/P.1.md
	@@ -1,1698 +1,1704 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# NAME

	bc - arbitrary-precision decimal arithmetic language and calculator

	# SYNOPSIS

	-bc [-ghilPqsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+bc [-ghilPqRsvVw] [-\-global-stacks] [-\-help] [-\-interactive] [-\-mathlib] [-\-no-prompt] [-\-no-read-prompt] [-\-quiet] [-\-standard] [-\-warn] [-\-version] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	bc(1) is an interactive processor for a language first standardized in 1991 by
	POSIX. (The current standard is [here][1].) The language provides unlimited
	precision decimal arithmetic and is somewhat C-like, but there are differences.
	Such differences will be noted in this document.

	After parsing and handling options, this bc(1) reads any files given on the
	command line and executes them before reading from stdin.

	This bc(1) is a drop-in replacement for any bc(1), including (and
	especially) the GNU bc(1). It also has many extensions and extra features beyond
	other implementations.

	# OPTIONS

	The following are the options that bc(1) accepts.

	-g, -\-global-stacks

	: Turns the globals ibase, obase, scale, and seed into stacks.

	This has the effect that a copy of the current value of all four are pushed
	onto a stack for every function call, as well as popped when every function
	returns. This means that functions can assign to any and all of those
	globals without worrying that the change will affect other functions.
	Thus, a hypothetical function named output(x,b) that simply printed
	x in base b could be written like this:

	define void output(x, b) {
	obase=b
	x
	}

	instead of like this:

	define void output(x, b) {
	auto c
	c=obase
	obase=b
	x
	obase=c
	}

	This makes writing functions much easier.

	(Note: the function output(x,b) exists in the extended math library.
	See the LIBRARY section.)

	However, since using this flag means that functions cannot set ibase,
	obase, scale, or seed globally, functions that are made to do so
	cannot work anymore. There are two possible use cases for that, and each has
	a solution.

	First, if a function is called on startup to turn bc(1) into a number
	converter, it is possible to replace that capability with various shell
	aliases. Examples:

	alias d2o="bc -e ibase=A -e obase=8"
	alias h2b="bc -e ibase=G -e obase=2"

	Second, if the purpose of a function is to set ibase, obase,
	scale, or seed globally for any other purpose, it could be split
	into one to four functions (based on how many globals it sets) and each of
	those functions could return the desired value for a global.

	For functions that set seed, the value assigned to seed is not
	propagated to parent functions. This means that the sequence of
	pseudo-random numbers that they see will not be the same sequence of
	pseudo-random numbers that any parent sees. This is only the case once
	seed has been set.

	If a function desires to not affect the sequence of pseudo-random numbers
	of its parents, but wants to use the same seed, it can use the following
	line:

	seed = seed

	If the behavior of this option is desired for every run of bc(1), then users
	could make sure to define BC_ENV_ARGS and include this option (see the
	ENVIRONMENT VARIABLES section for more details).

	If -s, -w, or any equivalents are used, this option is ignored.

	This is a non-portable extension.

	-h, -\-help

	: Prints a usage message and quits.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-l, -\-mathlib

	: Sets scale (see the SYNTAX section) to 20 and loads the included
	math library and the extended math library before running any code,
	including any expressions or files specified on the command line.

	To learn what is in the libraries, see the LIBRARY section.

	-P, -\-no-prompt

	: This option is a no-op.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Because bc(1) was built without support for prompts, this option is a no-op.
	+
	+ This is a non-portable extension.
	+
	-q, -\-quiet

	: This option is for compatibility with the [GNU bc(1)][2]; it is a no-op.
	Without this option, GNU bc(1) prints a copyright header. This bc(1) only
	prints the copyright header if one or more of the -v, -V, or
	-\-version options are given.

	This is a non-portable extension.

	-s, -\-standard

	: Process exactly the language defined by the [standard][1] and error if any
	extensions are used.

	This is a non-portable extension.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	This is a non-portable extension.

	-w, -\-warn

	: Like -s and -\-standard, except that warnings (and not errors) are
	printed for non-standard extensions and execution continues normally.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in BC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in BC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, bc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, bc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in bc <file> >&-, it will quit with an error. This
	is done so that bc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other bc(1) implementations, this bc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in bc <file> 2>&-, it will quit with an error. This
	is done so that bc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other bc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	The syntax for bc(1) programs is mostly C-like, with some differences. This
	bc(1) follows the [POSIX standard][1], which is a much more thorough resource
	for the language this bc(1) accepts. This section is meant to be a summary and a
	listing of all the extensions to the standard.

	In the sections below, E means expression, S means statement, and I
	means identifier.

	Identifiers (I) start with a lowercase letter and can be followed by any
	number (up to BC_NAME_MAX-1) of lowercase letters (a-z), digits
	(0-9), and underscores (\_). The regex is \[a-z\]\[a-z0-9\_\]\*.
	Identifiers with more than one character (letter) are a
	non-portable extension.

	ibase is a global variable determining how to interpret constant numbers. It
	is the "input" base, or the number base used for interpreting input numbers.
	ibase is initially 10. If the -s (-\-standard) and -w
	(-\-warn) flags were not given on the command line, the max allowable value
	for ibase is 36. Otherwise, it is 16. The min allowable value for
	ibase is 2. The max allowable value for ibase can be queried in
	bc(1) programs with the maxibase() built-in function.

	obase is a global variable determining how to output results. It is the
	"output" base, or the number base used for outputting numbers. obase is
	initially 10. The max allowable value for obase is BC_BASE_MAX and
	can be queried in bc(1) programs with the maxobase() built-in function. The
	min allowable value for obase is 0. If obase is 0, values are
	output in scientific notation, and if obase is 1, values are output in
	engineering notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a global variable that
	sets the precision of any operations, with exceptions. scale is initially
	0. scale cannot be negative. The max allowable value for scale is
	BC_SCALE_MAX and can be queried in bc(1) programs with the maxscale()
	built-in function.

	bc(1) has both global variables and local variables. All local
	variables are local to the function; they are parameters or are introduced in
	the auto list of a function (see the FUNCTIONS section). If a variable
	is accessed which is not a parameter or in the auto list, it is assumed to
	be global. If a parent function has a local variable version of a variable
	that a child function considers global, the value of that global variable in
	the child function is the value of the variable in the parent function, not the
	value of the actual global variable.

	All of the above applies to arrays as well.

	The value of a statement that is an expression (i.e., any of the named
	expressions or operands) is printed unless the lowest precedence operator is an
	assignment operator and the expression is notsurrounded by parentheses.

	The value that is printed is also assigned to the special variable last. A
	single dot (.) may also be used as a synonym for last. These are
	non-portable extensions.

	Either semicolons or newlines may separate statements.

	## Comments

	There are two kinds of comments:

	1. Block comments are enclosed in /\* and *\/**.
	2. Line comments go from # until, and not including, the next newline. This
	is a non-portable extension.

	## Named Expressions

	The following are named expressions in bc(1):

	1. Variables: I
	2. Array Elements: I[E]
	3. ibase
	4. obase
	5. scale
	6. seed
	7. last or a single dot (.)

	Numbers 6 and 7 are non-portable extensions.

	The meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is assigned to seed and used again, the
	pseudo-random number generator is guaranteed to produce the same sequence of
	pseudo-random numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if
	seed is queried again immediately. However, if seed does return a
	different value, both values, when assigned to seed, are guaranteed to
	produce the same sequence of pseudo-random numbers. This means that certain
	values assigned to seed will not produce unique sequences of pseudo-random
	numbers. The value of seed will change after any use of the rand() and
	irand(E) operands (see the Operands subsection below), except if the
	parameter passed to irand(E) is 0, 1, or negative.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	Variables and arrays do not interfere; users can have arrays named the same as
	variables. This also applies to functions (see the FUNCTIONS section), so a
	user can have a variable, array, and function that all have the same name, and
	they will not shadow each other, whether inside of functions or not.

	Named expressions are required as the operand of increment/decrement
	operators and as the left side of assignment operators (see the Operators
	subsection).

	## Operands

	The following are valid operands in bc(1):

	1. Numbers (see the Numbers subsection below).
	2. Array indices (I[E]).
	3. (E): The value of E (used to change precedence).
	4. sqrt(E): The square root of E. E must be non-negative.
	5. length(E): The number of significant decimal digits in E.
	6. length(I[]): The number of elements in the array I. This is a
	non-portable extension.
	7. scale(E): The scale of E.
	8. abs(E): The absolute value of E. This is a **non-portable
	extension**.
	9. I(), I(E), I(E, E), and so on, where I is an identifier for
	a non-void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.
	10. read(): Reads a line from stdin and uses that as an expression. The
	result of that expression is the result of the read() operand. This is a
	non-portable extension.
	11. maxibase(): The max allowable ibase. This is a **non-portable
	extension**.
	12. maxobase(): The max allowable obase. This is a **non-portable
	extension**.
	13. maxscale(): The max allowable scale. This is a **non-portable
	extension**.
	14. rand(): A pseudo-random integer between 0 (inclusive) and
	BC_RAND_MAX (inclusive). Using this operand will change the value of
	seed. This is a non-portable extension.
	15. irand(E): A pseudo-random integer between 0 (inclusive) and the
	value of E (exclusive). If E is negative or is a non-integer
	(E's scale is not 0), an error is raised, and bc(1) resets (see
	the RESET section) while seed remains unchanged. If E is larger
	than BC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	BC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this operand is unbounded. Using this operand will
	change the value of seed, unless the value of E is 0 or 1.
	In that case, 0 is returned, and seed is not changed. This is a
	non-portable extension.
	16. maxrand(): The max integer returned by rand(). This is a
	non-portable extension.

	The integers generated by rand() and irand(E) are guaranteed to be as
	unbiased as possible, subject to the limitations of the pseudo-random number
	generator.

	Note: The values returned by the pseudo-random number generator with
	rand() and irand(E) are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from bc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	## Numbers

	Numbers are strings made up of digits, uppercase letters, and at most 1
	period for a radix. Numbers can have up to BC_NUM_MAX digits. Uppercase
	letters are equal to 9 + their position in the alphabet (i.e., A equals
	10, or 9+1). If a digit or letter makes no sense with the current value
	of ibase, they are set to the value of the highest valid digit in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and Z alone always equals decimal
	35.

	In addition, bc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e-3 is equal to 0.0042890.

	Using scientific notation is an error or warning if the -s or -w,
	respectively, command-line options (or equivalents) are given.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and bc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if bc(1) is given the
	number string 10e-4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	## Operators

	The following arithmetic and logical operators can be used. They are listed in
	order of decreasing precedence. Operators in the same group have the same
	precedence.

	++ -\-

	: Type: Prefix and Postfix

	Associativity: None

	Description: increment, decrement

	- !

	: Type: Prefix

	Associativity: None

	Description: negation, boolean not

	\$

	: Type: Postfix

	Associativity: None

	Description: truncation

	\@

	: Type: Binary

	Associativity: Right

	Description: set precision

	\^

	: Type: Binary

	Associativity: Right

	Description: power

	\* / %

	: Type: Binary

	Associativity: Left

	Description: multiply, divide, modulus

	+ -

	: Type: Binary

	Associativity: Left

	Description: add, subtract

	\<\< \>\>

	: Type: Binary

	Associativity: Left

	Description: shift left, shift right

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: Type: Binary

	Associativity: Right

	Description: assignment

	== \<= \>= != \< \>

	: Type: Binary

	Associativity: Left

	Description: relational

	&&

	: Type: Binary

	Associativity: Left

	Description: boolean and

	\|\|

	: Type: Binary

	Associativity: Left

	Description: boolean or

	The operators will be described in more detail below.

	++ -\-

	: The prefix and postfix increment and decrement operators behave
	exactly like they would in C. They require a named expression (see the
	Named Expressions subsection) as an operand.

	The prefix versions of these operators are more efficient; use them where
	possible.

	-

	: The negation operator returns 0 if a user attempts to negate any
	expression with the value 0. Otherwise, a copy of the expression with
	its sign flipped is returned.

	!

	: The boolean not operator returns 1 if the expression is 0, or
	0 otherwise.

	This is a non-portable extension.

	\$

	: The truncation operator returns a copy of the given expression with all
	of its scale removed.

	This is a non-portable extension.

	\@

	: The set precision operator takes two expressions and returns a copy of
	the first with its scale equal to the value of the second expression. That
	could either mean that the number is returned without change (if the
	scale of the first expression matches the value of the second
	expression), extended (if it is less), or truncated (if it is more).

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\^

	: The power operator (not the exclusive or operator, as it would be in
	C) takes two expressions and raises the first to the power of the value of
	the second. The scale of the result is equal to scale.

	The second expression must be an integer (no scale), and if it is
	negative, the first value must be non-zero.

	\*

	: The multiply operator takes two expressions, multiplies them, and
	returns the product. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result is
	equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The divide operator takes two expressions, divides them, and returns the
	quotient. The scale of the result shall be the value of scale.

	The second expression must be non-zero.

	%

	: The modulus operator takes two expressions, a and b, and
	evaluates them by 1) Computing a/b to current scale and 2) Using the
	result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The second expression must be non-zero.

	+

	: The add operator takes two expressions, a and b, and returns the
	sum, with a scale equal to the max of the scales of a and b.

	-

	: The subtract operator takes two expressions, a and b, and
	returns the difference, with a scale equal to the max of the scales of
	a and b.

	\<\<

	: The left shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the right.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	\>\>

	: The right shift operator takes two expressions, a and b, and
	returns a copy of the value of a with its decimal point moved b
	places to the left.

	The second expression must be an integer (no scale) and non-negative.

	This is a non-portable extension.

	= \<\<= \>\>= += -= *\= /= %= \^= \@=**

	: The assignment operators take two expressions, a and b where
	a is a named expression (see the Named Expressions subsection).

	For =, b is copied and the result is assigned to a. For all
	others, a and b are applied as operands to the corresponding
	arithmetic operator and the result is assigned to a.

	The assignment operators that correspond to operators that are
	extensions are themselves non-portable extensions.

	== \<= \>= != \< \>

	: The relational operators compare two expressions, a and b, and
	if the relation holds, according to C language semantics, the result is
	1. Otherwise, it is 0.

	Note that unlike in C, these operators have a lower precedence than the
	assignment operators, which means that a=b\>c is interpreted as
	(a=b)\>c.

	Also, unlike the [standard][1] requires, these operators can appear anywhere
	any other expressions can be used. This allowance is a
	non-portable extension.

	&&

	: The boolean and operator takes two expressions and returns 1 if both
	expressions are non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	\|\|

	: The boolean or operator takes two expressions and returns 1 if one
	of the expressions is non-zero, 0 otherwise.

	This is not a short-circuit operator.

	This is a non-portable extension.

	## Statements

	The following items are statements:

	1. E
	2. { S ; ... ; S }
	3. if ( E ) S
	4. if ( E ) S else S
	5. while ( E ) S
	6. for ( E ; E ; E ) S
	7. An empty statement
	8. break
	9. continue
	10. quit
	11. halt
	12. limits
	13. A string of characters, enclosed in double quotes
	14. print E , ... , E
	15. I(), I(E), I(E, E), and so on, where I is an identifier for
	a void function (see the Void Functions subsection of the
	FUNCTIONS section). The E argument(s) may also be arrays of the form
	I[], which will automatically be turned into array references (see the
	Array References subsection of the FUNCTIONS section) if the
	corresponding parameter in the function definition is an array reference.

	Numbers 4, 9, 11, 12, 14, and 15 are non-portable extensions.

	Also, as a non-portable extension, any or all of the expressions in the
	header of a for loop may be omitted. If the condition (second expression) is
	omitted, it is assumed to be a constant 1.

	The break statement causes a loop to stop iterating and resume execution
	immediately following a loop. This is only allowed in loops.

	The continue statement causes a loop iteration to stop early and returns to
	the start of the loop, including testing the loop condition. This is only
	allowed in loops.

	The if else statement does the same thing as in C.

	The quit statement causes bc(1) to quit, even if it is on a branch that will
	not be executed (it is a compile-time command).

	The halt statement causes bc(1) to quit, if it is executed. (Unlike quit
	if it is on a branch of an if statement that is not executed, bc(1) does not
	quit.)

	The limits statement prints the limits that this bc(1) is subject to. This
	is like the quit statement in that it is a compile-time command.

	An expression by itself is evaluated and printed, followed by a newline.

	Both scientific notation and engineering notation are available for printing the
	results of expressions. Scientific notation is activated by assigning 0 to
	obase, and engineering notation is activated by assigning 1 to
	obase. To deactivate them, just assign a different value to obase.

	Scientific notation and engineering notation are disabled if bc(1) is run with
	either the -s or -w command-line options (or equivalents).

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	## Print Statement

	The "expressions" in a print statement may also be strings. If they are, there
	are backslash escape sequences that are interpreted specially. What those
	sequences are, and what they cause to be printed, are shown below:

	-------- -------
	\\a \\a
	\\b \\b
	\\\\ \\
	\\e \\
	\\f \\f
	\\n \\n
	\\q "
	\\r \\r
	\\t \\t
	-------- -------

	Any other character following a backslash causes the backslash and character to
	be printed as-is.

	Any non-string expression in a print statement shall be assigned to last,
	like any other expression that is printed.

	## Order of Evaluation

	All expressions in a statment are evaluated left to right, except as necessary
	to maintain order of operations. This means, for example, assuming that i is
	equal to 0, in the expression

	a[i++] = i++

	the first (or 0th) element of a is set to 1, and i is equal to 2
	at the end of the expression.

	This includes function arguments. Thus, assuming i is equal to 0, this
	means that in the expression

	x(i++, i++)

	the first argument passed to x() is 0, and the second argument is 1,
	while i is equal to 2 before the function starts executing.

	# FUNCTIONS

	Function definitions are as follows:

	```
	define I(I,...,I){
	auto I,...,I
	S;...;S
	return(E)
	}
	```

	Any I in the parameter list or auto list may be replaced with I[] to
	make a parameter or auto var an array, and any I in the parameter list
	may be replaced with *\I[]** to make a parameter an array reference. Callers
	of functions that take array references should not put an asterisk in the call;
	they must be called with just I[] like normal array parameters and will be
	automatically converted into references.

	As a non-portable extension, the opening brace of a define statement may
	appear on the next line.

	As a non-portable extension, the return statement may also be in one of the
	following forms:

	1. return
	2. return ( )
	3. return E

	The first two, or not specifying a return statement, is equivalent to
	return (0), unless the function is a void function (see the *Void
	Functions* subsection below).

	## Void Functions

	Functions can also be void functions, defined as follows:

	```
	define void I(I,...,I){
	auto I,...,I
	S;...;S
	return
	}
	```

	They can only be used as standalone expressions, where such an expression would
	be printed alone, except in a print statement.

	Void functions can only use the first two return statements listed above.
	They can also omit the return statement entirely.

	The word "void" is not treated as a keyword; it is still possible to have
	variables, arrays, and functions named void. The word "void" is only
	treated specially right after the define keyword.

	This is a non-portable extension.

	## Array References

	For any array in the parameter list, if the array is declared in the form

	```
	*I[]
	```

	it is a reference. Any changes to the array in the function are reflected,
	when the function returns, to the array that was passed in.

	Other than this, all function arguments are passed by value.

	This is a non-portable extension.

	# LIBRARY

	All of the functions below, including the functions in the extended math
	library (see the Extended Library subsection below), are available when the
	-l or -\-mathlib command-line flags are given, except that the extended
	math library is not available when the -s option, the -w option, or
	equivalents are given.

	## Standard Library

	The [standard][1] defines the following functions for the math library:

	s(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	c(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a(x)

	: Returns the arctangent of x, in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l(x)

	: Returns the natural logarithm of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	e(x)

	: Returns the mathematical constant e raised to the power of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	j(x, n)

	: Returns the bessel integer order n (truncated) of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	## Extended Library

	The extended library is not loaded when the -s/-\-standard or
	-w/-\-warn options are given since they are not part of the library
	defined by the [standard][1].

	The extended library is a non-portable extension.

	p(x, y)

	: Calculates x to the power of y, even if y is not an integer, and
	returns the result to the current scale.

	It is an error if y is negative and x is 0.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round half away from 0][3].

	ceil(x, p)

	: Returns x rounded to p decimal places according to the rounding mode
	[round away from 0][6].

	f(x)

	: Returns the factorial of the truncated absolute value of x.

	perm(n, k)

	: Returns the permutation of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	comb(n, k)

	: Returns the combination of the truncated absolute value of n of the
	truncated absolute value of k, if k \<= n. If not, it returns 0.

	l2(x)

	: Returns the logarithm base 2 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	l10(x)

	: Returns the logarithm base 10 of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	log(x, b)

	: Returns the logarithm base b of x.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cbrt(x)

	: Returns the cube root of x.

	root(x, n)

	: Calculates the truncated value of n, r, and returns the rth root
	of x to the current scale.

	If r is 0 or negative, this raises an error and causes bc(1) to
	reset (see the RESET section). It also raises an error and causes bc(1)
	to reset if r is even and x is negative.

	pi(p)

	: Returns pi to p decimal places.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	t(x)

	: Returns the tangent of x, which is assumed to be in radians.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	a2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	sin(x)

	: Returns the sine of x, which is assumed to be in radians.

	This is an alias of s(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	cos(x)

	: Returns the cosine of x, which is assumed to be in radians.

	This is an alias of c(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	tan(x)

	: Returns the tangent of x, which is assumed to be in radians.

	If x is equal to 1 or -1, this raises an error and causes bc(1)
	to reset (see the RESET section).

	This is an alias of t(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan(x)

	: Returns the arctangent of x, in radians.

	This is an alias of a(x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	atan2(y, x)

	: Returns the arctangent of y/x, in radians. If both y and x are
	equal to 0, it raises an error and causes bc(1) to reset (see the
	RESET section). Otherwise, if x is greater than 0, it returns
	a(y/x). If x is less than 0, and y is greater than or equal
	to 0, it returns a(y/x)+pi. If x is less than 0, and y
	is less than 0, it returns a(y/x)-pi. If x is equal to 0,
	and y is greater than 0, it returns pi/2. If x is equal to
	0, and y is less than 0, it returns -pi/2.

	This function is the same as the atan2() function in many programming
	languages.

	This is an alias of a2(y, x).

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	r2d(x)

	: Converts x from radians to degrees and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	d2r(x)

	: Converts x from degrees to radians and returns the result.

	This is a transcendental function (see the Transcendental Functions
	subsection below).

	frand(p)

	: Generates a pseudo-random number between 0 (inclusive) and 1
	(exclusive) with the number of decimal digits after the decimal point equal
	to the truncated absolute value of p. If p is not 0, then
	calling this function will change the value of seed. If p is 0,
	then 0 is returned, and seed is not changed.

	ifrand(i, p)

	: Generates a pseudo-random number that is between 0 (inclusive) and the
	truncated absolute value of i (exclusive) with the number of decimal
	digits after the decimal point equal to the truncated absolute value of
	p. If the absolute value of i is greater than or equal to 2, and
	p is not 0, then calling this function will change the value of
	seed; otherwise, 0 is returned and seed is not changed.

	srand(x)

	: Returns x with its sign flipped with probability 0.5. In other
	words, it randomizes the sign of x.

	brand()

	: Returns a random boolean value (either 0 or 1).

	ubytes(x)

	: Returns the numbers of unsigned integer bytes required to hold the truncated
	absolute value of x.

	sbytes(x)

	: Returns the numbers of signed, two's-complement integer bytes required to
	hold the truncated value of x.

	hex(x)

	: Outputs the hexadecimal (base 16) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary(x)

	: Outputs the binary (base 2) representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output(x, b)

	: Outputs the base b representation of x.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in as few power of two bytes as possible. Both outputs are
	split into bytes separated by spaces.

	If x is not an integer or is negative, an error message is printed
	instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in as few power of two bytes as possible. Both
	outputs are split into bytes separated by spaces.

	If x is not an integer, an error message is printed instead, but bc(1)
	is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uintn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in n bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into n bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	intn(x, n)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in n bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into n bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint8(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 1 byte. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 1 byte, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int8(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 1 byte. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 1 byte, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint16(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 2 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 2 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int16(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 2 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 2 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint32(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 4 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 4 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int32(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 4 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 4 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	uint64(x)

	: Outputs the representation, in binary and hexadecimal, of x as an
	unsigned integer in 8 bytes. Both outputs are split into bytes separated
	by spaces.

	If x is not an integer, is negative, or cannot fit into 8 bytes, an
	error message is printed instead, but bc(1) is not reset (see the RESET
	section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	int64(x)

	: Outputs the representation, in binary and hexadecimal, of x as a signed,
	two's-complement integer in 8 bytes. Both outputs are split into bytes
	separated by spaces.

	If x is not an integer or cannot fit into 8 bytes, an error message
	is printed instead, but bc(1) is not reset (see the RESET section).

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	hex_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in hexadecimal using n bytes. Not all of the value will
	be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	binary_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in binary using n bytes. Not all of the value will be
	output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_uint(x, n)

	: Outputs the representation of the truncated absolute value of x as an
	unsigned integer in the current obase (see the SYNTAX section) using
	n bytes. Not all of the value will be output if n is too small.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	output_byte(x, i)

	: Outputs byte i of the truncated absolute value of x, where 0 is
	the least significant byte and number_of_bytes - 1 is the most
	significant byte.

	This is a void function (see the Void Functions subsection of the
	FUNCTIONS section).

	## Transcendental Functions

	All transcendental functions can return slightly inaccurate results (up to 1
	[ULP][4]). This is unavoidable, and [this article][5] explains why it is
	impossible and unnecessary to calculate exact results for the transcendental
	functions.

	Because of the possible inaccuracy, I recommend that users call those functions
	with the precision (scale) set to at least 1 higher than is necessary. If
	exact results are absolutely required, users can double the precision
	(scale) and then truncate.

	The transcendental functions in the standard math library are:

	* s(x)
	* c(x)
	* a(x)
	* l(x)
	* e(x)
	* j(x, n)

	The transcendental functions in the extended math library are:

	* l2(x)
	* l10(x)
	* log(x, b)
	* pi(p)
	* t(x)
	* a2(y, x)
	* sin(x)
	* cos(x)
	* tan(x)
	* atan(x)
	* atan2(y, x)
	* r2d(x)
	* d2r(x)

	# RESET

	When bc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any functions that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	functions returned) is skipped.

	Thus, when bc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	Note that this reset behavior is different from the GNU bc(1), which attempts to
	start executing the statement right after the one that caused an error.

	# PERFORMANCE

	Most bc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This bc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where BC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where BC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	BC_BASE_DIGS.

	The actual values of BC_LONG_BIT and BC_BASE_DIGS can be queried with
	the limits statement.

	In addition, this bc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of BC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on bc(1):

	BC_LONG_BIT

	: The number of bits in the long type in the environment where bc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	BC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on BC_LONG_BIT.

	BC_BASE_POW

	: The max decimal number that each large integer can store (see
	BC_BASE_DIGS) plus 1. Depends on BC_BASE_DIGS.

	BC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on BC_LONG_BIT.

	BC_BASE_MAX

	: The maximum output base. Set at BC_BASE_POW.

	BC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	BC_SCALE_MAX

	: The maximum scale. Set at BC_OVERFLOW_MAX-1.

	BC_STRING_MAX

	: The maximum length of strings. Set at BC_OVERFLOW_MAX-1.

	BC_NAME_MAX

	: The maximum length of identifiers. Set at BC_OVERFLOW_MAX-1.

	BC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at BC_OVERFLOW_MAX-1.

	BC_RAND_MAX

	: The maximum integer (inclusive) returned by the rand() operand. Set at
	2\^BC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	BC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	The actual values can be queried with the limits statement.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	bc(1) recognizes the following environment variables:

	POSIXLY_CORRECT

	: If this variable exists (no matter the contents), bc(1) behaves as if
	the -s option was given.

	BC_ENV_ARGS

	: This is another way to give command-line arguments to bc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in BC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time bc(1) runs.

	The code that parses BC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some bc file.bc" will be correctly parsed, but the string
	"/home/gavin/some \"bc\" file.bc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'bc' file.bc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in BC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	BC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), bc(1) will output
	lines to that length, including the backslash (\\). The default line
	length is 70.

	# EXIT STATUS

	bc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (\<\<), and right shift (\>\>)
	operators and their corresponding assignment operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, using a token where it is invalid,
	giving an invalid expression, giving an invalid print statement, giving an
	invalid function definition, attempting to assign to an expression that is
	not a named expression (see the Named Expressions subsection of the
	SYNTAX section), giving an invalid auto list, having a duplicate
	auto/function parameter, failing to find the end of a code block,
	attempting to return a value from a void function, attempting to use a
	variable as a reference, and using any extensions when the option -s or
	any equivalents were given.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, passing the wrong number of
	arguments to functions, attempting to call an undefined function, and
	attempting to use a void function call as a value in an expression.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (bc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, bc(1) always exits
	and returns 4, no matter what mode bc(1) is in.

	The other statuses will only be returned when bc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since bc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	These exit statuses allow bc(1) to be used in shell scripting with error
	checking, and its normal behavior can be forced by using the -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Per the [standard][1], bc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, bc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, bc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause bc(1) to stop execution of the current input. If
	bc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If bc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If bc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to bc(1) as it is executing a file, it
	can seem as though bc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with bc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause bc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when bc(1) is in TTY mode, a SIGHUP will cause bc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	bc(1) supports interactive command-line editing. If bc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This bc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGES.

	# SEE ALSO

	dc(1)

	# STANDARDS

	bc(1) is compliant with the [IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1]
	specification. The flags -efghiqsvVw, all long options, and the extensions
	noted above are extensions to that specification.

	Note that the specification explicitly says that bc(1) only accepts numbers that
	use a period (.) as a radix point, regardless of the value of
	LC_NUMERIC.

	This bc(1) supports error messages for different locales, and thus, it supports
	LC_MESSAGES.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHORS

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://en.wikipedia.org/wiki/Rounding#Round_half_away_from_zero
	[4]: https://en.wikipedia.org/wiki/Unit_in_the_last_place
	[5]: https://people.eecs.berkeley.edu/~wkahan/LOG10HAF.TXT
	[6]: https://en.wikipedia.org/wiki/Rounding#Rounding_away_from_zero
	diff --git a/contrib/bc/manuals/bcl.3 b/contrib/bc/manuals/bcl.3
	index d83a2d3ad2e5..550ea118431e 100644
	--- a/contrib/bc/manuals/bcl.3
	+++ b/contrib/bc/manuals/bcl.3
	@@ -1,1365 +1,1446 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "BCL" "3" "March 2021" "Gavin D. Howard" "Libraries Manual"
	+.TH "BCL" "3" "April 2021" "Gavin D. Howard" "Libraries Manual"
	.SH NAME
	.PP
	bcl - library of arbitrary precision decimal arithmetic
	.SH SYNOPSIS
	.SS Use
	.PP
	\f[I]#include <bcl.h>\f[R]
	.PP
	Link with \f[I]-lbcl\f[R].
	.SS Signals
	.PP
	This procedure will allow clients to use signals to interrupt
	computations running in bcl(3).
	.PP
	-\f[B]void bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]void bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]bool bcl_running(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]bool bcl_running(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.SS Setup
	.PP
	These items allow clients to set up bcl(3).
	.PP
	-\f[B]BclError bcl_init(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_init(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]void bcl_free(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]void bcl_free(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]bool bcl_abortOnFatalError(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]bool bcl_abortOnFatalError(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]void bcl_setAbortOnFatalError(bool\f[R] \f[I]abrt\f[R]\f[B]);\f[R]
	+\f[B]void bcl_setAbortOnFatalError(bool\f[R] \f[I]abrt\f[R]);
	.PP
	-\f[B]void bcl_gc(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]void bcl_gc(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.SS Contexts
	.PP
	These items will allow clients to handle contexts, which are isolated
	from each other.
	This allows more than one client to use bcl(3) in the same program.
	.PP
	\f[B]struct BclCtxt;\f[R]
	.PP
	\f[B]typedef struct BclCtxt* BclContext;\f[R]
	.PP
	-\f[B]BclContext bcl_ctxt_create(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclContext bcl_ctxt_create(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]void bcl_ctxt_free(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]void bcl_ctxt_free(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]BclError bcl_pushContext(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_pushContext(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]void bcl_popContext(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]void bcl_popContext(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]BclContext bcl_context(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclContext bcl_context(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]void bcl_ctxt_freeNums(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]void bcl_ctxt_freeNums(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]size_t bcl_ctxt_scale(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]size_t bcl_ctxt_scale(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]void bcl_ctxt_setScale(BclContext\f[R] \f[I]ctxt\f[R]\f[B],
	-size_t\f[R] \f[I]scale\f[R]\f[B]);\f[R]
	+\f[B]void bcl_ctxt_setScale(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]scale\f[R]);
	.PP
	-\f[B]size_t bcl_ctxt_ibase(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]size_t bcl_ctxt_ibase(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]void bcl_ctxt_setIbase(BclContext\f[R] \f[I]ctxt\f[R]\f[B],
	-size_t\f[R] \f[I]ibase\f[R]\f[B]);\f[R]
	+\f[B]void bcl_ctxt_setIbase(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]ibase\f[R]);
	.PP
	-\f[B]size_t bcl_ctxt_obase(BclContext\f[R] \f[I]ctxt\f[R]\f[B]);\f[R]
	+\f[B]size_t bcl_ctxt_obase(BclContext\f[R] \f[I]ctxt\f[R]);
	.PP
	-\f[B]void bcl_ctxt_setObase(BclContext\f[R] \f[I]ctxt\f[R]\f[B],
	-size_t\f[R] \f[I]obase\f[R]\f[B]);\f[R]
	+\f[B]void bcl_ctxt_setObase(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]obase\f[R]);
	.SS Errors
	.PP
	These items allow clients to handle errors.
	.PP
	\f[B]typedef enum BclError BclError;\f[R]
	.PP
	-\f[B]BclError bcl_err(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_err(BclNumber\f[R] \f[I]n\f[R]);
	.SS Numbers
	.PP
	These items allow clients to manipulate and query the
	arbitrary-precision numbers managed by bcl(3).
	.PP
	\f[B]typedef struct { size_t i; } BclNumber;\f[R]
	.PP
	-\f[B]BclNumber bcl_num_create(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_num_create(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]void bcl_num_free(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]void bcl_num_free(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]bool bcl_num_neg(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]bool bcl_num_neg(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]void bcl_num_setNeg(BclNumber\f[R] \f[I]n\f[R]\f[B], bool\f[R]
	-\f[I]neg\f[R]\f[B]);\f[R]
	+\f[B]void bcl_num_setNeg(BclNumber\f[R] \f[I]n\f[R], bool
	+\f[I]neg\f[R]);
	.PP
	-\f[B]size_t bcl_num_scale(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]size_t bcl_num_scale(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]BclError bcl_num_setScale(BclNumber\f[R] \f[I]n\f[R]\f[B],
	-size_t\f[R] \f[I]scale\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_num_setScale(BclNumber\f[R] \f[I]n\f[R], size_t
	+\f[I]scale\f[R]);
	.PP
	-\f[B]size_t bcl_num_len(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]size_t bcl_num_len(BclNumber\f[R] \f[I]n\f[R]);
	.SS Conversion
	.PP
	These items allow clients to convert numbers into and from strings and
	integers.
	.PP
	-\f[B]BclNumber bcl_parse(const char *restrict\f[R]
	-\f[I]val\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_parse(const char restrict\f[R] \f[I]val\f[R]);*
	.PP
	-\f[B]char* bcl_string(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]char* bcl_string(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]BclError bcl_bigdig(BclNumber\f[R] \f[I]n\f[R]\f[B], BclBigDig
	-*\f[R]\f[I]result\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_bigdig(BclNumber\f[R] \f[I]n\f[R]**, BclBigDig
	+\f[I]\f[BI]result\f[I]\f[R]);*
	.PP
	-\f[B]BclNumber bcl_bigdig2num(BclBigDig\f[R] \f[I]val\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_bigdig2num(BclBigDig\f[R] \f[I]val\f[R]);
	.SS Math
	.PP
	These items allow clients to run math on numbers.
	.PP
	-\f[B]BclNumber bcl_add(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_add(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_sub(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_sub(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_mul(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_mul(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_div(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_div(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_mod(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_mod(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_pow(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_pow(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_lshift(BclNumber\f[R] \f[I]a\f[R]\f[B],
	-BclNumber\f[R] \f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_lshift(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_rshift(BclNumber\f[R] \f[I]a\f[R]\f[B],
	-BclNumber\f[R] \f[I]b\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_rshift(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclNumber bcl_sqrt(BclNumber\f[R] \f[I]a\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_sqrt(BclNumber\f[R] \f[I]a\f[R]);
	.PP
	-\f[B]BclError bcl_divmod(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B], BclNumber *\f[R]\f[I]c\f[R]\f[B], BclNumber
	-*\f[R]\f[I]d\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_divmod(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]*, BclNumber \f[I]\f[BI]c\f[I]\f[R], BclNumber
	+\f[I]\f[BI]d\f[I]\f[R]);*
	.PP
	-\f[B]BclNumber bcl_modexp(BclNumber\f[R] \f[I]a\f[R]\f[B],
	-BclNumber\f[R] \f[I]b\f[R]\f[B], BclNumber\f[R] \f[I]c\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_modexp(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R], BclNumber \f[I]c\f[R]);
	.SS Miscellaneous
	.PP
	These items are miscellaneous.
	.PP
	-\f[B]void bcl_zero(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]void bcl_zero(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]void bcl_one(BclNumber\f[R] \f[I]n\f[R]\f[B]);\f[R]
	+\f[B]void bcl_one(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	-\f[B]ssize_t bcl_cmp(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R]
	-\f[I]b\f[R]\f[B]);\f[R]
	+\f[B]ssize_t bcl_cmp(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]);
	.PP
	-\f[B]BclError bcl_copy(BclNumber\f[R] \f[I]d\f[R]\f[B], BclNumber\f[R]
	-\f[I]s\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_copy(BclNumber\f[R] \f[I]d\f[R], BclNumber
	+\f[I]s\f[R]);
	.PP
	-\f[B]BclNumber bcl_dup(BclNumber\f[R] \f[I]s\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_dup(BclNumber\f[R] \f[I]s\f[R]);
	.SS Pseudo-Random Number Generator
	.PP
	These items allow clients to manipulate the seeded pseudo-random number
	generator in bcl(3).
	.PP
	\f[B]#define BCL_SEED_ULONGS\f[R]
	.PP
	\f[B]#define BCL_SEED_SIZE\f[R]
	.PP
	\f[B]typedef unsigned long BclBigDig;\f[R]
	.PP
	\f[B]typedef unsigned long BclRandInt;\f[R]
	.PP
	-\f[B]BclNumber bcl_irand(BclNumber\f[R] \f[I]a\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_irand(BclNumber\f[R] \f[I]a\f[R]);
	.PP
	-\f[B]BclNumber bcl_frand(size_t\f[R] \f[I]places\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_frand(size_t\f[R] \f[I]places\f[R]);
	.PP
	-\f[B]BclNumber bcl_ifrand(BclNumber\f[R] \f[I]a\f[R]\f[B], size_t\f[R]
	-\f[I]places\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_ifrand(BclNumber\f[R] \f[I]a\f[R], size_t
	+\f[I]places\f[R]);
	.PP
	-\f[B]BclError bcl_rand_seedWithNum(BclNumber\f[R]
	-\f[I]n\f[R]\f[B]);\f[R]
	+\f[B]BclError bcl_rand_seedWithNum(BclNumber\f[R] \f[I]n\f[R]);
	.PP
	\f[B]BclError bcl_rand_seed(unsigned char\f[R]
	-\f[I]seed\f[R]\f[B][\f[R]\f[I]BC_SEED_SIZE\f[R]\f[B]]);\f[R]
	+\f[I]seed\f[R][\f[I]\f[BI]BC_SEED_SIZE\f[I]\f[R]]);
	.PP
	-\f[B]void bcl_rand_reseed(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]void bcl_rand_reseed(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]BclNumber bcl_rand_seed2num(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclNumber bcl_rand_seed2num(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]BclRandInt bcl_rand_int(\f[R]\f[I]void\f[R]\f[B]);\f[R]
	+\f[B]BclRandInt bcl_rand_int(\f[BI]\f[I]void\f[BI]\f[B]);\f[R]
	.PP
	-\f[B]BclRandInt bcl_rand_bounded(BclRandInt\f[R]
	-\f[I]bound\f[R]\f[B]);\f[R]
	+\f[B]BclRandInt bcl_rand_bounded(BclRandInt\f[R] \f[I]bound\f[R]);
	.SH DESCRIPTION
	.PP
	bcl(3) is a library that implements arbitrary-precision decimal math, as
	standardized by
	POSIX (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	in bc(1).
	.PP
	bcl(3) is async-signal-safe if
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] is used properly.
	+\f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R] is used properly.
	(See the \f[B]SIGNAL HANDLING\f[R] section.)
	.PP
	All of the items in its interface are described below.
	See the documentation for each function for what each function can
	return.
	.SS Signals
	-.TP
	-\f[B]void bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-An async-signal-safe function that can be called from a signal handler.
	+.PP
	+\f[B]void bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: An async-signal-safe function that can be called from a signal
	+handler.
	If called from a signal handler on the same thread as any executing
	bcl(3) functions, it will interrupt the functions and force them to
	return early.
	It is undefined behavior if this function is called from a thread that
	is \f[I]not\f[R] executing any bcl(3) functions while any bcl(3)
	functions are executing.
	-.RS
	-.PP
	-If execution \f[I]is\f[R] interrupted,
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] does \f[I]not\f[R]
	+.IP
	+.nf
	+\f[C]
	+If execution is interrupted, bcl_handleSignal(void) does not
	return to its caller.
	+
	+See the SIGNAL HANDLING section.
	+\f[R]
	+.fi
	+.PP
	+\f[B]bool bcl_running(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	-See the \f[B]SIGNAL HANDLING\f[R] section.
	-.RE
	-.TP
	-\f[B]bool bcl_running(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-An async-signal-safe function that can be called from a signal handler.
	+: An async-signal-safe function that can be called from a signal
	+handler.
	It will return \f[B]true\f[R] if any bcl(3) procedures are running,
	which means it is safe to call
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R].
	+\f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R].
	Otherwise, it returns \f[B]false\f[R].
	-.RS
	-.PP
	-See the \f[B]SIGNAL HANDLING\f[R] section.
	-.RE
	+.IP
	+.nf
	+\f[C]
	+See the SIGNAL HANDLING section.
	+\f[R]
	+.fi
	.SS Setup
	-.TP
	-\f[B]BclError bcl_init(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Initializes this library.
	+.PP
	+\f[B]BclError bcl_init(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Initializes this library.
	This function can be called multiple times, but each call must be
	-matched by a call to \f[B]bcl_free(\f[R]\f[I]void\f[R]\f[B])\f[R].
	+matched by a call to \f[B]bcl_free(\f[BI]\f[I]void\f[BI]\f[B])\f[R].
	This is to make it possible for multiple libraries and applications to
	initialize bcl(3) without problem.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+
	+This function must be the first one clients call. Calling any other
	+function without calling this one first is undefined behavior.
	+\f[R]
	+.fi
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	+\f[B]void bcl_free(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	-This function must be the first one clients call.
	-Calling any other function without calling this one first is undefined
	-behavior.
	-.RE
	-.TP
	-\f[B]void bcl_free(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Decrements bcl(3)\[cq]s reference count and frees the data associated
	+: Decrements bcl(3)\[aq]s reference count and frees the data associated
	with it if the reference count is \f[B]0\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This function must be the last one clients call. Calling this function
	+before calling any other function is undefined behavior.
	+\f[R]
	+.fi
	.PP
	-This function must be the last one clients call.
	-Calling this function before calling any other function is undefined
	-behavior.
	-.RE
	-.TP
	-\f[B]bool bcl_abortOnFatalError(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Queries and returns the current state of calling \f[B]abort()\f[R] on
	+\f[B]bool bcl_abortOnFatalError(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Queries and returns the current state of calling \f[B]abort()\f[R] on
	fatal errors.
	If \f[B]true\f[R] is returned, bcl(3) will cause a \f[B]SIGABRT\f[R] if
	a fatal error occurs.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	If activated, clients do not need to check for fatal errors.
	-.RE
	-.TP
	-\f[B]void bcl_setAbortOnFatalError(bool\f[R] \f[I]abrt\f[R]\f[B])\f[R]
	-Sets the state of calling \f[B]abort()\f[R] on fatal errors.
	+\f[R]
	+.fi
	+.PP
	+\f[B]void bcl_setAbortOnFatalError(bool\f[R] \f[I]abrt\f[R])
	+.PP
	+: Sets the state of calling \f[B]abort()\f[R] on fatal errors.
	If \f[I]abrt\f[R] is \f[B]false\f[R], bcl(3) will not cause a
	\f[B]SIGABRT\f[R] on fatal errors after the call.
	If \f[I]abrt\f[R] is \f[B]true\f[R], bcl(3) will cause a
	\f[B]SIGABRT\f[R] on fatal errors after the call.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	If activated, clients do not need to check for fatal errors.
	-.RE
	-.TP
	-\f[B]void bcl_gc(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Garbage collects cached instances of arbitrary-precision numbers.
	+\f[R]
	+.fi
	+.PP
	+\f[B]void bcl_gc(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Garbage collects cached instances of arbitrary-precision numbers.
	This only frees the memory of numbers that are \f[I]not\f[R] in use, so
	it is safe to call at any time.
	.SS Contexts
	.PP
	All procedures that take a \f[B]BclContext\f[R] parameter a require a
	valid context as an argument.
	-.TP
	+.PP
	\f[B]struct BclCtxt\f[R]
	-A forward declaration for a hidden \f[B]struct\f[R] type.
	+.PP
	+: A forward declaration for a hidden \f[B]struct\f[R] type.
	Clients cannot access the internals of the \f[B]struct\f[R] type
	directly.
	All interactions with the type are done through pointers.
	See \f[B]BclContext\f[R] below.
	-.TP
	+.PP
	\f[B]BclContext\f[R]
	-A typedef to a pointer of \f[B]struct BclCtxt\f[R].
	+.PP
	+: A typedef to a pointer of \f[B]struct BclCtxt\f[R].
	This is the only handle clients can get to \f[B]struct BclCtxt\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+A BclContext contains the values scale, ibase, and obase, as
	+well as a list of numbers.
	+
	+scale is a value used to control how many decimal places calculations
	+should use. A value of 0 means that calculations are done on integers
	+only, where applicable, and a value of 20, for example, means that all
	+applicable calculations return results with 20 decimal places. The default
	+is 0.
	+
	+ibase is a value used to control the input base. The minimum ibase
	+is 2, and the maximum is 36. If ibase is 2, numbers are
	+parsed as though they are in binary, and any digits larger than 1 are
	+clamped. Likewise, a value of 10 means that numbers are parsed as though
	+they are decimal, and any larger digits are clamped. The default is 10.
	+
	+obase is a value used to control the output base. The minimum obase
	+is 0 and the maximum is BC_BASE_MAX (see the LIMITS section).
	+
	+Numbers created in one context are not valid in another context. It is
	+undefined behavior to use a number created in a different context. Contexts
	+are meant to isolate the numbers used by different clients in the same
	+application.
	+\f[R]
	+.fi
	.PP
	-A \f[B]BclContext\f[R] contains the values \f[B]scale\f[R],
	-\f[B]ibase\f[R], and \f[B]obase\f[R], as well as a list of numbers.
	+\f[B]BclContext bcl_ctxt_create(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	-\f[B]scale\f[R] is a value used to control how many decimal places
	-calculations should use.
	-A value of \f[B]0\f[R] means that calculations are done on integers
	-only, where applicable, and a value of 20, for example, means that all
	-applicable calculations return results with 20 decimal places.
	-The default is \f[B]0\f[R].
	-.PP
	-\f[B]ibase\f[R] is a value used to control the input base.
	-The minimum \f[B]ibase\f[R] is \f[B]2\f[R], and the maximum is
	-\f[B]36\f[R].
	-If \f[B]ibase\f[R] is \f[B]2\f[R], numbers are parsed as though they are
	-in binary, and any digits larger than \f[B]1\f[R] are clamped.
	-Likewise, a value of \f[B]10\f[R] means that numbers are parsed as
	-though they are decimal, and any larger digits are clamped.
	-The default is \f[B]10\f[R].
	-.PP
	-\f[B]obase\f[R] is a value used to control the output base.
	-The minimum \f[B]obase\f[R] is \f[B]0\f[R] and the maximum is
	-\f[B]BC_BASE_MAX\f[R] (see the \f[B]LIMITS\f[R] section).
	-.PP
	-Numbers created in one context are not valid in another context.
	-It is undefined behavior to use a number created in a different context.
	-Contexts are meant to isolate the numbers used by different clients in
	-the same application.
	-.RE
	-.TP
	-\f[B]BclContext bcl_ctxt_create(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Creates a context and returns it.
	+: Creates a context and returns it.
	Returns \f[B]NULL\f[R] if there was an error.
	-.TP
	-\f[B]void bcl_ctxt_free(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Frees \f[I]ctxt\f[R], after which it is no longer valid.
	+.PP
	+\f[B]void bcl_ctxt_free(BclContext\f[R] \f[I]ctxt\f[R])
	+.PP
	+: Frees \f[I]ctxt\f[R], after which it is no longer valid.
	It is undefined behavior to attempt to use an invalid context.
	-.TP
	-\f[B]BclError bcl_pushContext(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Pushes \f[I]ctxt\f[R] onto bcl(3)\[cq]s stack of contexts.
	+.PP
	+\f[B]BclError bcl_pushContext(BclContext\f[R] \f[I]ctxt\f[R])
	+.PP
	+: Pushes \f[I]ctxt\f[R] onto bcl(3)\[aq]s stack of contexts.
	\f[I]ctxt\f[R] must have been created with
	-\f[B]bcl_ctxt_create(\f[R]\f[I]void\f[R]\f[B])\f[R].
	-.RS
	+\f[B]bcl_ctxt_create(\f[BI]\f[I]void\f[BI]\f[B])\f[R].
	+.IP
	+.nf
	+\f[C]
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+
	+There must be a valid context to do any arithmetic.
	+\f[R]
	+.fi
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	+\f[B]void bcl_popContext(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Pops the current context off of the stack, if one exists.
	+.PP
	+\f[B]BclContext bcl_context(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Returns the current context, or \f[B]NULL\f[R] if no context exists.
	+.PP
	+\f[B]void bcl_ctxt_freeNums(BclContext\f[R] \f[I]ctxt\f[R])
	.PP
	-There \f[I]must\f[R] be a valid context to do any arithmetic.
	-.RE
	-.TP
	-\f[B]void bcl_popContext(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Pops the current context off of the stack, if one exists.
	-.TP
	-\f[B]BclContext bcl_context(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Returns the current context, or \f[B]NULL\f[R] if no context exists.
	-.TP
	-\f[B]void bcl_ctxt_freeNums(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Frees all numbers in use that are associated with \f[I]ctxt\f[R].
	+: Frees all numbers in use that are associated with \f[I]ctxt\f[R].
	It is undefined behavior to attempt to use a number associated with
	\f[I]ctxt\f[R] after calling this procedure unless such numbers have
	-been created with \f[B]bcl_num_create(\f[R]\f[I]void\f[R]\f[B])\f[R]
	+been created with \f[B]bcl_num_create(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	after calling this procedure.
	-.TP
	-\f[B]size_t bcl_ctxt_scale(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Returns the \f[B]scale\f[R] for given context.
	-.TP
	-\f[B]void bcl_ctxt_setScale(BclContext\f[R] \f[I]ctxt\f[R]\f[B], size_t\f[R] \f[I]scale\f[R]\f[B])\f[R]
	-Sets the \f[B]scale\f[R] for the given context to the argument
	+.PP
	+\f[B]size_t bcl_ctxt_scale(BclContext\f[R] \f[I]ctxt\f[R])
	+.PP
	+: Returns the \f[B]scale\f[R] for given context.
	+.PP
	+\f[B]void bcl_ctxt_setScale(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]scale\f[R])
	+.PP
	+: Sets the \f[B]scale\f[R] for the given context to the argument
	\f[I]scale\f[R].
	-.TP
	-\f[B]size_t bcl_ctxt_ibase(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Returns the \f[B]ibase\f[R] for the given context.
	-.TP
	-\f[B]void bcl_ctxt_setIbase(BclContext\f[R] \f[I]ctxt\f[R]\f[B], size_t\f[R] \f[I]ibase\f[R]\f[B])\f[R]
	-Sets the \f[B]ibase\f[R] for the given context to the argument
	+.PP
	+\f[B]size_t bcl_ctxt_ibase(BclContext\f[R] \f[I]ctxt\f[R])
	+.PP
	+: Returns the \f[B]ibase\f[R] for the given context.
	+.PP
	+\f[B]void bcl_ctxt_setIbase(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]ibase\f[R])
	+.PP
	+: Sets the \f[B]ibase\f[R] for the given context to the argument
	\f[I]ibase\f[R].
	If the argument \f[I]ibase\f[R] is invalid, it clamped, so an
	\f[I]ibase\f[R] of \f[B]0\f[R] or \f[B]1\f[R] is clamped to \f[B]2\f[R],
	and any values above \f[B]36\f[R] are clamped to \f[B]36\f[R].
	-.TP
	-\f[B]size_t bcl_ctxt_obase(BclContext\f[R] \f[I]ctxt\f[R]\f[B])\f[R]
	-Returns the \f[B]obase\f[R] for the given context.
	-.TP
	-\f[B]void bcl_ctxt_setObase(BclContext\f[R] \f[I]ctxt\f[R]\f[B], size_t\f[R] \f[I]obase\f[R]\f[B])\f[R]
	-Sets the \f[B]obase\f[R] for the given context to the argument
	+.PP
	+\f[B]size_t bcl_ctxt_obase(BclContext\f[R] \f[I]ctxt\f[R])
	+.PP
	+: Returns the \f[B]obase\f[R] for the given context.
	+.PP
	+\f[B]void bcl_ctxt_setObase(BclContext\f[R] \f[I]ctxt\f[R], size_t
	+\f[I]obase\f[R])
	+.PP
	+: Sets the \f[B]obase\f[R] for the given context to the argument
	\f[I]obase\f[R].
	.SS Errors
	-.TP
	+.PP
	\f[B]BclError\f[R]
	-An \f[B]enum\f[R] of possible error codes.
	+.PP
	+: An \f[B]enum\f[R] of possible error codes.
	See the \f[B]ERRORS\f[R] section for a complete listing the codes.
	-.TP
	-\f[B]BclError bcl_err(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Checks for errors in a \f[B]BclNumber\f[R].
	+.PP
	+\f[B]BclError bcl_err(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Checks for errors in a \f[B]BclNumber\f[R].
	All functions that can return a \f[B]BclNumber\f[R] can encode an error
	in the number, and this function will return the error, if any.
	If there was no error, it will return \f[B]BCL_ERROR_NONE\f[R].
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	There must be a valid current context.
	-.RE
	+\f[R]
	+.fi
	.SS Numbers
	.PP
	All procedures in this section require a valid current context.
	-.TP
	+.PP
	\f[B]BclNumber\f[R]
	-A handle to an arbitrary-precision number.
	+.PP
	+: A handle to an arbitrary-precision number.
	The actual number type is not exposed; the \f[B]BclNumber\f[R] handle is
	the only way clients can refer to instances of arbitrary-precision
	numbers.
	-.TP
	-\f[B]BclNumber bcl_num_create(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Creates and returns a \f[B]BclNumber\f[R].
	-.RS
	-.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]void bcl_num_free(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Frees \f[I]n\f[R].
	+.PP
	+\f[B]BclNumber bcl_num_create(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Creates and returns a \f[B]BclNumber\f[R].
	+.IP
	+.nf
	+\f[C]
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	+.PP
	+\f[B]void bcl_num_free(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Frees \f[I]n\f[R].
	It is undefined behavior to use \f[I]n\f[R] after calling this function.
	-.TP
	-\f[B]bool bcl_num_neg(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Returns \f[B]true\f[R] if \f[I]n\f[R] is negative, \f[B]false\f[R]
	+.PP
	+\f[B]bool bcl_num_neg(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Returns \f[B]true\f[R] if \f[I]n\f[R] is negative, \f[B]false\f[R]
	otherwise.
	-.TP
	-\f[B]void bcl_num_setNeg(BclNumber\f[R] \f[I]n\f[R]\f[B], bool\f[R] \f[I]neg\f[R]\f[B])\f[R]
	-Sets \f[I]n\f[R]\[cq]s sign to \f[I]neg\f[R], where \f[B]true\f[R] is
	+.PP
	+\f[B]void bcl_num_setNeg(BclNumber\f[R] \f[I]n\f[R], bool
	+\f[I]neg\f[R])
	+.PP
	+: Sets \f[I]n\f[R]\[aq]s sign to \f[I]neg\f[R], where \f[B]true\f[R] is
	negative, and \f[B]false\f[R] is positive.
	-.TP
	-\f[B]size_t bcl_num_scale(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Returns the \f[I]scale\f[R] of \f[I]n\f[R].
	-.RS
	-.PP
	-The \f[I]scale\f[R] of a number is the number of decimal places it has
	-after the radix (decimal point).
	-.RE
	-.TP
	-\f[B]BclError bcl_num_setScale(BclNumber\f[R] \f[I]n\f[R]\f[B], size_t\f[R] \f[I]scale\f[R]\f[B])\f[R]
	-Sets the \f[I]scale\f[R] of \f[I]n\f[R] to the argument \f[I]scale\f[R].
	+.PP
	+\f[B]size_t bcl_num_scale(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Returns the \f[I]scale\f[R] of \f[I]n\f[R].
	+.IP
	+.nf
	+\f[C]
	+The scale of a number is the number of decimal places it has after the
	+radix (decimal point).
	+\f[R]
	+.fi
	+.PP
	+\f[B]BclError bcl_num_setScale(BclNumber\f[R] \f[I]n\f[R], size_t
	+\f[I]scale\f[R])
	+.PP
	+: Sets the \f[I]scale\f[R] of \f[I]n\f[R] to the argument
	+\f[I]scale\f[R].
	If the argument \f[I]scale\f[R] is greater than the \f[I]scale\f[R] of
	\f[I]n\f[R], \f[I]n\f[R] is extended.
	If the argument \f[I]scale\f[R] is less than the \f[I]scale\f[R] of
	\f[I]n\f[R], \f[I]n\f[R] is truncated.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]size_t bcl_num_len(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Returns the number of \f[I]significant decimal digits\f[R] in
	+\f[B]size_t bcl_num_len(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Returns the number of \f[I]significant decimal digits\f[R] in
	\f[I]n\f[R].
	.SS Conversion
	.PP
	All procedures in this section require a valid current context.
	.PP
	All procedures in this section consume the given \f[B]BclNumber\f[R]
	arguments that are not given to pointer arguments.
	See the \f[B]Consumption and Propagation\f[R] subsection below.
	-.TP
	-\f[B]BclNumber bcl_parse(const char *restrict\f[R] \f[I]val\f[R]\f[B])\f[R]
	-Parses a number string according to the current context\[cq]s
	+.PP
	+\f[B]BclNumber bcl_parse(const char restrict\f[R] \f[I]val\f[R])*
	+.PP
	+: Parses a number string according to the current context\[aq]s
	\f[B]ibase\f[R] and returns the resulting number.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+val must be non-NULL and a valid string. See
	+BCL_ERROR_PARSE_INVALID_STR in the ERRORS section for more
	+information.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_PARSE_INVALID_STR
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]val\f[R] must be non-\f[B]NULL\f[R] and a valid string.
	-See \f[B]BCL_ERROR_PARSE_INVALID_STR\f[R] in the \f[B]ERRORS\f[R]
	-section for more information.
	+\f[B]char* bcl_string(BclNumber\f[R] \f[I]n\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_PARSE_INVALID_STR\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]char* bcl_string(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Returns a string representation of \f[I]n\f[R] according the the current
	-context\[cq]s \f[B]ibase\f[R].
	+: Returns a string representation of \f[I]n\f[R] according the the
	+current context\[aq]s \f[B]ibase\f[R].
	The string is dynamically allocated and must be freed by the caller.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+n is consumed; it cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+\f[R]
	+.fi
	.PP
	-\f[I]n\f[R] is consumed; it cannot be used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	-.RE
	-.TP
	-\f[B]BclError bcl_bigdig(BclNumber\f[R] \f[I]n\f[R]\f[B], BclBigDig *\f[R]\f[I]result\f[R]\f[B])\f[R]
	-Converts \f[I]n\f[R] into a \f[B]BclBigDig\f[R] and returns the result
	-in the space pointed to by \f[I]result\f[R].
	-.RS
	+\f[B]BclError bcl_bigdig(BclNumber\f[R] \f[I]n\f[R]**, BclBigDig
	+\f[I]\f[BI]result\f[I]\f[R])*
	.PP
	-\f[I]a\f[R] must be smaller than \f[B]BC_OVERFLOW_MAX\f[R].
	-See the \f[B]LIMITS\f[R] section.
	+: Converts \f[I]n\f[R] into a \f[B]BclBigDig\f[R] and returns the result
	+in the space pointed to by \f[I]result\f[R].
	+.IP
	+.nf
	+\f[C]
	+a must be smaller than BC_OVERFLOW_MAX. See the LIMITS section.
	+
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_OVERFLOW
	+
	+n is consumed; it cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+\f[R]
	+.fi
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_OVERFLOW\f[R]
	+\f[B]BclNumber bcl_bigdig2num(BclBigDig\f[R] \f[I]val\f[R])
	.PP
	-\f[I]n\f[R] is consumed; it cannot be used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	-.RE
	-.TP
	-\f[B]BclNumber bcl_bigdig2num(BclBigDig\f[R] \f[I]val\f[R]\f[B])\f[R]
	-Creates a \f[B]BclNumber\f[R] from \f[I]val\f[R].
	-.RS
	-.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	+: Creates a \f[B]BclNumber\f[R] from \f[I]val\f[R].
	+.IP
	+.nf
	+\f[C]
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.SS Math
	.PP
	All procedures in this section require a valid current context.
	.PP
	All procedures in this section can return the following errors:
	.IP \[bu] 2
	\f[B]BCL_ERROR_INVALID_NUM\f[R]
	.IP \[bu] 2
	\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	.IP \[bu] 2
	\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.TP
	-\f[B]BclNumber bcl_add(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Adds \f[I]a\f[R] and \f[I]b\f[R] and returns the result.
	+.PP
	+\f[B]BclNumber bcl_add(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	+.PP
	+: Adds \f[I]a\f[R] and \f[I]b\f[R] and returns the result.
	The \f[I]scale\f[R] of the result is the max of the \f[I]scale\f[R]s of
	\f[I]a\f[R] and \f[I]b\f[R].
	-.RS
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_sub(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_sub(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Subtracts \f[I]b\f[R] from \f[I]a\f[R] and returns the result.
	+: Subtracts \f[I]b\f[R] from \f[I]a\f[R] and returns the result.
	The \f[I]scale\f[R] of the result is the max of the \f[I]scale\f[R]s of
	\f[I]a\f[R] and \f[I]b\f[R].
	-.RS
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_mul(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_mul(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Multiplies \f[I]a\f[R] and \f[I]b\f[R] and returns the result.
	+: Multiplies \f[I]a\f[R] and \f[I]b\f[R] and returns the result.
	If \f[I]ascale\f[R] is the \f[I]scale\f[R] of \f[I]a\f[R] and
	\f[I]bscale\f[R] is the \f[I]scale\f[R] of \f[I]b\f[R], the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(ascale+bscale,max(scale,ascale,bscale))\f[R], where
	\f[B]min()\f[R] and \f[B]max()\f[R] return the obvious values.
	-.RS
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_div(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_div(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Divides \f[I]a\f[R] by \f[I]b\f[R] and returns the result.
	+: Divides \f[I]a\f[R] by \f[I]b\f[R] and returns the result.
	The \f[I]scale\f[R] of the result is the \f[I]scale\f[R] of the current
	context.
	-.RS
	-.PP
	-\f[I]b\f[R] cannot be \f[B]0\f[R].
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+b cannot be 0.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_DIVIDE_BY_ZERO
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_mod(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_mod(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Divides \f[I]a\f[R] by \f[I]b\f[R] to the \f[I]scale\f[R] of the current
	-context, computes the modulus \f[B]a-(a/b)*b\f[R], and returns the
	-modulus.
	-.RS
	-.PP
	-\f[I]b\f[R] cannot be \f[B]0\f[R].
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+: Divides \f[I]a\f[R] by \f[I]b\f[R] to the \f[I]scale\f[R] of the
	+current context, computes the modulus \f[B]a-(a/b)*b\f[R], and returns
	+the modulus.
	+.IP
	+.nf
	+\f[C]
	+b cannot be 0.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_DIVIDE_BY_ZERO
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_pow(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_pow(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Calculates \f[I]a\f[R] to the power of \f[I]b\f[R] to the
	+: Calculates \f[I]a\f[R] to the power of \f[I]b\f[R] to the
	\f[I]scale\f[R] of the current context.
	\f[I]b\f[R] must be an integer, but can be negative.
	If it is negative, \f[I]a\f[R] must be non-zero.
	-.RS
	-.PP
	-\f[I]b\f[R] must be an integer.
	-If \f[I]b\f[R] is negative, \f[I]a\f[R] must not be \f[B]0\f[R].
	-.PP
	-\f[I]a\f[R] must be smaller than \f[B]BC_OVERFLOW_MAX\f[R].
	-See the \f[B]LIMITS\f[R] section.
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+b must be an integer. If b is negative, a must not be 0.
	+
	+a must be smaller than BC_OVERFLOW_MAX. See the LIMITS section.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_MATH_OVERFLOW
	+* BCL_ERROR_MATH_DIVIDE_BY_ZERO
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_lshift(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_OVERFLOW\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_lshift(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Shifts \f[I]a\f[R] left (moves the radix right) by \f[I]b\f[R] places
	+: Shifts \f[I]a\f[R] left (moves the radix right) by \f[I]b\f[R] places
	and returns the result.
	This is done in decimal.
	\f[I]b\f[R] must be an integer.
	-.RS
	-.PP
	-\f[I]b\f[R] must be an integer.
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+b must be an integer.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_rshift(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_rshift(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Shifts \f[I]a\f[R] right (moves the radix left) by \f[I]b\f[R] places
	+: Shifts \f[I]a\f[R] right (moves the radix left) by \f[I]b\f[R] places
	and returns the result.
	This is done in decimal.
	\f[I]b\f[R] must be an integer.
	-.RS
	-.PP
	-\f[I]b\f[R] must be an integer.
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+b must be an integer.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+a and b can be the same number.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] and \f[I]b\f[R] can be the same number.
	+\f[B]BclNumber bcl_sqrt(BclNumber\f[R] \f[I]a\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_sqrt(BclNumber\f[R] \f[I]a\f[R]\f[B])\f[R]
	-Calculates the square root of \f[I]a\f[R] and returns the result.
	+: Calculates the square root of \f[I]a\f[R] and returns the result.
	The \f[I]scale\f[R] of the result is equal to the \f[B]scale\f[R] of the
	current context.
	-.RS
	-.PP
	-\f[I]a\f[R] cannot be negative.
	+.IP
	+.nf
	+\f[C]
	+a cannot be negative.
	+
	+a is consumed; it cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NEGATIVE
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] is consumed; it cannot be used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+\f[B]BclError bcl_divmod(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R]*, BclNumber \f[I]\f[BI]c\f[I]\f[R], BclNumber
	+\f[I]\f[BI]d\f[I]\f[R])*
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NEGATIVE\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclError bcl_divmod(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B], BclNumber \f[R]\f[I]c\f[R]\f[B], BclNumber \f[R]\f[I]d\f[R]\f[B])\f[R]
	-Divides \f[I]a\f[R] by \f[I]b\f[R] and returns the quotient in a new
	+: Divides \f[I]a\f[R] by \f[I]b\f[R] and returns the quotient in a new
	number which is put into the space pointed to by \f[I]c\f[R], and puts
	the modulus in a new number which is put into the space pointed to by
	\f[I]d\f[R].
	-.RS
	-.PP
	-\f[I]b\f[R] cannot be \f[B]0\f[R].
	-.PP
	-\f[I]a\f[R] and \f[I]b\f[R] are consumed; they cannot be used after the
	-call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+.IP
	+.nf
	+\f[C]
	+b cannot be 0.
	+
	+a and b are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+c and d cannot point to the same place, nor can they point to the space
	+occupied by a or b.
	+
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_DIVIDE_BY_ZERO
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]c\f[R] and \f[I]d\f[R] cannot point to the same place, nor can they
	-point to the space occupied by \f[I]a\f[R] or \f[I]b\f[R].
	+\f[B]BclNumber bcl_modexp(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R], BclNumber \f[I]c\f[R])
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_modexp(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B], BclNumber\f[R] \f[I]c\f[R]\f[B])\f[R]
	-Computes a modular exponentiation where \f[I]a\f[R] is the base,
	+: Computes a modular exponentiation where \f[I]a\f[R] is the base,
	\f[I]b\f[R] is the exponent, and \f[I]c\f[R] is the modulus, and returns
	the result.
	The \f[I]scale\f[R] of the result is equal to the \f[B]scale\f[R] of the
	current context.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+a, b, and c must be integers. c must not be 0. b must not be
	+negative.
	+
	+a, b, and c are consumed; they cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NEGATIVE
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_MATH_DIVIDE_BY_ZERO
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	+.SS Miscellaneous
	.PP
	-\f[I]a\f[R], \f[I]b\f[R], and \f[I]c\f[R] must be integers.
	-\f[I]c\f[R] must not be \f[B]0\f[R].
	-\f[I]b\f[R] must not be negative.
	+\f[B]void bcl_zero(BclNumber\f[R] \f[I]n\f[R])
	.PP
	-\f[I]a\f[R], \f[I]b\f[R], and \f[I]c\f[R] are consumed; they cannot be
	-used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+: Sets \f[I]n\f[R] to \f[B]0\f[R].
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NEGATIVE\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.SS Miscellaneous
	-.TP
	-\f[B]void bcl_zero(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Sets \f[I]n\f[R] to \f[B]0\f[R].
	-.TP
	-\f[B]void bcl_one(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Sets \f[I]n\f[R] to \f[B]1\f[R].
	-.TP
	-\f[B]ssize_t bcl_cmp(BclNumber\f[R] \f[I]a\f[R]\f[B], BclNumber\f[R] \f[I]b\f[R]\f[B])\f[R]
	-Compares \f[I]a\f[R] and \f[I]b\f[R] and returns \f[B]0\f[R] if
	+\f[B]void bcl_one(BclNumber\f[R] \f[I]n\f[R])
	+.PP
	+: Sets \f[I]n\f[R] to \f[B]1\f[R].
	+.PP
	+\f[B]ssize_t bcl_cmp(BclNumber\f[R] \f[I]a\f[R], BclNumber
	+\f[I]b\f[R])
	+.PP
	+: Compares \f[I]a\f[R] and \f[I]b\f[R] and returns \f[B]0\f[R] if
	\f[I]a\f[R] and \f[I]b\f[R] are equal, \f[B]<0\f[R] if \f[I]a\f[R] is
	less than \f[I]b\f[R], and \f[B]>0\f[R] if \f[I]a\f[R] is greater than
	\f[I]b\f[R].
	-.TP
	-\f[B]BclError bcl_copy(BclNumber\f[R] \f[I]d\f[R]\f[B], BclNumber\f[R] \f[I]s\f[R]\f[B])\f[R]
	-Copies \f[I]s\f[R] into \f[I]d\f[R].
	-.RS
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_dup(BclNumber\f[R] \f[I]s\f[R]\f[B])\f[R]
	-Creates and returns a new \f[B]BclNumber\f[R] that is a copy of
	-\f[I]s\f[R].
	-.RS
	+\f[B]BclError bcl_copy(BclNumber\f[R] \f[I]d\f[R], BclNumber
	+\f[I]s\f[R])
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	+: Copies \f[I]s\f[R] into \f[I]d\f[R].
	+.IP
	+.nf
	+\f[C]
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	+.PP
	+\f[B]BclNumber bcl_dup(BclNumber\f[R] \f[I]s\f[R])
	+.PP
	+: Creates and returns a new \f[B]BclNumber\f[R] that is a copy of
	+\f[I]s\f[R].
	+.IP
	+.nf
	+\f[C]
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	The pseudo-random number generator in bcl(3) is a \f[I]seeded\f[R] PRNG.
	Given the same seed twice, it will produce the same sequence of
	pseudo-random numbers twice.
	.PP
	By default, bcl(3) attempts to seed the PRNG with data from
	\f[B]/dev/urandom\f[R].
	-If that fails, it seeds itself with by calling \f[B]libc\f[R]\[cq]s
	+If that fails, it seeds itself with by calling \f[B]libc\f[R]\[aq]s
	\f[B]srand(time(NULL))\f[R] and then calling \f[B]rand()\f[R] for each
	byte, since \f[B]rand()\f[R] is only guaranteed to return \f[B]15\f[R]
	bits.
	.PP
	This should provide fairly good seeding in the standard case while also
	remaining fairly portable.
	.PP
	If necessary, the PRNG can be reseeded with one of the following
	functions:
	.IP \[bu] 2
	\f[B]bcl_rand_seedWithNum(BclNumber)\f[R]
	.IP \[bu] 2
	\f[B]bcl_rand_seed(unsigned char[BC_SEED_SIZE])\f[R]
	.IP \[bu] 2
	-\f[B]bcl_rand_reseed(\f[R]\f[I]void\f[R]\f[B])\f[R]
	+\f[B]bcl_rand_reseed(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	The following items allow clients to use the pseudo-random number
	generator.
	All procedures require a valid current context.
	-.TP
	+.PP
	\f[B]BCL_SEED_ULONGS\f[R]
	-The number of \f[B]unsigned long\f[R]\[cq]s in a seed for bcl(3)\[cq]s
	+.PP
	+: The number of \f[B]unsigned long\f[R]\[aq]s in a seed for bcl(3)\[aq]s
	random number generator.
	-.TP
	+.PP
	\f[B]BCL_SEED_SIZE\f[R]
	-The size, in \f[B]char\f[R]\[cq]s, of a seed for bcl(3)\[cq]s random
	+.PP
	+: The size, in \f[B]char\f[R]\[aq]s, of a seed for bcl(3)\[aq]s random
	number generator.
	-.TP
	+.PP
	\f[B]BclBigDig\f[R]
	-bcl(3)\[cq]s overflow type (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	+: bcl(3)\[aq]s overflow type (see the \f[B]PERFORMANCE\f[R] section).
	+.PP
	\f[B]BclRandInt\f[R]
	-An unsigned integer type returned by bcl(3)\[cq]s random number
	+.PP
	+: An unsigned integer type returned by bcl(3)\[aq]s random number
	generator.
	-.TP
	-\f[B]BclNumber bcl_irand(BclNumber\f[R] \f[I]a\f[R]\f[B])\f[R]
	-Returns a random number that is not larger than \f[I]a\f[R] in a new
	+.PP
	+\f[B]BclNumber bcl_irand(BclNumber\f[R] \f[I]a\f[R])
	+.PP
	+: Returns a random number that is not larger than \f[I]a\f[R] in a new
	number.
	If \f[I]a\f[R] is \f[B]0\f[R] or \f[B]1\f[R], the new number is equal to
	\f[B]0\f[R].
	The bound is unlimited, so it is not bound to the size of
	\f[B]BclRandInt\f[R].
	This is done by generating as many random numbers as necessary,
	multiplying them by certain exponents, and adding them all together.
	-.RS
	-.PP
	-\f[I]a\f[R] must be an integer and non-negative.
	-.PP
	-\f[I]a\f[R] is consumed; it cannot be used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	-.PP
	+.IP
	+.nf
	+\f[C]
	+a must be an integer and non-negative.
	+
	+a is consumed; it cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	This procedure requires a valid current context.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NEGATIVE
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NEGATIVE\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_frand(size_t\f[R] \f[I]places\f[R]\f[B])\f[R]
	-Returns a random number between \f[B]0\f[R] (inclusive) and \f[B]1\f[R]
	-(exclusive) that has \f[I]places\f[R] decimal digits after the radix
	-(decimal point).
	-There are no limits on \f[I]places\f[R].
	-.RS
	+\f[B]BclNumber bcl_frand(size_t\f[R] \f[I]places\f[R])
	.PP
	+: Returns a random number between \f[B]0\f[R] (inclusive) and
	+\f[B]1\f[R] (exclusive) that has \f[I]places\f[R] decimal digits after
	+the radix (decimal point).
	+There are no limits on \f[I]places\f[R].
	+.IP
	+.nf
	+\f[C]
	This procedure requires a valid current context.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclNumber bcl_ifrand(BclNumber\f[R] \f[I]a\f[R]\f[B], size_t\f[R] \f[I]places\f[R]\f[B])\f[R]
	-Returns a random number less than \f[I]a\f[R] with \f[I]places\f[R]
	+\f[B]BclNumber bcl_ifrand(BclNumber\f[R] \f[I]a\f[R], size_t
	+\f[I]places\f[R])
	+.PP
	+: Returns a random number less than \f[I]a\f[R] with \f[I]places\f[R]
	decimal digits after the radix (decimal point).
	There are no limits on \f[I]a\f[R] or \f[I]places\f[R].
	-.RS
	-.PP
	-\f[I]a\f[R] must be an integer and non-negative.
	+.IP
	+.nf
	+\f[C]
	+a must be an integer and non-negative.
	+
	+a is consumed; it cannot be used after the call. See the
	+Consumption and Propagation subsection below.
	+
	+This procedure requires a valid current context.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_MATH_NEGATIVE
	+* BCL_ERROR_MATH_NON_INTEGER
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-\f[I]a\f[R] is consumed; it cannot be used after the call.
	-See the \f[B]Consumption and Propagation\f[R] subsection below.
	+\f[B]BclError bcl_rand_seedWithNum(BclNumber\f[R] \f[I]n\f[R])
	.PP
	+: Seeds the PRNG with \f[I]n\f[R].
	+.IP
	+.nf
	+\f[C]
	+n is not consumed.
	+
	This procedure requires a valid current context.
	+
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_NUM
	+* BCL_ERROR_INVALID_CONTEXT
	+
	+Note that if bcl_rand_seed2num(void) or
	+bcl_rand_seed2num_err(BclNumber) are called right after this function,
	+they are not guaranteed to return a number equal to n.
	+\f[R]
	+.fi
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NEGATIVE\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclError bcl_rand_seedWithNum(BclNumber\f[R] \f[I]n\f[R]\f[B])\f[R]
	-Seeds the PRNG with \f[I]n\f[R].
	-.RS
	-.PP
	-\f[I]n\f[R] is \f[I]not\f[R] consumed.
	+\f[B]BclError bcl_rand_seed(unsigned char\f[R]
	+\f[I]seed\f[R][\f[I]\f[BI]BC_SEED_SIZE\f[I]\f[R]])
	.PP
	-This procedure requires a valid current context.
	+: Seeds the PRNG with the bytes in \f[I]seed\f[R].
	+.IP
	+.nf
	+\f[C]
	+If there was no error, BCL_ERROR_NONE is returned. Otherwise, this
	+function can return:
	+
	+* BCL_ERROR_INVALID_CONTEXT
	+\f[R]
	+.fi
	.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	+\f[B]void bcl_rand_reseed(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	-Note that if \f[B]bcl_rand_seed2num(\f[R]\f[I]void\f[R]\f[B])\f[R] or
	-\f[B]bcl_rand_seed2num_err(BclNumber)\f[R] are called right after this
	-function, they are not guaranteed to return a number equal to
	-\f[I]n\f[R].
	-.RE
	-.TP
	-\f[B]BclError bcl_rand_seed(unsigned char\f[R] \f[I]seed\f[R]\f[B][\f[R]\f[I]BC_SEED_SIZE\f[R]\f[B]])\f[R]
	-Seeds the PRNG with the bytes in \f[I]seed\f[R].
	-.RS
	-.PP
	-If there was no error, \f[B]BCL_ERROR_NONE\f[R] is returned.
	-Otherwise, this function can return:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.RE
	-.TP
	-\f[B]void bcl_rand_reseed(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Reseeds the PRNG with the default reseeding behavior.
	+: Reseeds the PRNG with the default reseeding behavior.
	First, it attempts to read data from \f[B]/dev/urandom\f[R] and falls
	-back to \f[B]libc\f[R]\[cq]s \f[B]rand()\f[R].
	-.RS
	-.PP
	+back to \f[B]libc\f[R]\[aq]s \f[B]rand()\f[R].
	+.IP
	+.nf
	+\f[C]
	This procedure cannot fail.
	-.RE
	-.TP
	-\f[B]BclNumber bcl_rand_seed2num(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Returns the current seed of the PRNG as a \f[B]BclNumber\f[R].
	-.RS
	+\f[R]
	+.fi
	.PP
	+\f[B]BclNumber bcl_rand_seed2num(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	+.PP
	+: Returns the current seed of the PRNG as a \f[B]BclNumber\f[R].
	+.IP
	+.nf
	+\f[C]
	This procedure requires a valid current context.
	+
	+bcl(3) will encode an error in the return value, if there was one. The error
	+can be queried with bcl_err(BclNumber). Possible errors include:
	+
	+* BCL_ERROR_INVALID_CONTEXT
	+* BCL_ERROR_FATAL_ALLOC_ERR
	+\f[R]
	+.fi
	.PP
	-bcl(3) will encode an error in the return value, if there was one.
	-The error can be queried with \f[B]bcl_err(BclNumber)\f[R].
	-Possible errors include:
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-.IP \[bu] 2
	-\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-.RE
	-.TP
	-\f[B]BclRandInt bcl_rand_int(\f[R]\f[I]void\f[R]\f[B])\f[R]
	-Returns a random integer between \f[B]0\f[R] and \f[B]BC_RAND_MAX\f[R]
	-(inclusive).
	-.RS
	+\f[B]BclRandInt bcl_rand_int(\f[BI]\f[I]void\f[BI]\f[B])\f[R]
	.PP
	+: Returns a random integer between \f[B]0\f[R] and \f[B]BC_RAND_MAX\f[R]
	+(inclusive).
	+.IP
	+.nf
	+\f[C]
	This procedure cannot fail.
	-.RE
	-.TP
	-\f[B]BclRandInt bcl_rand_bounded(BclRandInt\f[R] \f[I]bound\f[R]\f[B])\f[R]
	-Returns a random integer between \f[B]0\f[R] and \f[I]bound\f[R]
	+\f[R]
	+.fi
	+.PP
	+\f[B]BclRandInt bcl_rand_bounded(BclRandInt\f[R] \f[I]bound\f[R])
	+.PP
	+: Returns a random integer between \f[B]0\f[R] and \f[I]bound\f[R]
	(exclusive).
	Bias is removed before returning the integer.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	This procedure cannot fail.
	-.RE
	+\f[R]
	+.fi
	.SS Consumption and Propagation
	.PP
	Some functions are listed as consuming some or all of their arguments.
	This means that the arguments are freed, regardless of if there were
	errors or not.
	.PP
	This is to enable compact code like the following:
	.IP
	.nf
	\f[C]
	BclNumber n = bcl_num_add(bcl_num_mul(a, b), bcl_num_div(c, d));
	\f[R]
	.fi
	.PP
	If arguments to those functions were not consumed, memory would be
	leaked until reclaimed with \f[B]bcl_ctxt_freeNums(BclContext)\f[R].
	.PP
	When errors occur, they are propagated through.
	The result should always be checked with \f[B]bcl_err(BclNumber)\f[R],
	so the example above should properly be:
	.IP
	.nf
	\f[C]
	BclNumber n = bcl_num_add(bcl_num_mul(a, b), bcl_num_div(c, d));
	if (bc_num_err(n) != BCL_ERROR_NONE) {
	// Handle the error.
	}
	\f[R]
	.fi
	.SH ERRORS
	.PP
	Most functions in bcl(3) return, directly or indirectly, any one of the
	error codes defined in \f[B]BclError\f[R].
	The complete list of codes is the following:
	-.TP
	+.PP
	\f[B]BCL_ERROR_NONE\f[R]
	-Success; no error occurred.
	-.TP
	+.PP
	+: Success; no error occurred.
	+.PP
	\f[B]BCL_ERROR_INVALID_NUM\f[R]
	-An invalid \f[B]BclNumber\f[R] was given as a parameter.
	-.TP
	+.PP
	+: An invalid \f[B]BclNumber\f[R] was given as a parameter.
	+.PP
	\f[B]BCL_ERROR_INVALID_CONTEXT\f[R]
	-An invalid \f[B]BclContext\f[R] is being used.
	-.TP
	+.PP
	+: An invalid \f[B]BclContext\f[R] is being used.
	+.PP
	\f[B]BCL_ERROR_SIGNAL\f[R]
	-A signal interrupted execution.
	-.TP
	+.PP
	+: A signal interrupted execution.
	+.PP
	\f[B]BCL_ERROR_MATH_NEGATIVE\f[R]
	-A negative number was given as an argument to a parameter that cannot
	+.PP
	+: A negative number was given as an argument to a parameter that cannot
	accept negative numbers, such as for square roots.
	-.TP
	+.PP
	\f[B]BCL_ERROR_MATH_NON_INTEGER\f[R]
	-A non-integer was given as an argument to a parameter that cannot accept
	-non-integer numbers, such as for the second parameter of
	+.PP
	+: A non-integer was given as an argument to a parameter that cannot
	+accept non-integer numbers, such as for the second parameter of
	\f[B]bcl_num_pow()\f[R].
	-.TP
	+.PP
	\f[B]BCL_ERROR_MATH_OVERFLOW\f[R]
	-A number that would overflow its result was given as an argument, such
	+.PP
	+: A number that would overflow its result was given as an argument, such
	as for converting a \f[B]BclNumber\f[R] to a \f[B]BclBigDig\f[R].
	-.TP
	+.PP
	\f[B]BCL_ERROR_MATH_DIVIDE_BY_ZERO\f[R]
	-A divide by zero occurred.
	-.TP
	+.PP
	+: A divide by zero occurred.
	+.PP
	\f[B]BCL_ERROR_PARSE_INVALID_STR\f[R]
	-An invalid number string was passed to a parsing function.
	-.RS
	-.PP
	-A valid number string can only be one radix (period).
	-In addition, any lowercase ASCII letters, symbols, or non-ASCII
	-characters are invalid.
	-It is allowed for the first character to be a dash.
	-In that case, the number is considered to be negative.
	-.PP
	-There is one exception to the above: one lowercase \f[B]e\f[R] is
	-allowed in the number, after the radix, if it exists.
	-If the letter \f[B]e\f[R] exists, the number is considered to be in
	-scientific notation, where the part before the \f[B]e\f[R] is the
	-number, and the part after, which must be an integer, is the exponent.
	-There can be a dash right after the \f[B]e\f[R] to indicate a negative
	+.PP
	+: An invalid number string was passed to a parsing function.
	+.IP
	+.nf
	+\f[C]
	+A valid number string can only be one radix (period). In addition, any
	+lowercase ASCII letters, symbols, or non-ASCII characters are invalid. It is
	+allowed for the first character to be a dash. In that case, the number is
	+considered to be negative.
	+
	+There is one exception to the above: one lowercase e is allowed in the
	+number, after the radix, if it exists. If the letter e exists, the
	+number is considered to be in scientific notation, where the part before the
	+e is the number, and the part after, which must be an integer, is the
	+exponent. There can be a dash right after the e to indicate a negative
	exponent.
	+
	+WARNING: Both the number and the exponent in scientific notation are
	+interpreted according to the current ibase, but the number is still
	+multiplied by 10\[rs]\[ha]exponent regardless of the current ibase. For
	+example, if ibase is 16 and bcl(3) is given the number string
	+FFeA, the resulting decimal number will be 2550000000000, and if
	+bcl(3) is given the number string 10e-4, the resulting decimal number
	+will be 0.0016.
	+\f[R]
	+.fi
	.PP
	-\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	-notation are interpreted according to the current \f[B]ibase\f[R], but
	-the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	-of the current \f[B]ibase\f[R].
	-For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and bcl(3) is given the
	-number string \f[B]FFeA\f[R], the resulting decimal number will be
	-\f[B]2550000000000\f[R], and if bcl(3) is given the number string
	-\f[B]10e-4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	-.RE
	-.TP
	\f[B]BCL_ERROR_FATAL_ALLOC_ERR\f[R]
	-bcl(3) failed to allocate memory.
	-.RS
	-.PP
	-If clients call \f[B]bcl_setAbortOnFatalError()\f[R] with an
	-\f[B]true\f[R] argument, this error will cause bcl(3) to throw a
	-\f[B]SIGABRT\f[R].
	-This behavior can also be turned off later by calling that same function
	-with a \f[B]false\f[R] argument.
	+.PP
	+: bcl(3) failed to allocate memory.
	+.IP
	+.nf
	+\f[C]
	+If clients call bcl_setAbortOnFatalError() with an true argument,
	+this error will cause bcl(3) to throw a SIGABRT. This behavior can also
	+be turned off later by calling that same function with a false argument.
	By default, this behavior is off.
	+
	+It is highly recommended that client libraries do not activate this
	+behavior.
	+\f[R]
	+.fi
	.PP
	-It is highly recommended that client libraries do \f[I]not\f[R] activate
	-this behavior.
	-.RE
	-.TP
	\f[B]BCL_ERROR_FATAL_UNKNOWN_ERR\f[R]
	-An unknown error occurred.
	-.RS
	-.PP
	-If clients call \f[B]bcl_setAbortOnFatalError()\f[R] with an
	-\f[B]true\f[R] argument, this error will cause bcl(3) to throw a
	-\f[B]SIGABRT\f[R].
	-This behavior can also be turned off later by calling that same function
	-with a \f[B]false\f[R] argument.
	-By default, this behavior is off.
	.PP
	-It is highly recommended that client libraries do \f[I]not\f[R] activate
	-this behavior.
	-.RE
	+: An unknown error occurred.
	+.IP
	+.nf
	+\f[C]
	+If clients call bcl_setAbortOnFatalError() with an true argument,
	+this error will cause bcl(3) to throw a SIGABRT. This behavior can also
	+be turned off later by calling that same function with a false argument.
	+By default, this behavior is off.
	+
	+It is highly recommended that client libraries do not activate this
	+behavior.
	+\f[R]
	+.fi
	.SH ATTRIBUTES
	.PP
	-When \f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] is used
	+When \f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R] is used
	properly, bcl(3) is async-signal-safe.
	.PP
	bcl(3) is \f[I]MT-Unsafe\f[R]: it is unsafe to call any functions from
	more than one thread.
	.SH PERFORMANCE
	.PP
	Most bc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	bcl(3) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]BC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]BC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]BC_BASE_DIGS\f[R].
	.PP
	In addition, this bcl(3) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]BC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on bcl(3):
	-.TP
	+.PP
	\f[B]BC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	bcl(3) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]BC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]BC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]BC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]BC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]BC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]BC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]BC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]BC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]BC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]BC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]bcl_rand_int()\f[R]
	-function.
	+.PP
	+: The maximum integer (inclusive) returned by the
	+\f[B]bcl_rand_int()\f[R] function.
	Set at \f[B]2\[ha]BC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]BC_OVERFLOW_MAX\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH SIGNAL HANDLING
	.PP
	If a signal handler calls
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] from the same
	+\f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R] from the same
	thread that there are bcl(3) functions executing in, it will cause all
	execution to stop as soon as possible, interrupting long-running
	calculations, if necessary and cause the function that was executing to
	return.
	If possible, the error code \f[B]BC_ERROR_SIGNAL\f[R] is returned.
	.PP
	If execution \f[I]is\f[R] interrupted,
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] does \f[I]not\f[R]
	-return to its caller.
	+\f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R] does
	+\f[I]not\f[R] return to its caller.
	.PP
	It is undefined behavior if
	-\f[B]bcl_handleSignal(\f[R]\f[I]void\f[R]\f[B])\f[R] is called from a
	+\f[B]bcl_handleSignal(\f[BI]\f[I]void\f[BI]\f[B])\f[R] is called from a
	thread that is not executing bcl(3) functions, if bcl(3) functions are
	executing.
	.SH SEE ALSO
	.PP
	bc(1) and dc(1)
	.SH STANDARDS
	.PP
	bcl(3) is compliant with the arithmetic defined in the IEEE Std
	1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification for bc(1).
	.PP
	Note that the specification explicitly says that bc(1) only accepts
	numbers that use a period (\f[B].\f[R]) as a radix point, regardless of
	the value of \f[B]LC_NUMERIC\f[R].
	This is also true of bcl(3).
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHORS
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/build.md b/contrib/bc/manuals/build.md
	index a58da6d427ed..656aa5250739 100644
	--- a/contrib/bc/manuals/build.md
	+++ b/contrib/bc/manuals/build.md
	@@ -1,710 +1,751 @@
	# Build

	This `bc` attempts to be as portable as possible. It can be built on any
	POSIX-compliant system.

	To accomplish that, a POSIX-compatible, custom `configure.sh` script is used to
	select build options, compiler, and compiler flags and generate a `Makefile`.

	The general form of configuring, building, and installing this `bc` is as
	follows:

	```
	[ENVIRONMENT_VARIABLE=<value>...] ./configure.sh [build_options...]
	make
	make install
	```

	To get all of the options, including any useful environment variables, use
	either one of the following commands:

	```
	./configure.sh -h
	./configure.sh --help
	```

	*WARNING*: even though `configure.sh` supports both option types, short and
	long, it does not support handling both at the same time. Use only one type.

	To learn the available `make` targets run the following command after running
	the `configure.sh` script:

	```
	make help
	```

	See [Build Environment Variables][4] for a more detailed description of all
	accepted environment variables and [Build Options][5] for more detail about all
	accepted build options.

	+## Windows
	+
	+On Windows, this `bc` can be built using Visual Studio or MSBuild.
	+
	+However, only one build configuration (besides Debug or Release) is supported:
	+extra math and prompt enabled, history and NLS (locale support) disabled, with
	+both calculators built.
	+
	+The library can also be built on Windows.
	+
	+### Visual Studio
	+
	+In Visual Studio, open up the solution file (`bc.sln` for `bc`, or `bcl.sln` for
	+the library), select the desired configuration, and build.
	+
	+### MSBuild
	+
	+To build with MSBuild, first, *be sure that you are using the MSBuild that comes
	+with Visual Studio*.
	+
	+To build `bc`, run the following from the root directory:
	+
	+```
	+msbuild -property:Configuration=<config> bc.sln
	+```
	+
	+where `<config>` is either one of `Debug` or `Release`.
	+
	+To build the library, run the following from the root directory:
	+
	+```
	+msbuild -property:Configuration=<config> bcl.sln
	+```
	+
	+where `<config>` is either one of `Debug` or `Release`.
	+
	+## POSIX-Compatible Systems
	+
	+Building `bc`, `dc`, and `bcl` (the library) is more complex than on Windows
	+because many build options are supported.
	+
	<a name="cross-compiling"/>

	-## Cross Compiling
	+### Cross Compiling

	To cross-compile this `bc`, an appropriate compiler must be present and assigned
	to the environment variable `HOSTCC` or `HOST_CC` (the two are equivalent,
	though `HOSTCC` is prioritized). This is in order to bootstrap core file(s), if
	the architectures are not compatible (i.e., unlike i686 on x86_64). Thus, the
	approach is:

	```
	HOSTCC="/path/to/native/compiler" ./configure.sh
	make
	make install
	```

	`HOST_CC` will work in exactly the same way.

	`HOSTCFLAGS` and `HOST_CFLAGS` can be used to set compiler flags for `HOSTCC`.
	(The two are equivalent, as `HOSTCC` and `HOST_CC` are.) `HOSTCFLAGS` is
	prioritized over `HOST_CFLAGS`. If neither are present, `HOSTCC` (or `HOST_CC`)
	uses `CFLAGS` (see [Build Environment Variables][4] for more details).

	It is expected that `CC` produces code for the target system and `HOSTCC`
	produces code for the host system. See [Build Environment Variables][4] for more
	details.

	If an emulator is necessary to run the bootstrap binaries, it can be set with
	the environment variable `GEN_EMU`.

	<a name="build-environment-variables"/>

	-## Build Environment Variables
	+### Build Environment Variables

	This `bc` supports `CC`, `HOSTCC`, `HOST_CC`, `CFLAGS`, `HOSTCFLAGS`,
	`HOST_CFLAGS`, `CPPFLAGS`, `LDFLAGS`, `LDLIBS`, `PREFIX`, `DESTDIR`, `BINDIR`,
	`DATAROOTDIR`, `DATADIR`, `MANDIR`, `MAN1DIR`, `LOCALEDIR` `EXECSUFFIX`,
	`EXECPREFIX`, `LONG_BIT`, `GEN_HOST`, and `GEN_EMU` environment variables in
	`configure.sh`. Any values of those variables given to `configure.sh` will be
	put into the generated Makefile.

	More detail on what those environment variables do can be found in the following
	sections.

	-### `CC`
	+#### `CC`

	C compiler for the target system. `CC` must be compatible with POSIX `c99`
	behavior and options. However, **I encourage users to use any C99 or C11
	compatible compiler they wish.**

	If there is a space in the basename of the compiler, the items after the first
	space are assumed to be compiler flags, and in that case, the flags are
	automatically moved into CFLAGS.

	Defaults to `c99`.

	### `HOSTCC` or `HOST_CC`

	C compiler for the host system, used only in [cross compiling][6]. Must be
	compatible with POSIX `c99` behavior and options.

	If there is a space in the basename of the compiler, the items after the first
	space are assumed to be compiler flags, and in that case, the flags are
	automatically moved into HOSTCFLAGS.

	Defaults to `$CC`.

	-### `CFLAGS`
	+#### `CFLAGS`

	Command-line flags that will be passed verbatim to `CC`.

	Defaults to empty.

	-### `HOSTCFLAGS` or `HOST_CFLAGS`
	+#### `HOSTCFLAGS` or `HOST_CFLAGS`

	Command-line flags that will be passed verbatim to `HOSTCC` or `HOST_CC`.

	Defaults to `$CFLAGS`.

	-### `CPPFLAGS`
	+#### `CPPFLAGS`

	Command-line flags for the C preprocessor. These are also passed verbatim to
	both compilers (`CC` and `HOSTCC`); they are supported just for legacy reasons.

	Defaults to empty.

	-### `LDFLAGS`
	+#### `LDFLAGS`

	Command-line flags for the linker. These are also passed verbatim to both
	compilers (`CC` and `HOSTCC`); they are supported just for legacy reasons.

	Defaults to empty.

	-### `LDLIBS`
	+#### `LDLIBS`

	Libraries to link to. These are also passed verbatim to both compilers (`CC` and
	`HOSTCC`); they are supported just for legacy reasons and for cross compiling
	with different C standard libraries (like [musl][3]).

	Defaults to empty.

	-### `PREFIX`
	+#### `PREFIX`

	The prefix to install to.

	Can be overridden by passing the `--prefix` option to `configure.sh`.

	Defaults to `/usr/local`.

	-### `DESTDIR`
	+#### `DESTDIR`

	Path to prepend onto `PREFIX`. This is mostly for distro and package
	maintainers.

	This can be passed either to `configure.sh` or `make install`. If it is passed
	to both, the one given to `configure.sh` takes precedence.

	Defaults to empty.

	-### `BINDIR`
	+#### `BINDIR`

	The directory to install binaries in.

	Can be overridden by passing the `--bindir` option to `configure.sh`.

	Defaults to `$PREFIX/bin`.

	-### `INCLUDEDIR`
	+#### `INCLUDEDIR`

	The directory to install header files in.

	Can be overridden by passing the `--includedir` option to `configure.sh`.

	Defaults to `$PREFIX/include`.

	-### `LIBDIR`
	+#### `LIBDIR`

	The directory to install libraries in.

	Can be overridden by passing the `--libdir` option to `configure.sh`.

	Defaults to `$PREFIX/lib`.

	-### `DATAROOTDIR`
	+#### `DATAROOTDIR`

	The root directory to install data files in.

	Can be overridden by passing the `--datarootdir` option to `configure.sh`.

	Defaults to `$PREFIX/share`.

	-### `DATADIR`
	+#### `DATADIR`

	The directory to install data files in.

	Can be overridden by passing the `--datadir` option to `configure.sh`.

	Defaults to `$DATAROOTDIR`.

	-### `MANDIR`
	+#### `MANDIR`

	The directory to install manpages in.

	Can be overridden by passing the `--mandir` option to `configure.sh`.

	Defaults to `$DATADIR/man`

	-### `MAN1DIR`
	+#### `MAN1DIR`

	The directory to install Section 1 manpages in. Because both `bc` and `dc` are
	Section 1 commands, this is the only relevant section directory.

	Can be overridden by passing the `--man1dir` option to `configure.sh`.

	Defaults to `$MANDIR/man1`.

	-### `LOCALEDIR`
	+#### `LOCALEDIR`

	The directory to install locales in.

	Can be overridden by passing the `--localedir` option to `configure.sh`.

	Defaults to `$DATAROOTDIR/locale`.

	-### `EXECSUFFIX`
	+#### `EXECSUFFIX`

	The suffix to append onto the executable names when installing. This is for
	packagers and distro maintainers who want this `bc` as an option, but do not
	want to replace the default `bc`.

	Defaults to empty.

	-### `EXECPREFIX`
	+#### `EXECPREFIX`

	The prefix to append onto the executable names when building and installing.
	This is for packagers and distro maintainers who want this `bc` as an option,
	but do not want to replace the default `bc`.

	Defaults to empty.

	-### `LONG_BIT`
	+#### `LONG_BIT`

	The number of bits in a C `long` type. This is mostly for the embedded space.

	This `bc` uses `long`s internally for overflow checking. In C99, a `long` is
	required to be 32 bits. For this reason, on 8-bit and 16-bit microcontrollers,
	the generated code to do math with `long` types may be inefficient.

	For most normal desktop systems, setting this is unnecessary, except that 32-bit
	platforms with 64-bit longs may want to set it to `32`.

	Defaults to the default value of `LONG_BIT` for the target platform. For
	compliance with the `bc` spec, the minimum allowed value is `32`.

	It is an error if the specified value is greater than the default value of
	`LONG_BIT` for the target platform.

	-### `GEN_HOST`
	+#### `GEN_HOST`

	Whether to use `gen/strgen.c`, instead of `gen/strgen.sh`, to produce the C
	files that contain the help texts as well as the math libraries. By default,
	`gen/strgen.c` is used, compiled by `$HOSTCC` and run on the host machine. Using
	`gen/strgen.sh` removes the need to compile and run an executable on the host
	machine since `gen/strgen.sh` is a POSIX shell script. However, `gen/lib2.bc` is
	perilously close to 4095 characters, the max supported length of a string
	literal in C99 (and it could be added to in the future), and `gen/strgen.sh`
	generates a string literal instead of an array, as `gen/strgen.c` does. For most
	production-ready compilers, this limit probably is not enforced, but it could
	be. Both options are still available for this reason.

	If you are sure your compiler does not have the limit and do not want to compile
	and run a binary on the host machine, set this variable to "0". Any other value,
	or a non-existent value, will cause the build system to compile and run
	`gen/strgen.c`.

	Default is "".

	-### `GEN_EMU`
	+#### `GEN_EMU`

	The emulator to run bootstrap binaries under. This is only if the binaries
	produced by `HOSTCC` (or `HOST_CC`) need to be run under an emulator to work.

	Defaults to empty.

	<a name="build-options"/>

	-## Build Options
	+### Build Options

	This `bc` comes with several build options, all of which are enabled by default.

	All options can be used with each other, with a few exceptions that will be
	noted below.

	NOTE: All long options with mandatory argumenst accept either one of the
	following forms:

	```
	--option arg
	--option=arg
	```

	-### Library
	+#### Library

	To build the math library, use the following commands for the configure step:

	```
	./configure.sh -a
	./configure.sh --library
	```

	Both commands are equivalent.

	When the library is built, history, prompt, and locales are disabled, and the
	functionality for `bc` and `dc` are both enabled, though the executables are
	not built. This is because the library's options clash with the executables.

	To build an optimized version of the library, users can pass optimization
	options to `configure.sh` or include them in `CFLAGS`.

	The library API can be found in `manuals/bcl.3.md` or `man bcl` once the library
	is installed.

	The library is built as `bin/libbcl.a`.

	-### `bc` Only
	+#### `bc` Only

	To build `bc` only (no `dc`), use any one of the following commands for the
	configure step:

	```
	./configure.sh -b
	./configure.sh --bc-only
	./configure.sh -D
	./configure.sh --disable-dc
	```

	Those commands are all equivalent.

	*Warning*: It is an error to use those options if `bc` has also been
	disabled (see below).

	-### `dc` Only
	+#### `dc` Only

	To build `dc` only (no `bc`), use either one of the following commands for the
	configure step:

	```
	./configure.sh -d
	./configure.sh --dc-only
	./configure.sh -B
	./configure.sh --disable-bc
	```

	Those commands are all equivalent.

	*Warning*: It is an error to use those options if `dc` has also been
	disabled (see above).

	<a name="build-history"/>

	-### History
	+#### History

	To disable signal handling, pass either the `-H` flag or the `--disable-history`
	option to `configure.sh`, as follows:

	```
	./configure.sh -H
	./configure.sh --disable-history
	```

	Both commands are equivalent.

	History is automatically disabled when building for Windows or on another
	platform that does not support the terminal handling that is required.

	*WARNING*: Of all of the code in the `bc`, this is the only code that is not
	completely portable. If the `bc` does not work on your platform, your first step
	should be to retry with history disabled.

	-### NLS (Locale Support)
	+#### NLS (Locale Support)

	To disable locale support (use only English), pass either the `-N` flag or the
	`--disable-nls` option to `configure.sh`, as follows:

	```
	./configure.sh -N
	./configure.sh --disable-nls
	```

	Both commands are equivalent.

	NLS (locale support) is automatically disabled when building for Windows or on
	another platform that does not support the POSIX locale API or utilities.

	-### Prompt
	+#### Prompt

	By default, `bc` and `dc` print a prompt when in interactive mode. They both
	have the command-line option `-P`/`--no-prompt`, which turns that off, but it
	can be disabled permanently in the build by passing the `-P` flag or the
	`--disable-prompt` option to `configure.sh`, as follows:

	```
	./configure.sh -P
	./configure.sh --disable-prompt
	```

	Both commands are equivalent.

	-### Locales
	+#### Locales

	By default, `bc` and `dc` do not install all locales, but only the enabled
	locales. If `DESTDIR` exists and is not empty, then they will install all of
	the locales that exist on the system. The `-l` flag or `--install-all-locales`
	option skips all of that and just installs all of the locales that `bc` and `dc`
	have, regardless. To enable that behavior, you can pass the `-l` flag or the
	`--install-all-locales` option to `configure.sh`, as follows:

	```
	./configure.sh -l
	./configure.sh --install-all-locales
	```

	Both commands are equivalent.

	-### Extra Math
	+#### Extra Math

	This `bc` has 7 extra operators:

	* `$` (truncation to integer)
	* `@` (set precision)
	* `@=` (set precision and assign)
	* `<<` (shift number left, shifts radix right)
	* `<<=` (shift number left and assign)
	* `>>` (shift number right, shifts radix left)
	* `>>=` (shift number right and assign)

	There is no assignment version of `$` because it is a unary operator.

	The assignment versions of the above operators are not available in `dc`, but
	the others are, as the operators `$`, `@`, `H`, and `h`, respectively.

	In addition, this `bc` has the option of outputting in scientific notation or
	engineering notation. It can also take input in scientific or engineering
	notation. On top of that, it has a pseudo-random number generator. (See the
	full manual for more details.)

	Extra operators, scientific notation, engineering notation, and the
	pseudo-random number generator can be disabled by passing either the `-E` flag
	or the `--disable-extra-math` option to `configure.sh`, as follows:

	```
	./configure.sh -E
	./configure.sh --disable-extra-math
	```

	Both commands are equivalent.

	This `bc` also has a larger library that is only enabled if extra operators and
	the pseudo-random number generator are. More information about the functions can
	be found in the Extended Library section of the full manual.

	-### Manpages
	+#### Manpages

	To disable installing manpages, pass either the `-M` flag or the
	`--disable-man-pages` option to `configure.sh` as follows:

	```
	./configure.sh -M
	./configure.sh --disable-man-pages
	```

	Both commands are equivalent.

	-### Karatsuba Length
	+#### Karatsuba Length

	The Karatsuba length is the point at which `bc` and `dc` switch from Karatsuba
	multiplication to brute force, `O(n^2)` multiplication. It can be set by passing
	the `-k` flag or the `--karatsuba-len` option to `configure.sh` as follows:

	```
	./configure.sh -k64
	./configure.sh --karatsuba-len 64
	```

	Both commands are equivalent.

	Default is `64`.

	*WARNING: The Karatsuba Length must be a integer* greater than or equal
	to `16` (to prevent stack overflow). If it is not, `configure.sh` will give an
	error.

	-### Install Options
	+#### Install Options

	The relevant `autotools`-style install options are supported in `configure.sh`:

	* `--prefix`
	* `--bindir`
	* `--datarootdir`
	* `--datadir`
	* `--mandir`
	* `--man1dir`
	* `--localedir`

	An example is:

	```
	./configure.sh --prefix=/usr --localedir /usr/share/nls
	make
	make install
	```

	They correspond to the environment variables `$PREFIX`, `$BINDIR`,
	`$DATAROOTDIR`, `$DATADIR`, `$MANDIR`, `$MAN1DIR`, and `$LOCALEDIR`,
	respectively.

	*WARNING*: If the option is given, the value of the corresponding
	environment variable is overridden.

	*WARNING*: If any long command-line options are used, the long form of all
	other command-line options must be used. Mixing long and short options is not
	supported.

	-## Optimization
	+### Optimization

	The `configure.sh` script will accept an optimization level to pass to the
	compiler. Because `bc` is orders of magnitude faster with optimization, I
	*highly* recommend package and distro maintainers pass the highest
	optimization level available in `CC` to `configure.sh` with the `-O` flag or
	`--opt` option, as follows:

	```
	./configure.sh -O3
	./configure.sh --opt 3
	```

	Both commands are equivalent.

	The build and install can then be run as normal:

	```
	make
	make install
	```

	As usual, `configure.sh` will also accept additional `CFLAGS` on the command
	line, so for SSE4 architectures, the following can add a bit more speed:

	```
	CFLAGS="-march=native -msse4" ./configure.sh -O3
	make
	make install
	```

	Building with link-time optimization (`-flto` in clang) can further increase the
	performance. I *highly* recommend doing so.

	I do NOT* recommend building with `-march=native`; doing so reduces this
	`bc`'s performance.

	Manual stripping is not necessary; non-debug builds are automatically stripped
	in the link stage.

	-## Debug Builds
	+### Debug Builds

	Debug builds (which also disable optimization if no optimization level is given
	and if no extra `CFLAGS` are given) can be enabled with either the `-g` flag or
	the `--debug` option, as follows:

	```
	./configure.sh -g
	./configure.sh --debug
	```

	Both commands are equivalent.

	The build and install can then be run as normal:

	```
	make
	make install
	```

	-## Stripping Binaries
	+### Stripping Binaries

	By default, when `bc` and `dc` are not built in debug mode, the binaries are
	stripped. Stripping can be disabled with either the `-T` or the
	`--disable-strip` option, as follows:

	```
	./configure.sh -T
	./configure.sh --disable-strip
	```

	Both commands are equivalent.

	The build and install can then be run as normal:

	```
	make
	make install
	```

	-## Binary Size
	+### Binary Size

	When built with both calculators, all available features, and `-Os` using
	`clang` and `musl`, the executable is 140.4 kb (140,386 bytes) on `x86_64`. That
	isn't much for what is contained in the binary, but if necessary, it can be
	reduced.

	The single largest user of space is the `bc` calculator. If just `dc` is needed,
	the size can be reduced to 107.6 kb (107,584 bytes).

	The next largest user of space is history support. If that is not needed, size
	can be reduced (for a build with both calculators) to 119.9 kb (119,866 bytes).

	There are several reasons that history is a bigger user of space than `dc`
	itself:

	* `dc`'s lexer and parser are tiny compared to `bc`'s because `dc` code is
	almost already in the form that it is executed in, while `bc` has to not only
	adjust the form to be executable, it has to parse functions, loops, `if`
	statements, and other extra features.
	* `dc` does not have much extra code in the interpreter.
	* History has a lot of const data for supporting `UTF-8` terminals.
	* History pulls in a bunch of more code from the `libc`.

	The next biggest user is extra math support. Without it, the size is reduced to
	124.0 kb (123,986 bytes) with history and 107.6 kb (107,560 bytes) without
	history.

	The reasons why extra math support is bigger than `dc`, besides the fact that
	`dc` is small already, are:

	* Extra math supports adds an extra math library that takes several kilobytes of
	constant data space.
	* Extra math support includes support for a pseudo-random number generator,
	including the code to convert a series of pseudo-random numbers into a number
	of arbitrary size.
	* Extra math support adds several operators.

	The next biggest user is `dc`, so if just `bc` is needed, the size can be
	reduced to 128.1 kb (128,096 bytes) with history and extra math support, 107.6
	kb (107,576 bytes) without history and with extra math support, and 95.3 kb
	(95,272 bytes) without history and without extra math support.

	Note: all of these binary sizes were compiled using `musl` `1.2.0` as the
	`libc`, making a fully static executable, with `clang` `9.0.1` (well,
	`musl-clang` using `clang` `9.0.1`) as the compiler and using `-Os`
	optimizations. These builds were done on an `x86_64` machine running Gentoo
	Linux.

	-## Testing
	+### Testing

	The default test suite can be run with the following command:

	```
	make test
	```

	To test `bc` only, run the following command:

	```
	make test_bc
	```

	To test `dc` only, run the following command:

	```
	make test_dc
	```

	This `bc`, if built, assumes a working, GNU-compatible `bc`, installed on the
	system and in the `PATH`, to generate some tests, unless the `-G` flag or
	`--disable-generated-tests` option is given to `configure.sh`, as follows:

	```
	./configure.sh -G
	./configure.sh --disable-generated-tests
	```

	After running `configure.sh`, build and run tests as follows:

	```
	make
	make test
	```

	This `dc` also assumes a working, GNU-compatible `dc`, installed on the system
	and in the `PATH`, to generate some tests, unless one of the above options is
	given to `configure.sh`.

	To generate test coverage, pass the `-c` flag or the `--coverage` option to
	`configure.sh` as follows:

	```
	./configure.sh -c
	./configure.sh --coverage
	```

	Both commands are equivalent.

	*WARNING*: Both `bc` and `dc` must be built for test coverage. Otherwise,
	`configure.sh` will give an error.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	[2]: https://www.gnu.org/software/bc/
	[3]: https://www.musl-libc.org/
	[4]: #build-environment-variables
	[5]: #build-options
	[6]: #cross-compiling
	diff --git a/contrib/bc/manuals/dc.1.md.in b/contrib/bc/manuals/dc.1.md.in
	index c5c361fe271a..56417d73f9dd 100644
	--- a/contrib/bc/manuals/dc.1.md.in
	+++ b/contrib/bc/manuals/dc.1.md.in
	@@ -1,1270 +1,1289 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	{{ A E H N EH EN HN EHN }}
	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.
	{{ end }}
	{{ P EP HP NP EHP ENP HNP EHNP }}
	: This option is a no-op.
	{{ end }}

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+{{ A E H N EH EN HN EHN }}
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+{{ end }}
	+{{ P EP HP NP EHP ENP HNP EHNP }}
	+: This option is a no-op.
	+{{ end }}
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	{{ A H N P HN HP NP HNP }}
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	value for obase is 2. Values are output in the specified base.
	{{ end }}

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	{{ A H N P HN HP NP HNP }}
	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.
	{{ end }}

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	{{ A H N P HN HP NP HNP }}
	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.
	{{ end }}

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	{{ A H N P HN HP NP HNP }}
	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.
	{{ end }}

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	{{ A H N P HN HP NP HNP }}
	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.
	{{ end }}

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	{{ A H N P HN HP NP HNP }}
	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.
	{{ end }}

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	{{ A H N P HN HP NP HNP }}
	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.
	{{ end }}

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	{{ A H N P HN HP NP HNP }}
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).
	{{ end }}

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	{{ A H N P HN HP NP HNP }}
	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.
	{{ end }}

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	{{ A H N P HN HP NP HNP }}
	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.
	{{ end }}

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	{{ A H N P HN HP NP HNP }}
	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.
	{{ end }}

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	{{ A H N P HN HP NP HNP }}
	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.
	{{ end }}

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	{{ A H N P HN HP NP HNP }}
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.
	{{ end }}
	{{ E EH EN EP EHN EHP ENP EHNP }}
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.
	{{ end }}

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	{{ A E N P EN EP NP ENP }}
	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.
	{{ end }}

	{{ A E H N EH EN HN EHN }}
	The prompt is enabled in TTY mode.
	{{ end }}

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	{{ A E N P EN EP NP ENP }}
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.
	{{ end }}
	{{ H EH HN HP EHN EHP HNP EHNP }}
	default handler for all other signals.
	{{ end }}

	{{ A E N P EN EP NP ENP }}
	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.
	{{ end }}

	{{ A E H P EH EP HP EHP }}
	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.
	{{ end }}

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/A.1 b/contrib/bc/manuals/dc/A.1
	index 7b91c02039e4..67bcf9e86d9f 100644
	--- a/contrib/bc/manuals/dc/A.1
	+++ b/contrib/bc/manuals/dc/A.1
	@@ -1,1350 +1,1572 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-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]--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]--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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/A.1.md b/contrib/bc/manuals/dc/A.1.md
	index e53646c2fba3..8b78f48c8ded 100644
	--- a/contrib/bc/manuals/dc/A.1.md
	+++ b/contrib/bc/manuals/dc/A.1.md
	@@ -1,1207 +1,1221 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/E.1 b/contrib/bc/manuals/dc/E.1
	index ebe8db87e996..e65a29fe8db2 100644
	--- a/contrib/bc/manuals/dc/E.1
	+++ b/contrib/bc/manuals/dc/E.1
	@@ -1,1142 +1,1343 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/E.1.md b/contrib/bc/manuals/dc/E.1.md
	index 5e0a85af9a90..641a3736878f 100644
	--- a/contrib/bc/manuals/dc/E.1.md
	+++ b/contrib/bc/manuals/dc/E.1.md
	@@ -1,1040 +1,1054 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EH.1 b/contrib/bc/manuals/dc/EH.1
	index e8e4b9069506..9676eeaba1cb 100644
	--- a/contrib/bc/manuals/dc/EH.1
	+++ b/contrib/bc/manuals/dc/EH.1
	@@ -1,1127 +1,1328 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EH.1.md b/contrib/bc/manuals/dc/EH.1.md
	index 6d1413d0dae4..3bdef59ef917 100644
	--- a/contrib/bc/manuals/dc/EH.1.md
	+++ b/contrib/bc/manuals/dc/EH.1.md
	@@ -1,1027 +1,1041 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EHN.1 b/contrib/bc/manuals/dc/EHN.1
	index 37f4a6656c65..8aa8f2460216 100644
	--- a/contrib/bc/manuals/dc/EHN.1
	+++ b/contrib/bc/manuals/dc/EHN.1
	@@ -1,1123 +1,1324 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EHN.1.md b/contrib/bc/manuals/dc/EHN.1.md
	index 2e24a10a06dc..fc49cc7187c3 100644
	--- a/contrib/bc/manuals/dc/EHN.1.md
	+++ b/contrib/bc/manuals/dc/EHN.1.md
	@@ -1,1022 +1,1036 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EHNP.1 b/contrib/bc/manuals/dc/EHNP.1
	index f0ea848f819b..be491096703f 100644
	--- a/contrib/bc/manuals/dc/EHNP.1
	+++ b/contrib/bc/manuals/dc/EHNP.1
	@@ -1,1116 +1,1307 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EHNP.1.md b/contrib/bc/manuals/dc/EHNP.1.md
	index 5abed62294c2..edbf30b272e1 100644
	--- a/contrib/bc/manuals/dc/EHNP.1.md
	+++ b/contrib/bc/manuals/dc/EHNP.1.md
	@@ -1,1017 +1,1023 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EHP.1 b/contrib/bc/manuals/dc/EHP.1
	index 654c24309c56..797f0ef2bcfb 100644
	--- a/contrib/bc/manuals/dc/EHP.1
	+++ b/contrib/bc/manuals/dc/EHP.1
	@@ -1,1120 +1,1311 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EHP.1.md b/contrib/bc/manuals/dc/EHP.1.md
	index 17ebe0420492..d890cc3a0c72 100644
	--- a/contrib/bc/manuals/dc/EHP.1.md
	+++ b/contrib/bc/manuals/dc/EHP.1.md
	@@ -1,1022 +1,1028 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EN.1 b/contrib/bc/manuals/dc/EN.1
	index 6d522efdde45..242306dab617 100644
	--- a/contrib/bc/manuals/dc/EN.1
	+++ b/contrib/bc/manuals/dc/EN.1
	@@ -1,1138 +1,1339 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EN.1.md b/contrib/bc/manuals/dc/EN.1.md
	index 4c0297fdab7f..dbd7e8d8e52d 100644
	--- a/contrib/bc/manuals/dc/EN.1.md
	+++ b/contrib/bc/manuals/dc/EN.1.md
	@@ -1,1035 +1,1049 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/ENP.1 b/contrib/bc/manuals/dc/ENP.1
	index c9659423dc26..4f23bebed353 100644
	--- a/contrib/bc/manuals/dc/ENP.1
	+++ b/contrib/bc/manuals/dc/ENP.1
	@@ -1,1131 +1,1322 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/ENP.1.md b/contrib/bc/manuals/dc/ENP.1.md
	index 4025c643b956..a2facd8d8cdd 100644
	--- a/contrib/bc/manuals/dc/ENP.1.md
	+++ b/contrib/bc/manuals/dc/ENP.1.md
	@@ -1,1030 +1,1036 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/EP.1 b/contrib/bc/manuals/dc/EP.1
	index 1dd0da3235e7..ad6277c249b0 100644
	--- a/contrib/bc/manuals/dc/EP.1
	+++ b/contrib/bc/manuals/dc/EP.1
	@@ -1,1135 +1,1326 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]2\f[R].
	Values are output in the specified base.
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	and \f[B]scale\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]2\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	+.PP
	\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	+.PP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	-stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]) operator.
	+\f[R]
	+.fi
	.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, attempting to convert a negative number to a hardware
	-integer, overflow when converting a number to a hardware integer, and
	-attempting to use a non-integer where an integer is required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]) operator.
	-.RE
	-.TP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/EP.1.md b/contrib/bc/manuals/dc/EP.1.md
	index fcb15291262d..32b7f35fe92e 100644
	--- a/contrib/bc/manuals/dc/EP.1.md
	+++ b/contrib/bc/manuals/dc/EP.1.md
	@@ -1,1035 +1,1041 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 2. Values are output in the specified base.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, and scale. Also
	see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 2 and DC_BASE_MAX, inclusive (see the
	LIMITS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^) operator.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/H.1 b/contrib/bc/manuals/dc/H.1
	index 15fe0edb0d2d..9d7ef21b3d1f 100644
	--- a/contrib/bc/manuals/dc/H.1
	+++ b/contrib/bc/manuals/dc/H.1
	@@ -1,1335 +1,1557 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-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]--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]--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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/H.1.md b/contrib/bc/manuals/dc/H.1.md
	index de83e3088f9c..0114f7556a49 100644
	--- a/contrib/bc/manuals/dc/H.1.md
	+++ b/contrib/bc/manuals/dc/H.1.md
	@@ -1,1194 +1,1208 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/HN.1 b/contrib/bc/manuals/dc/HN.1
	index a617bb473ec1..c04b7463f6bc 100644
	--- a/contrib/bc/manuals/dc/HN.1
	+++ b/contrib/bc/manuals/dc/HN.1
	@@ -1,1331 +1,1553 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-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]--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]--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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/HN.1.md b/contrib/bc/manuals/dc/HN.1.md
	index 005579cd02c8..92f040cffb13 100644
	--- a/contrib/bc/manuals/dc/HN.1.md
	+++ b/contrib/bc/manuals/dc/HN.1.md
	@@ -1,1189 +1,1203 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/HNP.1 b/contrib/bc/manuals/dc/HNP.1
	index 7eb4b8b19f3d..bec07f5ad64f 100644
	--- a/contrib/bc/manuals/dc/HNP.1
	+++ b/contrib/bc/manuals/dc/HNP.1
	@@ -1,1324 +1,1536 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	-.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/HNP.1.md b/contrib/bc/manuals/dc/HNP.1.md
	index d099d6f9cdcf..a93b3271ec85 100644
	--- a/contrib/bc/manuals/dc/HNP.1.md
	+++ b/contrib/bc/manuals/dc/HNP.1.md
	@@ -1,1184 +1,1190 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/HP.1 b/contrib/bc/manuals/dc/HP.1
	index cea646c8a3f3..a28ee9a9cae2 100644
	--- a/contrib/bc/manuals/dc/HP.1
	+++ b/contrib/bc/manuals/dc/HP.1
	@@ -1,1328 +1,1540 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	-.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/HP.1.md b/contrib/bc/manuals/dc/HP.1.md
	index 93938790f460..dcc59f1896d5 100644
	--- a/contrib/bc/manuals/dc/HP.1.md
	+++ b/contrib/bc/manuals/dc/HP.1.md
	@@ -1,1189 +1,1195 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/N.1 b/contrib/bc/manuals/dc/N.1
	index 6f4f01c48354..41cc7449c3a6 100644
	--- a/contrib/bc/manuals/dc/N.1
	+++ b/contrib/bc/manuals/dc/N.1
	@@ -1,1346 +1,1568 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-Disables the prompt in TTY mode.
	+.PP
	+: 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
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	do not want a prompt or are not used to having them in dc(1).
	Most of those users would want to put this option in
	\f[B]DC_ENV_ARGS\f[R].
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: Disables the read prompt in TTY mode.
	+(The read prompt is only enabled in TTY mode.
	+See the \f[B]TTY MODE\f[R] section.) This is mostly for those users that
	+do not want a read prompt or are not used to having them in dc(1).
	+Most of those users would want to put this option in
	+\f[B]BC_ENV_ARGS\f[R] (see the \f[B]ENVIRONMENT VARIABLES\f[R] section).
	+This option is also useful in hash bang lines of dc(1) scripts that
	+prompt for user input.
	+.IP
	+.nf
	+\f[C]
	+This option does not disable the regular prompt because the read prompt is
	+only used when the ? command is used.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-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]--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]--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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	The prompt is enabled in TTY mode.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/N.1.md b/contrib/bc/manuals/dc/N.1.md
	index 43876cfb24a6..d790c960b5c7 100644
	--- a/contrib/bc/manuals/dc/N.1.md
	+++ b/contrib/bc/manuals/dc/N.1.md
	@@ -1,1202 +1,1216 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	: Disables the prompt in TTY mode. (The prompt is only enabled in TTY mode.
	- See the TTY MODE section) This is mostly for those users that do not
	+ See the TTY MODE section.) This is mostly for those users that do not
	want a prompt or are not used to having them in dc(1). Most of those users
	would want to put this option in DC_ENV_ARGS.

	This is a non-portable extension.

	+-R, -\-no-read-prompt
	+
	+: Disables the read prompt in TTY mode. (The read prompt is only enabled in
	+ TTY mode. See the TTY MODE section.) This is mostly for those users that
	+ do not want a read prompt or are not used to having them in dc(1). Most of
	+ those users would want to put this option in BC_ENV_ARGS (see the
	+ ENVIRONMENT VARIABLES section). This option is also useful in hash bang
	+ lines of dc(1) scripts that prompt for user input.
	+
	+ This option does not disable the regular prompt because the read prompt is
	+ only used when the ? command is used.
	+
	+ This is a non-portable extension.
	+
	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	The prompt is enabled in TTY mode.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/NP.1 b/contrib/bc/manuals/dc/NP.1
	index ad4a69957c1c..75a56bbe3538 100644
	--- a/contrib/bc/manuals/dc/NP.1
	+++ b/contrib/bc/manuals/dc/NP.1
	@@ -1,1339 +1,1551 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	-.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/NP.1.md b/contrib/bc/manuals/dc/NP.1.md
	index b1f29d76f06e..4533a534e84c 100644
	--- a/contrib/bc/manuals/dc/NP.1.md
	+++ b/contrib/bc/manuals/dc/NP.1.md
	@@ -1,1197 +1,1203 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/dc/P.1 b/contrib/bc/manuals/dc/P.1
	index 2bbe54c37604..6ee6d0f7bd2f 100644
	--- a/contrib/bc/manuals/dc/P.1
	+++ b/contrib/bc/manuals/dc/P.1
	@@ -1,1343 +1,1555 @@
	.\"
	.\" SPDX-License-Identifier: BSD-2-Clause
	.\"
	.\" Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	.\"
	.\" Redistribution and use in source and binary forms, with or without
	.\" modification, are permitted provided that the following conditions are met:
	.\"
	.\" * Redistributions of source code must retain the above copyright notice,
	.\" this list of conditions and the following disclaimer.
	.\"
	.\" * 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.
	.\"
	.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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 "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 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]--version\f[R]]
	+\f[B]dc\f[R] [\f[B]-hiPRvVx\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]\&...]
	+[\f[B]--no-read-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
	dc(1) is an arbitrary-precision calculator.
	It uses a stack (reverse Polish notation) to store numbers and results
	of computations.
	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]--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]--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
	VARIABLES\f[R] section).
	Any expressions given on the command-line should be used to set up a
	standard environment.
	For example, if a user wants the \f[B]scale\f[R] always set to
	\f[B]10\f[R], they can set \f[B]DC_ENV_ARGS\f[R] to \f[B]-e 10k\f[R],
	and this dc(1) will always start with a \f[B]scale\f[R] of \f[B]10\f[R].
	.PP
	If users want to have dc(1) exit after processing all input from
	\f[B]-e\f[R] and \f[B]-f\f[R] arguments (and their equivalents), then
	they can just simply add \f[B]-e q\f[R] as the last command-line
	argument or define the environment variable \f[B]DC_EXPR_EXIT\f[R].
	.SH OPTIONS
	.PP
	The following are the options that dc(1) accepts.
	-.TP
	+.PP
	\f[B]-h\f[R], \f[B]--help\f[R]
	-Prints a usage message and quits.
	-.TP
	+.PP
	+: Prints a usage message and quits.
	+.PP
	\f[B]-v\f[R], \f[B]-V\f[R], \f[B]--version\f[R]
	-Print the version information (copyright header) and exit.
	-.TP
	+.PP
	+: Print the version information (copyright header) and exit.
	+.PP
	\f[B]-i\f[R], \f[B]--interactive\f[R]
	-Forces interactive mode.
	+.PP
	+: Forces interactive mode.
	(See the \f[B]INTERACTIVE MODE\f[R] section.)
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]-P\f[R], \f[B]--no-prompt\f[R]
	-This option is a no-op.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	+\f[B]-R\f[R], \f[B]--no-read-prompt\f[R]
	+.PP
	+: This option is a no-op.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]-x\f[R] \f[B]--extended-register\f[R]
	-Enables extended register mode.
	+.PP
	+: 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.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\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].
	+.PP
	+: 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
	evaluated in the order given.
	This means that if a file is given before an expression, the file is
	read in and evaluated first.
	-.RS
	-.PP
	-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]--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]--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.
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file, whether on the
	+command-line or in DC_ENV_ARGS. However, if any other -e,
	+-\[rs]-expression, -f, or -\[rs]-file arguments are given after -f-
	+or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.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]--file\f[R]=\f[I]file\f[R]
	-Reads in \f[I]file\f[R] and evaluates it, line by line, as though it
	+.PP
	+: 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
	in the order given.
	-.RS
	-.PP
	-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]--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
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	+see the ENVIRONMENT VARIABLES section), then after processing all
	+expressions and files, dc(1) will exit, unless - (stdin) was given
	+as an argument at least once to -f or -\[rs]-file. However, if any other
	+-e, -\[rs]-expression, -f, or -\[rs]-file arguments are given after
	+-f- or equivalent is given, dc(1) will give a fatal error and exit.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	All long options are \f[B]non-portable extensions\f[R].
	.SH STDOUT
	.PP
	Any non-error output is written to \f[B]stdout\f[R].
	In addition, if history (see the \f[B]HISTORY\f[R] section) and the
	prompt (see the \f[B]TTY MODE\f[R] section) are enabled, both are output
	to \f[B]stdout\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stdout\f[R], so if \f[B]stdout\f[R] is closed, as in
	\f[B]dc >&-\f[R], it will quit with an error.
	This is done so that dc(1) can report problems when \f[B]stdout\f[R] is
	redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stdout\f[R] to \f[B]/dev/null\f[R].
	.SH STDERR
	.PP
	Any error output is written to \f[B]stderr\f[R].
	.PP
	\f[B]Note\f[R]: Unlike other dc(1) implementations, this dc(1) will
	issue a fatal error (see the \f[B]EXIT STATUS\f[R] section) if it cannot
	write to \f[B]stderr\f[R], so if \f[B]stderr\f[R] is closed, as in
	\f[B]dc 2>&-\f[R], it will quit with an error.
	This is done so that dc(1) can exit with an error code when
	\f[B]stderr\f[R] is redirected to a file.
	.PP
	If there are scripts that depend on the behavior of other dc(1)
	implementations, it is recommended that those scripts be changed to
	redirect \f[B]stderr\f[R] to \f[B]/dev/null\f[R].
	.SH SYNTAX
	.PP
	Each item in the input source code, either a number (see the
	\f[B]NUMBERS\f[R] section) or a command (see the \f[B]COMMANDS\f[R]
	section), is processed and executed, in order.
	Input is processed immediately when entered.
	.PP
	\f[B]ibase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to interpret constant numbers.
	-It is the \[lq]input\[rq] base, or the number base used for interpreting
	+It is the \[dq]input\[dq] base, or the number base used for interpreting
	input numbers.
	\f[B]ibase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]ibase\f[R] is \f[B]16\f[R].
	The min allowable value for \f[B]ibase\f[R] is \f[B]2\f[R].
	The max allowable value for \f[B]ibase\f[R] can be queried in dc(1)
	programs with the \f[B]T\f[R] command.
	.PP
	\f[B]obase\f[R] is a register (see the \f[B]REGISTERS\f[R] section) that
	determines how to output results.
	-It is the \[lq]output\[rq] base, or the number base used for outputting
	+It is the \[dq]output\[dq] base, or the number base used for outputting
	numbers.
	\f[B]obase\f[R] is initially \f[B]10\f[R].
	The max allowable value for \f[B]obase\f[R] is \f[B]DC_BASE_MAX\f[R] and
	can be queried with the \f[B]U\f[R] command.
	The min allowable value for \f[B]obase\f[R] is \f[B]0\f[R].
	If \f[B]obase\f[R] is \f[B]0\f[R], values are output in scientific
	notation, and if \f[B]obase\f[R] is \f[B]1\f[R], values are output in
	engineering notation.
	Otherwise, values are output in the specified base.
	.PP
	Outputting in scientific and engineering notations are \f[B]non-portable
	extensions\f[R].
	.PP
	The \f[I]scale\f[R] of an expression is the number of digits in the
	result of the expression right of the decimal point, and \f[B]scale\f[R]
	is a register (see the \f[B]REGISTERS\f[R] section) that sets the
	precision of any operations (with exceptions).
	\f[B]scale\f[R] is initially \f[B]0\f[R].
	\f[B]scale\f[R] cannot be negative.
	The max allowable value for \f[B]scale\f[R] can be queried in dc(1)
	programs with the \f[B]V\f[R] command.
	.PP
	\f[B]seed\f[R] is a register containing the current seed for the
	pseudo-random number generator.
	If the current value of \f[B]seed\f[R] is queried and stored, then if it
	is assigned to \f[B]seed\f[R] later, the pseudo-random number generator
	is guaranteed to produce the same sequence of pseudo-random numbers that
	were generated after the value of \f[B]seed\f[R] was first queried.
	.PP
	Multiple values assigned to \f[B]seed\f[R] can produce the same sequence
	of pseudo-random numbers.
	Likewise, when a value is assigned to \f[B]seed\f[R], it is not
	guaranteed that querying \f[B]seed\f[R] immediately after will return
	the same value.
	In addition, the value of \f[B]seed\f[R] will change after any call to
	-the \f[B]\[cq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	+the \f[B]\[aq]\f[R] command or the \f[B]\[dq]\f[R] command that does not
	get receive a value of \f[B]0\f[R] or \f[B]1\f[R].
	-The maximum integer returned by the \f[B]\[cq]\f[R] command can be
	+The maximum integer returned by the \f[B]\[aq]\f[R] command can be
	queried with the \f[B]W\f[R] command.
	.PP
	\f[B]Note\f[R]: The values returned by the pseudo-random number
	-generator with the \f[B]\[cq]\f[R] and \f[B]\[dq]\f[R] commands are
	+generator with the \f[B]\[aq]\f[R] and \f[B]\[dq]\f[R] commands are
	guaranteed to \f[B]NOT\f[R] be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator.
	However, they \f[I]are\f[R] guaranteed to be reproducible with identical
	\f[B]seed\f[R] values.
	This means that the pseudo-random values from dc(1) should only be used
	where a reproducible stream of pseudo-random numbers is
	\f[I]ESSENTIAL\f[R].
	In any other case, use a non-seeded pseudo-random number generator.
	.PP
	The pseudo-random number generator, \f[B]seed\f[R], and all associated
	operations are \f[B]non-portable extensions\f[R].
	.SS Comments
	.PP
	Comments go from \f[B]#\f[R] until, and not including, the next newline.
	This is a \f[B]non-portable extension\f[R].
	.SH NUMBERS
	.PP
	Numbers are strings made up of digits, uppercase letters up to
	\f[B]F\f[R], and at most \f[B]1\f[R] period for a radix.
	Numbers can have up to \f[B]DC_NUM_MAX\f[R] digits.
	Uppercase letters are equal to \f[B]9\f[R] + their position in the
	alphabet (i.e., \f[B]A\f[R] equals \f[B]10\f[R], or \f[B]9+1\f[R]).
	If a digit or letter makes no sense with the current value of
	\f[B]ibase\f[R], they are set to the value of the highest valid digit in
	\f[B]ibase\f[R].
	.PP
	Single-character numbers (i.e., \f[B]A\f[R] alone) take the value that
	they would have if they were valid digits, regardless of the value of
	\f[B]ibase\f[R].
	This means that \f[B]A\f[R] alone always equals decimal \f[B]10\f[R] and
	\f[B]F\f[R] alone always equals decimal \f[B]15\f[R].
	.PP
	In addition, dc(1) accepts numbers in scientific notation.
	These have the form \f[B]<number>e<integer>\f[R].
	The exponent (the portion after the \f[B]e\f[R]) must be an integer.
	An example is \f[B]1.89237e9\f[R], which is equal to
	\f[B]1892370000\f[R].
	Negative exponents are also allowed, so \f[B]4.2890e_3\f[R] is equal to
	\f[B]0.0042890\f[R].
	.PP
	\f[B]WARNING\f[R]: Both the number and the exponent in scientific
	notation are interpreted according to the current \f[B]ibase\f[R], but
	the number is still multiplied by \f[B]10\[ha]exponent\f[R] regardless
	of the current \f[B]ibase\f[R].
	For example, if \f[B]ibase\f[R] is \f[B]16\f[R] and dc(1) is given the
	number string \f[B]FFeA\f[R], the resulting decimal number will be
	\f[B]2550000000000\f[R], and if dc(1) is given the number string
	\f[B]10e_4\f[R], the resulting decimal number will be \f[B]0.0016\f[R].
	.PP
	Accepting input as scientific notation is a \f[B]non-portable
	extension\f[R].
	.SH COMMANDS
	.PP
	The valid commands are listed below.
	.SS Printing
	.PP
	These commands are used for printing.
	.PP
	Note that both scientific notation and engineering notation are
	available for printing numbers.
	Scientific notation is activated by assigning \f[B]0\f[R] to
	\f[B]obase\f[R] using \f[B]0o\f[R], and engineering notation is
	activated by assigning \f[B]1\f[R] to \f[B]obase\f[R] using
	\f[B]1o\f[R].
	To deactivate them, just assign a different value to \f[B]obase\f[R].
	.PP
	Printing numbers in scientific notation and/or engineering notation is a
	\f[B]non-portable extension\f[R].
	-.TP
	+.PP
	\f[B]p\f[R]
	-Prints the value on top of the stack, whether number or string, and
	-prints a newline after.
	-.RS
	.PP
	+: Prints the value on top of the stack, whether number or string, and
	+prints a newline after.
	+.IP
	+.nf
	+\f[C]
	This does not alter the stack.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]n\f[R]
	-Prints the value on top of the stack, whether number or string, and pops
	-it off of the stack.
	-.TP
	+.PP
	+: Prints the value on top of the stack, whether number or string, and
	+pops it off of the stack.
	+.PP
	\f[B]P\f[R]
	-Pops a value off the stack.
	-.RS
	.PP
	+: Pops a value off the stack.
	+.IP
	+.nf
	+\f[C]
	If the value is a number, it is truncated and the absolute value of the
	-result is printed as though \f[B]obase\f[R] is \f[B]UCHAR_MAX+1\f[R] and
	-each digit is interpreted as an ASCII character, making it a byte
	-stream.
	-.PP
	+result is printed as though obase is UCHAR_MAX+1 and each digit is
	+interpreted as an ASCII character, making it a byte stream.
	+
	If the value is a string, it is printed without a trailing newline.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]f\f[R]
	-Prints the entire contents of the stack, in order from newest to oldest,
	-without altering anything.
	-.RS
	.PP
	+: Prints the entire contents of the stack, in order from newest to
	+oldest, without altering anything.
	+.IP
	+.nf
	+\f[C]
	Users should use this command when they get lost.
	-.RE
	+\f[R]
	+.fi
	.SS Arithmetic
	.PP
	These are the commands used for arithmetic.
	-.TP
	+.PP
	\f[B]+\f[R]
	-The top two values are popped off the stack, added, and the result is
	+.PP
	+: The top two values are popped off the stack, added, and the result is
	pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]-\f[R]
	-The top two values are popped off the stack, subtracted, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, subtracted, and the
	+result is pushed onto the stack.
	The \f[I]scale\f[R] of the result is equal to the max \f[I]scale\f[R] of
	both operands.
	-.TP
	+.PP
	\f[B]*\f[R]
	-The top two values are popped off the stack, multiplied, and the result
	-is pushed onto the stack.
	+.PP
	+: The top two values are popped off the stack, multiplied, and the
	+result is pushed onto the stack.
	If \f[B]a\f[R] is the \f[I]scale\f[R] of the first expression and
	\f[B]b\f[R] is the \f[I]scale\f[R] of the second expression, the
	\f[I]scale\f[R] of the result is equal to
	\f[B]min(a+b,max(scale,a,b))\f[R] where \f[B]min()\f[R] and
	\f[B]max()\f[R] return the obvious values.
	-.TP
	+.PP
	\f[B]/\f[R]
	-The top two values are popped off the stack, divided, and the result is
	-pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	-The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	-\f[B]%\f[R]
	-The top two values are popped off the stack, remaindered, and the result
	+: The top two values are popped off the stack, divided, and the result
	is pushed onto the stack.
	-.RS
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be non-zero.
	+\f[R]
	+.fi
	.PP
	-Remaindering is equivalent to 1) Computing \f[B]a/b\f[R] to current
	-\f[B]scale\f[R], and 2) Using the result of step 1 to calculate
	-\f[B]a-(a/b)*b\f[R] to \f[I]scale\f[R]
	-\f[B]max(scale+scale(b),scale(a))\f[R].
	+\f[B]%\f[R]
	.PP
	+: The top two values are popped off the stack, remaindered, and the
	+result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	+Remaindering is equivalent to 1) Computing a/b to current scale, and
	+2) Using the result of step 1 to calculate *a-(a/b)\[rs]b** to scale
	+max(scale+scale(b),scale(a)).
	+
	The first value popped off of the stack must be non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]\[ti]\f[R]
	-The top two values are popped off the stack, divided and remaindered,
	+.PP
	+: The top two values are popped off the stack, divided and remaindered,
	and the results (divided first, remainder second) are pushed onto the
	stack.
	This is equivalent to \f[B]x y / x y %\f[R] except that \f[B]x\f[R] and
	\f[B]y\f[R] are only evaluated once.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be non-zero.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[ha]\f[R]
	-The top two values are popped off the stack, the second is raised to the
	-power of the first, and the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top two values are popped off the stack, the second is raised to
	+the power of the first, and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]v\f[R]
	-The top value is popped off the stack, its square root is computed, and
	-the result is pushed onto the stack.
	-The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	-.RS
	.PP
	+: The top value is popped off the stack, its square root is computed,
	+and the result is pushed onto the stack.
	+The \f[I]scale\f[R] of the result is equal to \f[B]scale\f[R].
	+.IP
	+.nf
	+\f[C]
	The value popped off of the stack must be non-negative.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]_\f[R]
	-If this command \f[I]immediately\f[R] precedes a number (i.e., no spaces
	-or other commands), then that number is input as a negative number.
	-.RS
	-.PP
	-Otherwise, the top value on the stack is popped and copied, and the copy
	-is negated and pushed onto the stack.
	-This behavior without a number is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+.PP
	+: If this command \f[I]immediately\f[R] precedes a number (i.e., no
	+spaces or other commands), then that number is input as a negative
	+number.
	+.IP
	+.nf
	+\f[C]
	+Otherwise, the top value on the stack is popped and copied, and the copy is
	+negated and pushed onto the stack. This behavior without a number is a
	+non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]b\f[R]
	-The top value is popped off the stack, and if it is zero, it is pushed
	+.PP
	+: The top value is popped off the stack, and if it is zero, it is pushed
	back onto the stack.
	Otherwise, its absolute value is pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\|\f[R]
	-The top three values are popped off the stack, a modular exponentiation
	-is computed, and the result is pushed onto the stack.
	-.RS
	.PP
	+: The top three values are popped off the stack, a modular
	+exponentiation is computed, and the result is pushed onto the stack.
	+.IP
	+.nf
	+\f[C]
	The first value popped is used as the reduction modulus and must be an
	-integer and non-zero.
	-The second value popped is used as the exponent and must be an integer
	-and non-negative.
	-The third value popped is the base and must be an integer.
	+integer and non-zero. The second value popped is used as the exponent and
	+must be an integer and non-negative. The third value popped is the base and
	+must be an integer.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]$\f[R]
	-The top value is popped off the stack and copied, and the copy is
	+.PP
	+: The top value is popped off the stack and copied, and the copy is
	truncated and pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[at]\f[R]
	-The top two values are popped off the stack, and the precision of the
	+.PP
	+: The top two values are popped off the stack, and the precision of the
	second is set to the value of the first, whether by truncation or
	extension.
	-.RS
	-.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]H\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-left (radix shifted right) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+left (radix shifted right) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]h\f[R]
	-The top two values are popped off the stack, and the second is shifted
	-right (radix shifted left) to the value of the first.
	-.RS
	.PP
	-The first value popped off of the stack must be an integer and
	-non-negative.
	+: The top two values are popped off the stack, and the second is shifted
	+right (radix shifted left) to the value of the first.
	+.IP
	+.nf
	+\f[C]
	+The first value popped off of the stack must be an integer and non-negative.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]G\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if they are equal, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]N\f[R]
	-The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	+.PP
	+: The top value is popped off of the stack, and if it a \f[B]0\f[R], a
	\f[B]1\f[R] is pushed; otherwise, a \f[B]0\f[R] is pushed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B](\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]{\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is less than or equal to the second,
	-or \f[B]0\f[R] otherwise.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is less than or equal to the
	+second, or \f[B]0\f[R] otherwise.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B])\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than the second, or
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than the second, or
	\f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]}\f[R]
	-The top two values are popped off of the stack, they are compared, and a
	-\f[B]1\f[R] is pushed if the first is greater than or equal to the
	+.PP
	+: The top two values are popped off of the stack, they are compared, and
	+a \f[B]1\f[R] is pushed if the first is greater than or equal to the
	second, or \f[B]0\f[R] otherwise.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]M\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If they are both non-zero, a \f[B]1\f[R] is pushed onto the stack.
	If either of them is zero, or both of them are, then a \f[B]0\f[R] is
	pushed onto the stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is like the && operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is like the \f[B]&&\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]m\f[R]
	-The top two values are popped off of the stack.
	+.PP
	+: The top two values are popped off of the stack.
	If at least one of them is non-zero, a \f[B]1\f[R] is pushed onto the
	stack.
	If both of them are zero, then a \f[B]0\f[R] is pushed onto the stack.
	-.RS
	-.PP
	-This is like the \f[B]\|\|\f[R] operator in bc(1), and it is \f[I]not\f[R]
	-a short-circuit operator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+.IP
	+.nf
	+\f[C]
	+This is like the \|\| operator in bc(1), and it is not a short-circuit
	+operator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Pseudo-Random Number Generator
	.PP
	dc(1) has a built-in pseudo-random number generator.
	These commands query the pseudo-random number generator.
	(See Parameters for more information about the \f[B]seed\f[R] value that
	controls the pseudo-random number generator.)
	.PP
	The pseudo-random number generator is guaranteed to \f[B]NOT\f[R] be
	cryptographically secure.
	-.TP
	-\f[B]\[cq]\f[R]
	-Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive (see
	-the \f[B]LIMITS\f[R] section).
	-.RS
	.PP
	+\f[B]\[aq]\f[R]
	+.PP
	+: Generates an integer between 0 and \f[B]DC_RAND_MAX\f[R], inclusive
	+(see the \f[B]LIMITS\f[R] section).
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]\[dq]\f[R]
	-Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	+.PP
	+: Pops a value off of the stack, which is used as an \f[B]exclusive\f[R]
	upper bound on the integer that will be generated.
	If the bound is negative or is a non-integer, an error is raised, and
	dc(1) resets (see the \f[B]RESET\f[R] section) while \f[B]seed\f[R]
	remains unchanged.
	If the bound is larger than \f[B]DC_RAND_MAX\f[R], the higher bound is
	honored by generating several pseudo-random integers, multiplying them
	by appropriate powers of \f[B]DC_RAND_MAX+1\f[R], and adding them
	together.
	Thus, the size of integer that can be generated with this command is
	unbounded.
	Using this command will change the value of \f[B]seed\f[R], unless the
	operand is \f[B]0\f[R] or \f[B]1\f[R].
	In that case, \f[B]0\f[R] is pushed onto the stack, and \f[B]seed\f[R]
	is \f[I]not\f[R] changed.
	-.RS
	-.PP
	+.IP
	+.nf
	+\f[C]
	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.
	-.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Stack Control
	.PP
	These commands control the stack.
	-.TP
	+.PP
	\f[B]c\f[R]
	-Removes all items from (\[lq]clears\[rq]) the stack.
	-.TP
	+.PP
	+: Removes all items from (\[dq]clears\[dq]) the stack.
	+.PP
	\f[B]d\f[R]
	-Copies the item on top of the stack (\[lq]duplicates\[rq]) and pushes
	+.PP
	+: Copies the item on top of the stack (\[dq]duplicates\[dq]) and pushes
	the copy onto the stack.
	-.TP
	+.PP
	\f[B]r\f[R]
	-Swaps (\[lq]reverses\[rq]) the two top items on the stack.
	-.TP
	+.PP
	+: Swaps (\[dq]reverses\[dq]) the two top items on the stack.
	+.PP
	\f[B]R\f[R]
	-Pops (\[lq]removes\[rq]) the top value from the stack.
	+.PP
	+: Pops (\[dq]removes\[dq]) the top value from the stack.
	.SS Register Control
	.PP
	These commands control registers (see the \f[B]REGISTERS\f[R] section).
	-.TP
	+.PP
	\f[B]s\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack and stores it into register
	+.PP
	+: Pops the value off the top of the stack and stores it into register
	\f[I]r\f[R].
	-.TP
	+.PP
	\f[B]l\f[R]\f[I]r\f[R]
	-Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	+.PP
	+: Copies the value in register \f[I]r\f[R] and pushes it onto the stack.
	This does not alter the contents of \f[I]r\f[R].
	-.TP
	+.PP
	\f[B]S\f[R]\f[I]r\f[R]
	-Pops the value off the top of the (main) stack and pushes it onto the
	+.PP
	+: Pops the value off the top of the (main) stack and pushes it onto the
	stack of register \f[I]r\f[R].
	The previous value of the register becomes inaccessible.
	-.TP
	+.PP
	\f[B]L\f[R]\f[I]r\f[R]
	-Pops the value off the top of the stack for register \f[I]r\f[R] and
	+.PP
	+: Pops the value off the top of the stack for register \f[I]r\f[R] and
	push it onto the main stack.
	The previous value in the stack for register \f[I]r\f[R], if any, is now
	accessible via the \f[B]l\f[R]\f[I]r\f[R] command.
	.SS Parameters
	.PP
	These commands control the values of \f[B]ibase\f[R], \f[B]obase\f[R],
	\f[B]scale\f[R], and \f[B]seed\f[R].
	Also see the \f[B]SYNTAX\f[R] section.
	-.TP
	+.PP
	\f[B]i\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]ibase\f[R], which must be between \f[B]2\f[R] and \f[B]16\f[R],
	inclusive.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]o\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]obase\f[R], which must be between \f[B]0\f[R] and
	\f[B]DC_BASE_MAX\f[R], inclusive (see the \f[B]LIMITS\f[R] section and
	the \f[B]NUMBERS\f[R] section).
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]k\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]scale\f[R], which must be non-negative.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If the value on top of the stack has any scale, the scale is ignored.
	+\f[R]
	+.fi
	.PP
	-If the value on top of the stack has any \f[I]scale\f[R], the
	-\f[I]scale\f[R] is ignored.
	-.RE
	-.TP
	\f[B]j\f[R]
	-Pops the value off of the top of the stack and uses it to set
	+.PP
	+: Pops the value off of the top of the stack and uses it to set
	\f[B]seed\f[R].
	The meaning of \f[B]seed\f[R] is dependent on the current pseudo-random
	number generator but is guaranteed to not change except for new major
	versions.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+The scale and sign of the value may be significant.
	+
	+If a previously used seed value is used again, the pseudo-random number
	+generator is guaranteed to produce the same sequence of pseudo-random
	+numbers as it did when the seed value was previously used.
	+
	+The exact value assigned to seed is not guaranteed to be returned if the
	+J command is used. However, if seed does return a different value,
	+both values, when assigned to seed, are guaranteed to produce the same
	+sequence of pseudo-random numbers. This means that certain values assigned
	+to seed will not produce unique sequences of pseudo-random numbers.
	+
	+There is no limit to the length (number of significant decimal digits) or
	+scale of the value that can be assigned to seed.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-The \f[I]scale\f[R] and sign of the value may be significant.
	+\f[B]I\f[R]
	.PP
	-If a previously used \f[B]seed\f[R] value is used again, the
	-pseudo-random number generator is guaranteed to produce the same
	-sequence of pseudo-random numbers as it did when the \f[B]seed\f[R]
	-value was previously used.
	+: Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	.PP
	-The exact value assigned to \f[B]seed\f[R] is not guaranteed to be
	-returned if the \f[B]J\f[R] command is used.
	-However, if \f[B]seed\f[R] \f[I]does\f[R] return a different value, both
	-values, when assigned to \f[B]seed\f[R], are guaranteed to produce the
	-same sequence of pseudo-random numbers.
	-This means that certain values assigned to \f[B]seed\f[R] will not
	-produce unique sequences of pseudo-random numbers.
	+\f[B]O\f[R]
	.PP
	-There is no limit to the length (number of significant decimal digits)
	-or \f[I]scale\f[R] of the value that can be assigned to \f[B]seed\f[R].
	+: Pushes the current value of \f[B]obase\f[R] onto the main stack.
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	-\f[B]I\f[R]
	-Pushes the current value of \f[B]ibase\f[R] onto the main stack.
	-.TP
	-\f[B]O\f[R]
	-Pushes the current value of \f[B]obase\f[R] onto the main stack.
	-.TP
	\f[B]K\f[R]
	-Pushes the current value of \f[B]scale\f[R] onto the main stack.
	-.TP
	+.PP
	+: Pushes the current value of \f[B]scale\f[R] onto the main stack.
	+.PP
	\f[B]J\f[R]
	-Pushes the current value of \f[B]seed\f[R] onto the main stack.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	+: Pushes the current value of \f[B]seed\f[R] onto the main stack.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	+.PP
	\f[B]T\f[R]
	-Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]ibase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]U\f[R]
	-Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]obase\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]V\f[R]
	-Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	+.PP
	+: Pushes the maximum allowable value of \f[B]scale\f[R] onto the main
	stack.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]W\f[R]
	-Pushes the maximum (inclusive) integer that can be generated with the
	-\f[B]\[cq]\f[R] pseudo-random number generator command.
	-.RS
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	+: Pushes the maximum (inclusive) integer that can be generated with the
	+\f[B]\[aq]\f[R] pseudo-random number generator command.
	+.IP
	+.nf
	+\f[C]
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.SS Strings
	.PP
	The following commands control strings.
	.PP
	dc(1) can work with both numbers and strings, and registers (see the
	\f[B]REGISTERS\f[R] section) can hold both strings and numbers.
	dc(1) always knows whether the contents of a register are a string or a
	number.
	.PP
	While arithmetic operations have to have numbers, and will print an
	error if given a string, other commands accept strings.
	.PP
	Strings can also be executed as macros.
	For example, if the string \f[B][1pR]\f[R] is executed as a macro, then
	the code \f[B]1pR\f[R] is executed, meaning that the \f[B]1\f[R] will be
	printed with a newline after and then popped from the stack.
	-.TP
	-\f[B][\f[R]_characters_\f[B]]\f[R]
	-Makes a string containing \f[I]characters\f[R] and pushes it onto the
	-stack.
	-.RS
	.PP
	-If there are brackets (\f[B][\f[R] and \f[B]]\f[R]) in the string, then
	-they must be balanced.
	-Unbalanced brackets can be escaped using a backslash (\f[B]\[rs]\f[R])
	-character.
	+\f[B][\f[R]\f[I]characters\f[R]\f[B]]\f[R]
	.PP
	+: Makes a string containing \f[I]characters\f[R] and pushes it onto the
	+stack.
	+.IP
	+.nf
	+\f[C]
	+If there are brackets (\[rs][ and \[rs]]) in the string, then they must be
	+balanced. Unbalanced brackets can be escaped using a backslash (\[rs]\[rs])
	+character.
	+
	If there is a backslash character in the string, the character after it
	-(even another backslash) is put into the string verbatim, but the
	-(first) backslash is not.
	-.RE
	-.TP
	-\f[B]a\f[R]
	-The value on top of the stack is popped.
	-.RS
	+(even another backslash) is put into the string verbatim, but the (first)
	+backslash is not.
	+\f[R]
	+.fi
	.PP
	-If it is a number, it is truncated and its absolute value is taken.
	-The result mod \f[B]UCHAR_MAX+1\f[R] is calculated.
	-If that result is \f[B]0\f[R], push an empty string; otherwise, push a
	-one-character string where the character is the result of the mod
	-interpreted as an ASCII character.
	+\f[B]a\f[R]
	.PP
	-If it is a string, then a new string is made.
	-If the original string is empty, the new string is empty.
	-If it is not, then the first character of the original string is used to
	-create the new string as a one-character string.
	-The new string is then pushed onto the stack.
	+: The value on top of the stack is popped.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, it is truncated and its absolute value is taken. The
	+result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	+empty string; otherwise, push a one-character string where the character is
	+the result of the mod interpreted as an ASCII character.
	+
	+If it is a string, then a new string is made. If the original string is
	+empty, the new string is empty. If it is not, then the first character of
	+the original string is used to create the new string as a one-character
	+string. The new string is then pushed onto the stack.
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]x\f[R]
	-Pops a value off of the top of the stack.
	-.RS
	.PP
	+: Pops a value off of the top of the stack.
	+.IP
	+.nf
	+\f[C]
	If it is a number, it is pushed back onto the stack.
	-.PP
	+
	If it is a string, it is executed as a macro.
	-.PP
	+
	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is greater than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	-.PP
	-For example, \f[B]0 1>a\f[R] will execute the contents of register
	-\f[B]a\f[R], and \f[B]1 0>a\f[R] will not.
	+.IP
	+.nf
	+\f[C]
	+For example, 0 1>a will execute the contents of register a, and
	+1 0>a will not.
	+
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not greater than the second (less than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!>\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is less than the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not less than the second (greater than or equal
	to), then the contents of register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!<\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is equal to the second, then the contents of register
	\f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]
	-Pops two values off of the stack that must be numbers and compares them.
	+.PP
	+: Pops two values off of the stack that must be numbers and compares
	+them.
	If the first value is not equal to the second, then the contents of
	register \f[I]r\f[R] are executed.
	-.RS
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+\f[R]
	+.fi
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	-.RE
	-.TP
	\f[B]!=\f[R]\f[I]r\f[R]\f[B]e\f[R]\f[I]s\f[R]
	-Like the above, but will execute register \f[I]s\f[R] if the comparison
	-fails.
	-.RS
	.PP
	-If either or both of the values are not numbers, dc(1) will raise an
	-error and reset (see the \f[B]RESET\f[R] section).
	+: Like the above, but will execute register \f[I]s\f[R] if the
	+comparison fails.
	+.IP
	+.nf
	+\f[C]
	+If either or both of the values are not numbers, dc(1) will raise an error
	+and reset (see the RESET section).
	+
	+This is a non-portable extension.
	+\f[R]
	+.fi
	.PP
	-This is a \f[B]non-portable extension\f[R].
	-.RE
	-.TP
	\f[B]?\f[R]
	-Reads a line from the \f[B]stdin\f[R] and executes it.
	+.PP
	+: Reads a line from the \f[B]stdin\f[R] and executes it.
	This is to allow macros to request input from users.
	-.TP
	+.PP
	\f[B]q\f[R]
	-During execution of a macro, this exits the execution of that macro and
	-the execution of the macro that executed it.
	+.PP
	+: During execution of a macro, this exits the execution of that macro
	+and the execution of the macro that executed it.
	If there are no macros, or only one macro executing, dc(1) exits.
	-.TP
	+.PP
	\f[B]Q\f[R]
	-Pops a value from the stack which must be non-negative and is used the
	+.PP
	+: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack.
	If the number of levels to pop is greater than the number of executing
	macros, dc(1) exits.
	.SS Status
	.PP
	These commands query status of the stack or its top value.
	-.TP
	-\f[B]Z\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, calculates the number of significant decimal digits
	-it has and pushes the result.
	+\f[B]Z\f[R]
	.PP
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, calculates the number of significant decimal digits it
	+has and pushes the result.
	+
	If it is a string, pushes the number of characters the string has.
	-.RE
	-.TP
	+\f[R]
	+.fi
	+.PP
	\f[B]X\f[R]
	-Pops a value off of the stack.
	-.RS
	.PP
	-If it is a number, pushes the \f[I]scale\f[R] of the value onto the
	-stack.
	+: Pops a value off of the stack.
	+.IP
	+.nf
	+\f[C]
	+If it is a number, pushes the scale of the value onto the stack.
	+
	+If it is a string, pushes 0.
	+\f[R]
	+.fi
	.PP
	-If it is a string, pushes \f[B]0\f[R].
	-.RE
	-.TP
	\f[B]z\f[R]
	-Pushes the current stack depth (before execution of this command).
	+.PP
	+: Pushes the current stack depth (before execution of this command).
	.SS Arrays
	.PP
	These commands manipulate arrays.
	-.TP
	+.PP
	\f[B]:\f[R]\f[I]r\f[R]
	-Pops the top two values off of the stack.
	+.PP
	+: Pops the top two values off of the stack.
	The second value will be stored in the array \f[I]r\f[R] (see the
	\f[B]REGISTERS\f[R] section), indexed by the first value.
	-.TP
	+.PP
	\f[B];\f[R]\f[I]r\f[R]
	-Pops the value on top of the stack and uses it as an index into the
	+.PP
	+: Pops the value on top of the stack and uses it as an index into the
	array \f[I]r\f[R].
	The selected value is then pushed onto the stack.
	.SH REGISTERS
	.PP
	Registers are names that can store strings, numbers, and arrays.
	(Number/string registers do not interfere with array registers.)
	.PP
	Each register is also its own stack, so the current register value is
	the top of the stack for the register.
	All registers, when first referenced, have one value (\f[B]0\f[R]) in
	their stack.
	.PP
	In non-extended register mode, a register name is just the single
	character that follows any command that needs a register name.
	-The only exception is a newline (\f[B]`\[rs]n'\f[R]); it is a parse
	-error for a newline to be used as a register name.
	+The only exception is a newline (\f[B]\[aq]\[rs]n\[aq]\f[R]); it is a
	+parse error for a newline to be used as a register name.
	.SS Extended Register Mode
	.PP
	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]--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
	-(\f[B]`\[rs]n'\f[R]).
	+(\f[B]\[aq]\[rs]n\[aq]\f[R]).
	.PP
	In that case, the register name is found according to the regex
	\f[B][a-z][a-z0-9_]*\f[R] (like bc(1) identifiers), and it is a parse
	error if the next non-space characters do not match that regex.
	.SH RESET
	.PP
	When dc(1) encounters an error or a signal that it has a non-default
	handler for, it resets.
	This means that several things happen.
	.PP
	First, any macros that are executing are stopped and popped off the
	stack.
	The behavior is not unlike that of exceptions in programming languages.
	Then the execution point is set so that any code waiting to execute
	(after all macros returned) is skipped.
	.PP
	Thus, when dc(1) resets, it skips any remaining code waiting to be
	executed.
	Then, if it is interactive mode, and the error was not a fatal error
	(see the \f[B]EXIT STATUS\f[R] section), it asks for more input;
	otherwise, it exits with the appropriate return code.
	.SH PERFORMANCE
	.PP
	Most dc(1) implementations use \f[B]char\f[R] types to calculate the
	value of \f[B]1\f[R] decimal digit at a time, but that can be slow.
	This dc(1) does something different.
	.PP
	It uses large integers to calculate more than \f[B]1\f[R] decimal digit
	at a time.
	If built in a environment where \f[B]DC_LONG_BIT\f[R] (see the
	\f[B]LIMITS\f[R] section) is \f[B]64\f[R], then each integer has
	\f[B]9\f[R] decimal digits.
	If built in an environment where \f[B]DC_LONG_BIT\f[R] is \f[B]32\f[R]
	then each integer has \f[B]4\f[R] decimal digits.
	This value (the number of decimal digits per large integer) is called
	\f[B]DC_BASE_DIGS\f[R].
	.PP
	In addition, this dc(1) uses an even larger integer for overflow
	checking.
	This integer type depends on the value of \f[B]DC_LONG_BIT\f[R], but is
	always at least twice as large as the integer type used to store digits.
	.SH LIMITS
	.PP
	The following are the limits on dc(1):
	-.TP
	+.PP
	\f[B]DC_LONG_BIT\f[R]
	-The number of bits in the \f[B]long\f[R] type in the environment where
	+.PP
	+: The number of bits in the \f[B]long\f[R] type in the environment where
	dc(1) was built.
	This determines how many decimal digits can be stored in a single large
	integer (see the \f[B]PERFORMANCE\f[R] section).
	-.TP
	+.PP
	\f[B]DC_BASE_DIGS\f[R]
	-The number of decimal digits per large integer (see the
	+.PP
	+: The number of decimal digits per large integer (see the
	\f[B]PERFORMANCE\f[R] section).
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_POW\f[R]
	-The max decimal number that each large integer can store (see
	+.PP
	+: The max decimal number that each large integer can store (see
	\f[B]DC_BASE_DIGS\f[R]) plus \f[B]1\f[R].
	Depends on \f[B]DC_BASE_DIGS\f[R].
	-.TP
	+.PP
	\f[B]DC_OVERFLOW_MAX\f[R]
	-The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	+.PP
	+: The max number that the overflow type (see the \f[B]PERFORMANCE\f[R]
	section) can hold.
	Depends on \f[B]DC_LONG_BIT\f[R].
	-.TP
	+.PP
	\f[B]DC_BASE_MAX\f[R]
	-The maximum output base.
	+.PP
	+: The maximum output base.
	Set at \f[B]DC_BASE_POW\f[R].
	-.TP
	+.PP
	\f[B]DC_DIM_MAX\f[R]
	-The maximum size of arrays.
	+.PP
	+: The maximum size of arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_SCALE_MAX\f[R]
	-The maximum \f[B]scale\f[R].
	+.PP
	+: The maximum \f[B]scale\f[R].
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_STRING_MAX\f[R]
	-The maximum length of strings.
	+.PP
	+: The maximum length of strings.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NAME_MAX\f[R]
	-The maximum length of identifiers.
	+.PP
	+: The maximum length of identifiers.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_NUM_MAX\f[R]
	-The maximum length of a number (in decimal digits), which includes
	+.PP
	+: The maximum length of a number (in decimal digits), which includes
	digits after the decimal point.
	Set at \f[B]DC_OVERFLOW_MAX-1\f[R].
	-.TP
	+.PP
	\f[B]DC_RAND_MAX\f[R]
	-The maximum integer (inclusive) returned by the \f[B]\[cq]\f[R] command,
	-if dc(1).
	+.PP
	+: The maximum integer (inclusive) returned by the \f[B]\[aq]\f[R]
	+command, if dc(1).
	Set at \f[B]2\[ha]DC_LONG_BIT-1\f[R].
	-.TP
	+.PP
	Exponent
	-The maximum allowable exponent (positive or negative).
	+.PP
	+: The maximum allowable exponent (positive or negative).
	Set at \f[B]DC_OVERFLOW_MAX\f[R].
	-.TP
	+.PP
	Number of vars
	-The maximum number of vars/arrays.
	+.PP
	+: The maximum number of vars/arrays.
	Set at \f[B]SIZE_MAX-1\f[R].
	.PP
	These limits are meant to be effectively non-existent; the limits are so
	large (at least on 64-bit machines) that there should not be any point
	at which they become a problem.
	In fact, memory should be exhausted before these limits should be hit.
	.SH ENVIRONMENT VARIABLES
	.PP
	dc(1) recognizes the following environment variables:
	-.TP
	+.PP
	\f[B]DC_ENV_ARGS\f[R]
	-This is another way to give command-line arguments to dc(1).
	+.PP
	+: This is another way to give command-line arguments to dc(1).
	They should be in the same format as all other command-line arguments.
	These are always processed first, so any files given in
	\f[B]DC_ENV_ARGS\f[R] will be processed before arguments and files given
	on the command-line.
	-This gives the user the ability to set up \[lq]standard\[rq] options and
	+This gives the user the ability to set up \[dq]standard\[dq] options and
	files to be used at every invocation.
	The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs.
	Another use would be to use the \f[B]-e\f[R] option to set
	\f[B]scale\f[R] to a value other than \f[B]0\f[R].
	-.RS
	-.PP
	-The code that parses \f[B]DC_ENV_ARGS\f[R] will correctly handle quoted
	-arguments, but it does not understand escape sequences.
	-For example, the string \f[B]\[lq]/home/gavin/some dc file.dc\[rq]\f[R]
	-will be correctly parsed, but the string \f[B]\[lq]/home/gavin/some
	-\[dq]dc\[dq] file.dc\[rq]\f[R] will include the backslashes.
	-.PP
	-The quote parsing will handle either kind of quotes, \f[B]\[cq]\f[R] or
	-\f[B]\[lq]\f[R]. Thus, if you have a file with any number of single
	-quotes in the name, you can use double quotes as the outside quotes, as
	-in \f[B]\[rq]some `dc' file.dc\[dq]\f[R], and vice versa if you have a
	-file with double quotes.
	-However, handling a file with both kinds of quotes in
	-\f[B]DC_ENV_ARGS\f[R] is not supported due to the complexity of the
	-parsing, though such files are still supported on the command-line where
	-the parsing is done by the shell.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	+but it does not understand escape sequences. For example, the string
	+\[dq]/home/gavin/some dc file.dc\[dq] will be correctly parsed, but the string
	+\[dq]/home/gavin/some \[rs]\[dq]dc\[rs]\[dq] file.dc\[dq] will include the backslashes.
	+
	+The quote parsing will handle either kind of quotes, \[aq] or \[dq]. Thus,
	+if you have a file with any number of single quotes in the name, you can use
	+double quotes as the outside quotes, as in \[dq]some \[aq]dc\[aq] file.dc\[dq], and vice
	+versa if you have a file with double quotes. However, handling a file with
	+both kinds of quotes in DC_ENV_ARGS is not supported due to the
	+complexity of the parsing, though such files are still supported on the
	+command-line where the parsing is done by the shell.
	+\f[R]
	+.fi
	+.PP
	\f[B]DC_LINE_LENGTH\f[R]
	-If this environment variable exists and contains an integer that is
	+.PP
	+: If this environment variable exists and contains an integer that is
	greater than \f[B]1\f[R] and is less than \f[B]UINT16_MAX\f[R]
	(\f[B]2\[ha]16-1\f[R]), dc(1) will output lines to that length,
	including the backslash newline combo.
	The default line length is \f[B]70\f[R].
	-.TP
	+.PP
	\f[B]DC_EXPR_EXIT\f[R]
	-If this variable exists (no matter the contents), dc(1) will exit
	+.PP
	+: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the
	\f[B]-e\f[R] and/or \f[B]-f\f[R] command-line options (and any
	equivalents).
	.SH EXIT STATUS
	.PP
	dc(1) returns the following exit statuses:
	-.TP
	+.PP
	\f[B]0\f[R]
	-No error.
	-.TP
	+.PP
	+: No error.
	+.PP
	\f[B]1\f[R]
	-A math error occurred.
	+.PP
	+: A math error occurred.
	This follows standard practice of using \f[B]1\f[R] for expected errors,
	since math errors will happen in the process of normal execution.
	-.RS
	-.PP
	-Math errors include divide by \f[B]0\f[R], taking the square root of a
	-negative number, using a negative number as a bound for the
	-pseudo-random number generator, attempting to convert a negative number
	-to a hardware integer, overflow when converting a number to a hardware
	-integer, and attempting to use a non-integer where an integer is
	-required.
	-.PP
	-Converting to a hardware integer happens for the second operand of the
	-power (\f[B]\[ha]\f[R]), places (\f[B]\[at]\f[R]), left shift
	-(\f[B]H\f[R]), and right shift (\f[B]h\f[R]) operators.
	-.RE
	-.TP
	+.IP
	+.nf
	+\f[C]
	+Math errors include divide by 0, taking the square root of a negative
	+number, using a negative number as a bound for the pseudo-random number
	+generator, attempting to convert a negative number to a hardware integer,
	+overflow when converting a number to a hardware integer, and attempting to
	+use a non-integer where an integer is required.
	+
	+Converting to a hardware integer happens for the second operand of the power
	+(\[rs]\[ha]), places (\[rs]\[at]), left shift (H), and right shift (h)
	+operators.
	+\f[R]
	+.fi
	+.PP
	\f[B]2\f[R]
	-A parse error occurred.
	-.RS
	-.PP
	-Parse errors include unexpected \f[B]EOF\f[R], using an invalid
	-character, failing to find the end of a string or comment, and using a
	-token where it is invalid.
	-.RE
	-.TP
	+.PP
	+: A parse error occurred.
	+.IP
	+.nf
	+\f[C]
	+Parse errors include unexpected EOF, using an invalid character, failing
	+to find the end of a string or comment, and using a token where it is
	+invalid.
	+\f[R]
	+.fi
	+.PP
	\f[B]3\f[R]
	-A runtime error occurred.
	-.RS
	-.PP
	-Runtime errors include assigning an invalid number to \f[B]ibase\f[R],
	-\f[B]obase\f[R], or \f[B]scale\f[R]; give a bad expression to a
	-\f[B]read()\f[R] call, calling \f[B]read()\f[R] inside of a
	-\f[B]read()\f[R] call, type errors, and attempting an operation when the
	-stack has too few elements.
	-.RE
	-.TP
	+.PP
	+: A runtime error occurred.
	+.IP
	+.nf
	+\f[C]
	+Runtime errors include assigning an invalid number to ibase, obase,
	+or scale; give a bad expression to a read() call, calling read()
	+inside of a read() call, type errors, and attempting an operation when
	+the stack has too few elements.
	+\f[R]
	+.fi
	+.PP
	\f[B]4\f[R]
	-A fatal error occurred.
	-.RS
	.PP
	-Fatal errors include memory allocation errors, I/O errors, failing to
	-open files, attempting to use files that do not have only ASCII
	-characters (dc(1) only accepts ASCII characters), attempting to open a
	-directory as a file, and giving invalid command-line options.
	-.RE
	+: A fatal error occurred.
	+.IP
	+.nf
	+\f[C]
	+Fatal errors include memory allocation errors, I/O errors, failing to open
	+files, attempting to use files that do not have only ASCII characters (dc(1)
	+only accepts ASCII characters), attempting to open a directory as a file,
	+and giving invalid command-line options.
	+\f[R]
	+.fi
	.PP
	The exit status \f[B]4\f[R] is special; when a fatal error occurs, dc(1)
	always exits and returns \f[B]4\f[R], no matter what mode dc(1) is in.
	.PP
	The other statuses will only be returned when dc(1) is not in
	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]--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]--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]--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
	\f[B]stdout\f[R] as soon as execution is done for the current input.
	.SH TTY MODE
	.PP
	If \f[B]stdin\f[R], \f[B]stdout\f[R], and \f[B]stderr\f[R] are all
	-connected to a TTY, dc(1) turns on \[lq]TTY mode.\[rq]
	+connected to a TTY, dc(1) turns on \[dq]TTY mode.\[dq]
	.PP
	TTY mode is required for history to be enabled (see the \f[B]COMMAND
	LINE HISTORY\f[R] section).
	It is also required to enable special handling for \f[B]SIGINT\f[R]
	signals.
	.PP
	TTY mode is different from interactive mode because interactive mode is
	required in the bc(1)
	specification (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html),
	and interactive mode requires only \f[B]stdin\f[R] and \f[B]stdout\f[R]
	to be connected to a terminal.
	.SH SIGNAL HANDLING
	.PP
	Sending a \f[B]SIGINT\f[R] will cause dc(1) to stop execution of the
	current input.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), it will
	reset (see the \f[B]RESET\f[R] section).
	Otherwise, it will clean up and exit.
	.PP
	-Note that \[lq]current input\[rq] can mean one of two things.
	+Note that \[dq]current input\[dq] can mean one of two things.
	If dc(1) is processing input from \f[B]stdin\f[R] in TTY mode, it will
	ask for more input.
	If dc(1) is processing input from a file in TTY mode, it will stop
	processing the file and start processing the next file, if one exists,
	or ask for input from \f[B]stdin\f[R] if no other file exists.
	.PP
	This means that if a \f[B]SIGINT\f[R] is sent to dc(1) as it is
	executing a file, it can seem as though dc(1) did not respond to the
	signal since it will immediately start executing the next file.
	This is by design; most files that users execute when interacting with
	dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file.
	The rest of the files could still be executed without problem, allowing
	the user to continue.
	.PP
	\f[B]SIGTERM\f[R] and \f[B]SIGQUIT\f[R] cause dc(1) to clean up and
	exit, and it uses the default handler for all other signals.
	The one exception is \f[B]SIGHUP\f[R]; in that case, when dc(1) is in
	TTY mode, a \f[B]SIGHUP\f[R] will cause dc(1) to clean up and exit.
	.SH COMMAND LINE HISTORY
	.PP
	dc(1) supports interactive command-line editing.
	If dc(1) is in TTY mode (see the \f[B]TTY MODE\f[R] section), history is
	enabled.
	Previous lines can be recalled and edited with the arrow keys.
	.PP
	\f[B]Note\f[R]: tabs are converted to 8 spaces.
	.SH LOCALES
	.PP
	This dc(1) ships with support for adding error messages for different
	locales and thus, supports \f[B]LC_MESSAGS\f[R].
	.SH SEE ALSO
	.PP
	bc(1)
	.SH STANDARDS
	.PP
	The dc(1) utility operators are compliant with the operators in the
	bc(1) IEEE Std 1003.1-2017
	(\[lq]POSIX.1-2017\[rq]) (https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html)
	specification.
	.SH BUGS
	.PP
	None are known.
	Report bugs at https://git.yzena.com/gavin/bc.
	.SH AUTHOR
	.PP
	Gavin D.
	Howard <gavin@yzena.com> and contributors.
	diff --git a/contrib/bc/manuals/dc/P.1.md b/contrib/bc/manuals/dc/P.1.md
	index 0101b68fb872..ccb71bf549fa 100644
	--- a/contrib/bc/manuals/dc/P.1.md
	+++ b/contrib/bc/manuals/dc/P.1.md
	@@ -1,1202 +1,1208 @@
	<!---

	SPDX-License-Identifier: BSD-2-Clause

	Copyright (c) 2018-2021 Gavin D. Howard and contributors.

	Redistribution and use in source and binary forms, with or without
	modification, are permitted provided that the following conditions are met:

	* Redistributions of source code must retain the above copyright notice, this
	list of conditions and the following disclaimer.

	* 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.

	THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.

	-->

	# Name

	dc - arbitrary-precision decimal reverse-Polish notation calculator

	# SYNOPSIS

	-dc [-hiPvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]
	+dc [-hiPRvVx] [-\-version] [-\-help] [-\-interactive] [-\-no-prompt] [-\-no-read-prompt] [-\-extended-register] [-e expr] [-\-expression=expr...] [-f file...] [-\-file=file...] [file...]

	# DESCRIPTION

	dc(1) is an arbitrary-precision calculator. It uses a stack (reverse Polish
	notation) to store numbers and results of computations. Arithmetic operations
	pop arguments off of the stack and push the results.

	If no files are given on the command-line as extra arguments (i.e., not as
	-f or -\-file arguments), then dc(1) reads from stdin. Otherwise,
	those files are processed, and dc(1) will then exit.

	This is different from the dc(1) on OpenBSD and possibly other dc(1)
	implementations, where -e (-\-expression) and -f (-\-file)
	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 DC_ENV_ARGS
	(see the ENVIRONMENT VARIABLES section). Any expressions given on the
	command-line should be used to set up a standard environment. For example, if a
	user wants the scale always set to 10, they can set DC_ENV_ARGS to
	-e 10k, and this dc(1) will always start with a scale of 10.

	If users want to have dc(1) exit after processing all input from -e and
	-f arguments (and their equivalents), then they can just simply add -e q
	as the last command-line argument or define the environment variable
	DC_EXPR_EXIT.

	# OPTIONS

	The following are the options that dc(1) accepts.

	-h, -\-help

	: Prints a usage message and quits.

	-v, -V, -\-version

	: Print the version information (copyright header) and exit.

	-i, -\-interactive

	: Forces interactive mode. (See the INTERACTIVE MODE section.)

	This is a non-portable extension.

	-P, -\-no-prompt

	+: This option is a no-op.
	+
	+ This is a non-portable extension.
	+
	+-R, -\-no-read-prompt
	+
	: This option is a no-op.

	This is a non-portable extension.

	-x -\-extended-register

	: Enables extended register mode. See the Extended Register Mode subsection
	of the REGISTERS section for more information.

	This is a non-portable extension.

	-e expr, -\-expression=expr

	: Evaluates expr. If multiple expressions are given, they are evaluated in
	order. If files are given as well (see below), the expressions and files are
	evaluated in the order given. This means that if a file is given before an
	expression, the file is read in and evaluated first.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file, whether on the
	command-line or in DC_ENV_ARGS. However, if any other -e,
	-\-expression, -f, or -\-file arguments are given after -f-
	or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	-f file, -\-file=file

	: Reads in file and evaluates it, line by line, as though it were read
	through stdin. If expressions are also given (see above), the
	expressions are evaluated in the order given.

	If this option is given on the command-line (i.e., not in DC_ENV_ARGS,
	see the ENVIRONMENT VARIABLES section), then after processing all
	expressions and files, dc(1) will exit, unless - (stdin) was given
	as an argument at least once to -f or -\-file. However, if any other
	-e, -\-expression, -f, or -\-file arguments are given after
	-f- or equivalent is given, dc(1) will give a fatal error and exit.

	This is a non-portable extension.

	All long options are non-portable extensions.

	# STDOUT

	Any non-error output is written to stdout. In addition, if history (see the
	HISTORY section) and the prompt (see the TTY MODE section) are enabled,
	both are output to stdout.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stdout, so if
	stdout is closed, as in dc <file> >&-, it will quit with an error. This
	is done so that dc(1) can report problems when stdout is redirected to a
	file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stdout to
	/dev/null.

	# STDERR

	Any error output is written to stderr.

	Note: Unlike other dc(1) implementations, this dc(1) will issue a fatal
	error (see the EXIT STATUS section) if it cannot write to stderr, so if
	stderr is closed, as in dc <file> 2>&-, it will quit with an error. This
	is done so that dc(1) can exit with an error code when stderr is redirected
	to a file.

	If there are scripts that depend on the behavior of other dc(1) implementations,
	it is recommended that those scripts be changed to redirect stderr to
	/dev/null.

	# SYNTAX

	Each item in the input source code, either a number (see the NUMBERS
	section) or a command (see the COMMANDS section), is processed and executed,
	in order. Input is processed immediately when entered.

	ibase is a register (see the REGISTERS section) that determines how to
	interpret constant numbers. It is the "input" base, or the number base used for
	interpreting input numbers. ibase is initially 10. The max allowable
	value for ibase is 16. The min allowable value for ibase is 2.
	The max allowable value for ibase can be queried in dc(1) programs with the
	T command.

	obase is a register (see the REGISTERS section) that determines how to
	output results. It is the "output" base, or the number base used for outputting
	numbers. obase is initially 10. The max allowable value for obase is
	DC_BASE_MAX and can be queried with the U command. The min allowable
	value for obase is 0. If obase is 0, values are output in
	scientific notation, and if obase is 1, values are output in engineering
	notation. Otherwise, values are output in the specified base.

	Outputting in scientific and engineering notations are **non-portable
	extensions**.

	The scale of an expression is the number of digits in the result of the
	expression right of the decimal point, and scale is a register (see the
	REGISTERS section) that sets the precision of any operations (with
	exceptions). scale is initially 0. scale cannot be negative. The max
	allowable value for scale can be queried in dc(1) programs with the V
	command.

	seed is a register containing the current seed for the pseudo-random number
	generator. If the current value of seed is queried and stored, then if it is
	assigned to seed later, the pseudo-random number generator is guaranteed to
	produce the same sequence of pseudo-random numbers that were generated after the
	value of seed was first queried.

	Multiple values assigned to seed can produce the same sequence of
	pseudo-random numbers. Likewise, when a value is assigned to seed, it is not
	guaranteed that querying seed immediately after will return the same value.
	In addition, the value of seed will change after any call to the '
	command or the " command that does not get receive a value of 0 or
	1. The maximum integer returned by the ' command can be queried with the
	W command.

	Note: The values returned by the pseudo-random number generator with the
	' and " commands are guaranteed to NOT be cryptographically secure.
	This is a consequence of using a seeded pseudo-random number generator. However,
	they are guaranteed to be reproducible with identical seed values. This
	means that the pseudo-random values from dc(1) should only be used where a
	reproducible stream of pseudo-random numbers is ESSENTIAL. In any other case,
	use a non-seeded pseudo-random number generator.

	The pseudo-random number generator, seed, and all associated operations are
	non-portable extensions.

	## Comments

	Comments go from # until, and not including, the next newline. This is a
	non-portable extension.

	# NUMBERS

	Numbers are strings made up of digits, uppercase letters up to F, and at
	most 1 period for a radix. Numbers can have up to DC_NUM_MAX digits.
	Uppercase letters are equal to 9 + their position in the alphabet (i.e.,
	A equals 10, or 9+1). If a digit or letter makes no sense with the
	current value of ibase, they are set to the value of the highest valid digit
	in ibase.

	Single-character numbers (i.e., A alone) take the value that they would have
	if they were valid digits, regardless of the value of ibase. This means that
	A alone always equals decimal 10 and F alone always equals decimal
	15.

	In addition, dc(1) accepts numbers in scientific notation. These have the form
	\<number\>e\<integer\>. The exponent (the portion after the e) must be
	an integer. An example is 1.89237e9, which is equal to 1892370000.
	Negative exponents are also allowed, so 4.2890e_3 is equal to 0.0042890.

	WARNING: Both the number and the exponent in scientific notation are
	interpreted according to the current ibase, but the number is still
	multiplied by 10\^exponent regardless of the current ibase. For example,
	if ibase is 16 and dc(1) is given the number string FFeA, the
	resulting decimal number will be 2550000000000, and if dc(1) is given the
	number string 10e_4, the resulting decimal number will be 0.0016.

	Accepting input as scientific notation is a non-portable extension.

	# COMMANDS

	The valid commands are listed below.

	## Printing

	These commands are used for printing.

	Note that both scientific notation and engineering notation are available for
	printing numbers. Scientific notation is activated by assigning 0 to
	obase using 0o, and engineering notation is activated by assigning 1
	to obase using 1o. To deactivate them, just assign a different value to
	obase.

	Printing numbers in scientific notation and/or engineering notation is a
	non-portable extension.

	p

	: Prints the value on top of the stack, whether number or string, and prints a
	newline after.

	This does not alter the stack.

	n

	: Prints the value on top of the stack, whether number or string, and pops it
	off of the stack.

	P

	: Pops a value off the stack.

	If the value is a number, it is truncated and the absolute value of the
	result is printed as though obase is UCHAR_MAX+1 and each digit is
	interpreted as an ASCII character, making it a byte stream.

	If the value is a string, it is printed without a trailing newline.

	This is a non-portable extension.

	f

	: Prints the entire contents of the stack, in order from newest to oldest,
	without altering anything.

	Users should use this command when they get lost.

	## Arithmetic

	These are the commands used for arithmetic.

	+

	: The top two values are popped off the stack, added, and the result is pushed
	onto the stack. The scale of the result is equal to the max scale of
	both operands.

	-

	: The top two values are popped off the stack, subtracted, and the result is
	pushed onto the stack. The scale of the result is equal to the max
	scale of both operands.

	\*

	: The top two values are popped off the stack, multiplied, and the result is
	pushed onto the stack. If a is the scale of the first expression and
	b is the scale of the second expression, the scale of the result
	is equal to min(a+b,max(scale,a,b)) where min() and max() return
	the obvious values.

	/

	: The top two values are popped off the stack, divided, and the result is
	pushed onto the stack. The scale of the result is equal to scale.

	The first value popped off of the stack must be non-zero.

	%

	: The top two values are popped off the stack, remaindered, and the result is
	pushed onto the stack.

	Remaindering is equivalent to 1) Computing a/b to current scale, and
	2) Using the result of step 1 to calculate *a-(a/b)\b** to scale
	max(scale+scale(b),scale(a)).

	The first value popped off of the stack must be non-zero.

	~

	: The top two values are popped off the stack, divided and remaindered, and
	the results (divided first, remainder second) are pushed onto the stack.
	This is equivalent to x y / x y % except that x and y are only
	evaluated once.

	The first value popped off of the stack must be non-zero.

	This is a non-portable extension.

	\^

	: The top two values are popped off the stack, the second is raised to the
	power of the first, and the result is pushed onto the stack. The scale of
	the result is equal to scale.

	The first value popped off of the stack must be an integer, and if that
	value is negative, the second value popped off of the stack must be
	non-zero.

	v

	: The top value is popped off the stack, its square root is computed, and the
	result is pushed onto the stack. The scale of the result is equal to
	scale.

	The value popped off of the stack must be non-negative.

	\_

	: If this command immediately precedes a number (i.e., no spaces or other
	commands), then that number is input as a negative number.

	Otherwise, the top value on the stack is popped and copied, and the copy is
	negated and pushed onto the stack. This behavior without a number is a
	non-portable extension.

	b

	: The top value is popped off the stack, and if it is zero, it is pushed back
	onto the stack. Otherwise, its absolute value is pushed onto the stack.

	This is a non-portable extension.

	\|

	: The top three values are popped off the stack, a modular exponentiation is
	computed, and the result is pushed onto the stack.

	The first value popped is used as the reduction modulus and must be an
	integer and non-zero. The second value popped is used as the exponent and
	must be an integer and non-negative. The third value popped is the base and
	must be an integer.

	This is a non-portable extension.

	\$

	: The top value is popped off the stack and copied, and the copy is truncated
	and pushed onto the stack.

	This is a non-portable extension.

	\@

	: The top two values are popped off the stack, and the precision of the second
	is set to the value of the first, whether by truncation or extension.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	H

	: The top two values are popped off the stack, and the second is shifted left
	(radix shifted right) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	h

	: The top two values are popped off the stack, and the second is shifted right
	(radix shifted left) to the value of the first.

	The first value popped off of the stack must be an integer and non-negative.

	This is a non-portable extension.

	G

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if they are equal, or 0 otherwise.

	This is a non-portable extension.

	N

	: The top value is popped off of the stack, and if it a 0, a 1 is
	pushed; otherwise, a 0 is pushed.

	This is a non-portable extension.

	(

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than the second, or 0 otherwise.

	This is a non-portable extension.

	{

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is less than or equal to the second, or 0
	otherwise.

	This is a non-portable extension.

	)

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than the second, or 0 otherwise.

	This is a non-portable extension.

	}

	: The top two values are popped off of the stack, they are compared, and a
	1 is pushed if the first is greater than or equal to the second, or
	0 otherwise.

	This is a non-portable extension.

	M

	: The top two values are popped off of the stack. If they are both non-zero, a
	1 is pushed onto the stack. If either of them is zero, or both of them
	are, then a 0 is pushed onto the stack.

	This is like the && operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	m

	: The top two values are popped off of the stack. If at least one of them is
	non-zero, a 1 is pushed onto the stack. If both of them are zero, then a
	0 is pushed onto the stack.

	This is like the \|\| operator in bc(1), and it is not a short-circuit
	operator.

	This is a non-portable extension.

	## Pseudo-Random Number Generator

	dc(1) has a built-in pseudo-random number generator. These commands query the
	pseudo-random number generator. (See Parameters for more information about the
	seed value that controls the pseudo-random number generator.)

	The pseudo-random number generator is guaranteed to NOT be
	cryptographically secure.

	'

	: Generates an integer between 0 and DC_RAND_MAX, inclusive (see the
	LIMITS section).

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	"

	: Pops a value off of the stack, which is used as an exclusive upper bound
	on the integer that will be generated. If the bound is negative or is a
	non-integer, an error is raised, and dc(1) resets (see the RESET
	section) while seed remains unchanged. If the bound is larger than
	DC_RAND_MAX, the higher bound is honored by generating several
	pseudo-random integers, multiplying them by appropriate powers of
	DC_RAND_MAX+1, and adding them together. Thus, the size of integer that
	can be generated with this command is unbounded. Using this command will
	change the value of seed, unless the operand is 0 or 1. In that
	case, 0 is pushed onto the stack, and seed is not changed.

	The generated integer is made as unbiased as possible, subject to the
	limitations of the pseudo-random number generator.

	This is a non-portable extension.

	## Stack Control

	These commands control the stack.

	c

	: Removes all items from ("clears") the stack.

	d

	: Copies the item on top of the stack ("duplicates") and pushes the copy onto
	the stack.

	r

	: Swaps ("reverses") the two top items on the stack.

	R

	: Pops ("removes") the top value from the stack.

	## Register Control

	These commands control registers (see the REGISTERS section).

	-sr
	+s_r_

	: Pops the value off the top of the stack and stores it into register r.

	-lr
	+l_r_

	: Copies the value in register r and pushes it onto the stack. This does not
	alter the contents of r.

	-Sr
	+S_r_

	: Pops the value off the top of the (main) stack and pushes it onto the stack
	of register r. The previous value of the register becomes inaccessible.

	-Lr
	+L_r_

	: Pops the value off the top of the stack for register r and push it onto
	the main stack. The previous value in the stack for register r, if any, is
	- now accessible via the lr command.
	+ now accessible via the l_r_ command.

	## Parameters

	These commands control the values of ibase, obase, scale, and
	seed. Also see the SYNTAX section.

	i

	: Pops the value off of the top of the stack and uses it to set ibase,
	which must be between 2 and 16, inclusive.

	If the value on top of the stack has any scale, the scale is ignored.

	o

	: Pops the value off of the top of the stack and uses it to set obase,
	which must be between 0 and DC_BASE_MAX, inclusive (see the
	LIMITS section and the NUMBERS section).

	If the value on top of the stack has any scale, the scale is ignored.

	k

	: Pops the value off of the top of the stack and uses it to set scale,
	which must be non-negative.

	If the value on top of the stack has any scale, the scale is ignored.

	j

	: Pops the value off of the top of the stack and uses it to set seed. The
	meaning of seed is dependent on the current pseudo-random number
	generator but is guaranteed to not change except for new major versions.

	The scale and sign of the value may be significant.

	If a previously used seed value is used again, the pseudo-random number
	generator is guaranteed to produce the same sequence of pseudo-random
	numbers as it did when the seed value was previously used.

	The exact value assigned to seed is not guaranteed to be returned if the
	J command is used. However, if seed does return a different value,
	both values, when assigned to seed, are guaranteed to produce the same
	sequence of pseudo-random numbers. This means that certain values assigned
	to seed will not produce unique sequences of pseudo-random numbers.

	There is no limit to the length (number of significant decimal digits) or
	scale of the value that can be assigned to seed.

	This is a non-portable extension.

	I

	: Pushes the current value of ibase onto the main stack.

	O

	: Pushes the current value of obase onto the main stack.

	K

	: Pushes the current value of scale onto the main stack.

	J

	: Pushes the current value of seed onto the main stack.

	This is a non-portable extension.

	T

	: Pushes the maximum allowable value of ibase onto the main stack.

	This is a non-portable extension.

	U

	: Pushes the maximum allowable value of obase onto the main stack.

	This is a non-portable extension.

	V

	: Pushes the maximum allowable value of scale onto the main stack.

	This is a non-portable extension.

	W

	: Pushes the maximum (inclusive) integer that can be generated with the '
	pseudo-random number generator command.

	This is a non-portable extension.

	## Strings

	The following commands control strings.

	dc(1) can work with both numbers and strings, and registers (see the
	REGISTERS section) can hold both strings and numbers. dc(1) always knows
	whether the contents of a register are a string or a number.

	While arithmetic operations have to have numbers, and will print an error if
	given a string, other commands accept strings.

	Strings can also be executed as macros. For example, if the string [1pR] is
	executed as a macro, then the code 1pR is executed, meaning that the 1
	will be printed with a newline after and then popped from the stack.

	\[_characters_\]

	: Makes a string containing characters and pushes it onto the stack.

	If there are brackets (\[ and \]) in the string, then they must be
	balanced. Unbalanced brackets can be escaped using a backslash (\\)
	character.

	If there is a backslash character in the string, the character after it
	(even another backslash) is put into the string verbatim, but the (first)
	backslash is not.

	a

	: The value on top of the stack is popped.

	If it is a number, it is truncated and its absolute value is taken. The
	result mod UCHAR_MAX+1 is calculated. If that result is 0, push an
	empty string; otherwise, push a one-character string where the character is
	the result of the mod interpreted as an ASCII character.

	If it is a string, then a new string is made. If the original string is
	empty, the new string is empty. If it is not, then the first character of
	the original string is used to create the new string as a one-character
	string. The new string is then pushed onto the stack.

	This is a non-portable extension.

	x

	: Pops a value off of the top of the stack.

	If it is a number, it is pushed back onto the stack.

	If it is a string, it is executed as a macro.

	This behavior is the norm whenever a macro is executed, whether by this
	command or by the conditional execution commands below.

	-\>r
	+\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is greater than the second, then the contents of register
	r are executed.

	For example, 0 1>a will execute the contents of register a, and
	1 0>a will not.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	->res
	+>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\>r
	+!\>_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not greater than the second (less than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\>res
	+!\>_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-\<r
	+\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is less than the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-\<res
	+\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!\<r
	+!\<_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not less than the second (greater than or equal to), then
	the contents of register r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!\<res
	+!\<_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-=r
	+=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is equal to the second, then the contents of register r
	are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-=res
	+=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	-!=r
	+!=_r_

	: Pops two values off of the stack that must be numbers and compares them. If
	the first value is not equal to the second, then the contents of register
	r are executed.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	-!=res
	+!=_r_e_s_

	: Like the above, but will execute register s if the comparison fails.

	If either or both of the values are not numbers, dc(1) will raise an error
	and reset (see the RESET section).

	This is a non-portable extension.

	?

	: Reads a line from the stdin and executes it. This is to allow macros to
	request input from users.

	q

	: During execution of a macro, this exits the execution of that macro and the
	execution of the macro that executed it. If there are no macros, or only one
	macro executing, dc(1) exits.

	Q

	: Pops a value from the stack which must be non-negative and is used the
	number of macro executions to pop off of the execution stack. If the number
	of levels to pop is greater than the number of executing macros, dc(1)
	exits.

	## Status

	These commands query status of the stack or its top value.

	Z

	: Pops a value off of the stack.

	If it is a number, calculates the number of significant decimal digits it
	has and pushes the result.

	If it is a string, pushes the number of characters the string has.

	X

	: Pops a value off of the stack.

	If it is a number, pushes the scale of the value onto the stack.

	If it is a string, pushes 0.

	z

	: Pushes the current stack depth (before execution of this command).

	## Arrays

	These commands manipulate arrays.

	-:r
	+:_r_

	: Pops the top two values off of the stack. The second value will be stored in
	the array r (see the REGISTERS section), indexed by the first value.

	-;r
	+;_r_

	: Pops the value on top of the stack and uses it as an index into the array
	r. The selected value is then pushed onto the stack.

	# REGISTERS

	Registers are names that can store strings, numbers, and arrays. (Number/string
	registers do not interfere with array registers.)

	Each register is also its own stack, so the current register value is the top of
	the stack for the register. All registers, when first referenced, have one value
	(0) in their stack.

	In non-extended register mode, a register name is just the single character that
	follows any command that needs a register name. The only exception is a newline
	('\\n'); it is a parse error for a newline to be used as a register name.

	## Extended Register Mode

	Unlike most other dc(1) implentations, this dc(1) provides nearly unlimited
	amounts of registers, if extended register mode is enabled.

	If extended register mode is enabled (-x or -\-extended-register
	command-line arguments are given), then normal single character registers are
	used unless the character immediately following a command that needs a
	register name is a space (according to isspace()) and not a newline
	('\\n').

	In that case, the register name is found according to the regex
	\[a-z\]\[a-z0-9\_\]\* (like bc(1) identifiers), and it is a parse error if
	the next non-space characters do not match that regex.

	# RESET

	When dc(1) encounters an error or a signal that it has a non-default handler
	for, it resets. This means that several things happen.

	First, any macros that are executing are stopped and popped off the stack.
	The behavior is not unlike that of exceptions in programming languages. Then
	the execution point is set so that any code waiting to execute (after all
	macros returned) is skipped.

	Thus, when dc(1) resets, it skips any remaining code waiting to be executed.
	Then, if it is interactive mode, and the error was not a fatal error (see the
	EXIT STATUS section), it asks for more input; otherwise, it exits with the
	appropriate return code.

	# PERFORMANCE

	Most dc(1) implementations use char types to calculate the value of 1
	decimal digit at a time, but that can be slow. This dc(1) does something
	different.

	It uses large integers to calculate more than 1 decimal digit at a time. If
	built in a environment where DC_LONG_BIT (see the LIMITS section) is
	64, then each integer has 9 decimal digits. If built in an environment
	where DC_LONG_BIT is 32 then each integer has 4 decimal digits. This
	value (the number of decimal digits per large integer) is called
	DC_BASE_DIGS.

	In addition, this dc(1) uses an even larger integer for overflow checking. This
	integer type depends on the value of DC_LONG_BIT, but is always at least
	twice as large as the integer type used to store digits.

	# LIMITS

	The following are the limits on dc(1):

	DC_LONG_BIT

	: The number of bits in the long type in the environment where dc(1) was
	built. This determines how many decimal digits can be stored in a single
	large integer (see the PERFORMANCE section).

	DC_BASE_DIGS

	: The number of decimal digits per large integer (see the PERFORMANCE
	section). Depends on DC_LONG_BIT.

	DC_BASE_POW

	: The max decimal number that each large integer can store (see
	DC_BASE_DIGS) plus 1. Depends on DC_BASE_DIGS.

	DC_OVERFLOW_MAX

	: The max number that the overflow type (see the PERFORMANCE section) can
	hold. Depends on DC_LONG_BIT.

	DC_BASE_MAX

	: The maximum output base. Set at DC_BASE_POW.

	DC_DIM_MAX

	: The maximum size of arrays. Set at SIZE_MAX-1.

	DC_SCALE_MAX

	: The maximum scale. Set at DC_OVERFLOW_MAX-1.

	DC_STRING_MAX

	: The maximum length of strings. Set at DC_OVERFLOW_MAX-1.

	DC_NAME_MAX

	: The maximum length of identifiers. Set at DC_OVERFLOW_MAX-1.

	DC_NUM_MAX

	: The maximum length of a number (in decimal digits), which includes digits
	after the decimal point. Set at DC_OVERFLOW_MAX-1.

	DC_RAND_MAX

	: The maximum integer (inclusive) returned by the ' command, if dc(1). Set
	at 2\^DC_LONG_BIT-1.

	Exponent

	: The maximum allowable exponent (positive or negative). Set at
	DC_OVERFLOW_MAX.

	Number of vars

	: The maximum number of vars/arrays. Set at SIZE_MAX-1.

	These limits are meant to be effectively non-existent; the limits are so large
	(at least on 64-bit machines) that there should not be any point at which they
	become a problem. In fact, memory should be exhausted before these limits should
	be hit.

	# ENVIRONMENT VARIABLES

	dc(1) recognizes the following environment variables:

	DC_ENV_ARGS

	: This is another way to give command-line arguments to dc(1). They should be
	in the same format as all other command-line arguments. These are always
	processed first, so any files given in DC_ENV_ARGS will be processed
	before arguments and files given on the command-line. This gives the user
	the ability to set up "standard" options and files to be used at every
	invocation. The most useful thing for such files to contain would be useful
	functions that the user might want every time dc(1) runs. Another use would
	be to use the -e option to set scale to a value other than 0.

	The code that parses DC_ENV_ARGS will correctly handle quoted arguments,
	but it does not understand escape sequences. For example, the string
	"/home/gavin/some dc file.dc" will be correctly parsed, but the string
	"/home/gavin/some \"dc\" file.dc" will include the backslashes.

	The quote parsing will handle either kind of quotes, ' or ". Thus,
	if you have a file with any number of single quotes in the name, you can use
	double quotes as the outside quotes, as in "some 'dc' file.dc", and vice
	versa if you have a file with double quotes. However, handling a file with
	both kinds of quotes in DC_ENV_ARGS is not supported due to the
	complexity of the parsing, though such files are still supported on the
	command-line where the parsing is done by the shell.

	DC_LINE_LENGTH

	: If this environment variable exists and contains an integer that is greater
	than 1 and is less than UINT16_MAX (2\^16-1), dc(1) will output
	lines to that length, including the backslash newline combo. The default
	line length is 70.

	DC_EXPR_EXIT

	: If this variable exists (no matter the contents), dc(1) will exit
	immediately after executing expressions and files given by the -e and/or
	-f command-line options (and any equivalents).

	# EXIT STATUS

	dc(1) returns the following exit statuses:

	0

	: No error.

	1

	: A math error occurred. This follows standard practice of using 1 for
	expected errors, since math errors will happen in the process of normal
	execution.

	Math errors include divide by 0, taking the square root of a negative
	number, using a negative number as a bound for the pseudo-random number
	generator, attempting to convert a negative number to a hardware integer,
	overflow when converting a number to a hardware integer, and attempting to
	use a non-integer where an integer is required.

	Converting to a hardware integer happens for the second operand of the power
	(\^), places (\@), left shift (H), and right shift (h)
	operators.

	2

	: A parse error occurred.

	Parse errors include unexpected EOF, using an invalid character, failing
	to find the end of a string or comment, and using a token where it is
	invalid.

	3

	: A runtime error occurred.

	Runtime errors include assigning an invalid number to ibase, obase,
	or scale; give a bad expression to a read() call, calling read()
	inside of a read() call, type errors, and attempting an operation when
	the stack has too few elements.

	4

	: A fatal error occurred.

	Fatal errors include memory allocation errors, I/O errors, failing to open
	files, attempting to use files that do not have only ASCII characters (dc(1)
	only accepts ASCII characters), attempting to open a directory as a file,
	and giving invalid command-line options.

	The exit status 4 is special; when a fatal error occurs, dc(1) always exits
	and returns 4, no matter what mode dc(1) is in.

	The other statuses will only be returned when dc(1) is not in interactive mode
	(see the INTERACTIVE MODE section), since dc(1) resets its state (see the
	RESET 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
	-i flag or -\-interactive option.

	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 -i flag or
	-\-interactive option.

	# INTERACTIVE MODE

	Like bc(1), dc(1) has an interactive mode and a non-interactive mode.
	Interactive mode is turned on automatically when both stdin and stdout
	are hooked to a terminal, but the -i flag and -\-interactive option can
	turn it on in other cases.

	In interactive mode, dc(1) attempts to recover from errors (see the RESET
	section), and in normal execution, flushes stdout as soon as execution is
	done for the current input.

	# TTY MODE

	If stdin, stdout, and stderr are all connected to a TTY, dc(1) turns
	on "TTY mode."

	TTY mode is required for history to be enabled (see the COMMAND LINE HISTORY
	section). It is also required to enable special handling for SIGINT signals.

	TTY mode is different from interactive mode because interactive mode is required
	in the [bc(1) specification][1], and interactive mode requires only stdin
	and stdout to be connected to a terminal.

	# SIGNAL HANDLING

	Sending a SIGINT will cause dc(1) to stop execution of the current input. If
	dc(1) is in TTY mode (see the TTY MODE section), it will reset (see the
	RESET section). Otherwise, it will clean up and exit.

	Note that "current input" can mean one of two things. If dc(1) is processing
	input from stdin in TTY mode, it will ask for more input. If dc(1) is
	processing input from a file in TTY mode, it will stop processing the file and
	start processing the next file, if one exists, or ask for input from stdin
	if no other file exists.

	This means that if a SIGINT is sent to dc(1) as it is executing a file, it
	can seem as though dc(1) did not respond to the signal since it will immediately
	start executing the next file. This is by design; most files that users execute
	when interacting with dc(1) have function definitions, which are quick to parse.
	If a file takes a long time to execute, there may be a bug in that file. The
	rest of the files could still be executed without problem, allowing the user to
	continue.

	SIGTERM and SIGQUIT cause dc(1) to clean up and exit, and it uses the
	default handler for all other signals. The one exception is SIGHUP; in that
	case, when dc(1) is in TTY mode, a SIGHUP will cause dc(1) to clean up and
	exit.

	# COMMAND LINE HISTORY

	dc(1) supports interactive command-line editing. If dc(1) is in TTY mode (see
	the TTY MODE section), history is enabled. Previous lines can be recalled
	and edited with the arrow keys.

	Note: tabs are converted to 8 spaces.

	# LOCALES

	This dc(1) ships with support for adding error messages for different locales
	and thus, supports LC_MESSAGS.

	# SEE ALSO

	bc(1)

	# STANDARDS

	The dc(1) utility operators are compliant with the operators in the bc(1)
	[IEEE Std 1003.1-2017 (“POSIX.1-2017”)][1] specification.

	# BUGS

	None are known. Report bugs at https://git.yzena.com/gavin/bc.

	# AUTHOR

	Gavin D. Howard <gavin@yzena.com> and contributors.

	[1]: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/bc.html
	diff --git a/contrib/bc/manuals/header_bc.txt b/contrib/bc/manuals/header_bc.txt
	index e07d2e79a1ce..594138f68956 100644
	--- a/contrib/bc/manuals/header_bc.txt
	+++ b/contrib/bc/manuals/header_bc.txt
	@@ -1 +1 @@
	-.TH "BC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "BC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	diff --git a/contrib/bc/manuals/header_bcl.txt b/contrib/bc/manuals/header_bcl.txt
	index 5933f01f2732..26bbefa1b61e 100644
	--- a/contrib/bc/manuals/header_bcl.txt
	+++ b/contrib/bc/manuals/header_bcl.txt
	@@ -1 +1 @@
	-.TH "BCL" "3" "March 2021" "Gavin D. Howard" "Libraries Manual"
	+.TH "BCL" "3" "April 2021" "Gavin D. Howard" "Libraries Manual"
	diff --git a/contrib/bc/manuals/header_dc.txt b/contrib/bc/manuals/header_dc.txt
	index 227aac310a0e..e1e2c98373f5 100644
	--- a/contrib/bc/manuals/header_dc.txt
	+++ b/contrib/bc/manuals/header_dc.txt
	@@ -1 +1 @@
	-.TH "DC" "1" "March 2021" "Gavin D. Howard" "General Commands Manual"
	+.TH "DC" "1" "April 2021" "Gavin D. Howard" "General Commands Manual"
	diff --git a/contrib/bc/release.sh b/contrib/bc/release.sh
	index 902f26ef4d33..e30875f10c17 100755
	--- a/contrib/bc/release.sh
	+++ b/contrib/bc/release.sh
	@@ -1,582 +1,601 @@
	#! /bin/sh
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#

	usage() {
	printf 'usage: %s [run_tests] [generate_tests] [test_with_clang] [test_with_gcc] \n' "$script"
	printf ' [run_sanitizers] [run_valgrind] [run_64_bit] [run_gen_script]\n'
	+ printf ' [test_c11] [test_128_bit]\n'
	exit 1
	}

	header() {

	_header_msg="$1"
	shift

	printf '\n'
	printf '*******************\n'
	printf "$_header_msg"
	printf '\n'
	printf '*******************\n'
	printf '\n'
	}

	do_make() {
	make -j16 "$@"
	}

	configure() {

	_configure_CFLAGS="$1"
	shift

	_configure_CC="$1"
	shift

	_configure_configure_flags="$1"
	shift

	_configure_GEN_HOST="$1"
	shift

	_configure_LONG_BIT="$1"
	shift

	if [ "$gen_tests" -eq 0 ]; then
	_configure_configure_flags="-G $_configure_configure_flags"
	fi

	if [ "$_configure_CC" = "clang" ]; then
	_configure_CFLAGS="$clang_flags $_configure_CFLAGS"
	elif [ "$_configure_CC" = "gcc" ]; then
	_configure_CFLAGS="$gcc_flags $_configure_CFLAGS"
	fi

	_configure_header=$(printf 'Running ./configure.sh %s ...' "$_configure_configure_flags")
	_configure_header=$(printf "$_configure_header\n CC=\"%s\"\n" "$_configure_CC")
	_configure_header=$(printf "$_configure_header\n CFLAGS=\"%s\"\n" "$_configure_CFLAGS")
	_configure_header=$(printf "$_configure_header\n LONG_BIT=%s" "$_configure_LONG_BIT")
	_configure_header=$(printf "$_configure_header\n GEN_HOST=%s" "$_configure_GEN_HOST")

	header "$_configure_header"
	CFLAGS="$_configure_CFLAGS" CC="$_configure_CC" GEN_HOST="$_configure_GEN_HOST" \
	LONG_BIT="$_configure_LONG_BIT" ./configure.sh $_configure_configure_flags > /dev/null
	}

	build() {

	_build_CFLAGS="$1"
	shift

	_build_CC="$1"
	shift

	_build_configure_flags="$1"
	shift

	_build_GEN_HOST="$1"
	shift

	_build_LONG_BIT="$1"
	shift

	configure "$_build_CFLAGS" "$_build_CC" "$_build_configure_flags" "$_build_GEN_HOST" "$_build_LONG_BIT"

	_build_header=$(printf 'Building...\n CC=%s' "$_build_CC")
	_build_header=$(printf "$_build_header\n CFLAGS=\"%s\"" "$_build_CFLAGS")
	_build_header=$(printf "$_build_header\n LONG_BIT=%s" "$_build_LONG_BIT")
	_build_header=$(printf "$_build_header\n GEN_HOST=%s" "$_build_GEN_HOST")

	header "$_build_header"

	do_make > /dev/null 2> "$scriptdir/.test.txt"

	if [ -s "$scriptdir/.test.txt" ]; then
	printf '%s generated warning(s):\n' "$_build_CC"
	printf '\n'
	cat "$scriptdir/.test.txt"
	exit 1
	fi
	}

	runtest() {

	header "Running tests"

	if [ "$#" -gt 0 ]; then
	do_make "$@"
	else
	do_make test
	fi
	}

	runconfigtests() {

	_runconfigtests_CFLAGS="$1"
	shift

	_runconfigtests_CC="$1"
	shift

	_runconfigtests_configure_flags="$1"
	shift

	_runconfigtests_GEN_HOST="$1"
	shift

	_runconfigtests_LONG_BIT="$1"
	shift

	_runconfigtests_run_tests="$1"
	shift

	if [ "$_runconfigtests_run_tests" -ne 0 ]; then
	_runconfigtests_header=$(printf 'Running tests with configure flags')
	else
	_runconfigtests_header=$(printf 'Building with configure flags')
	fi

	_runconfigtests_header=$(printf "$_runconfigtests_header \"%s\" ...\n" "$_runconfigtests_configure_flags")
	_runconfigtests_header=$(printf "$_runconfigtests_header\n CC=%s\n" "$_runconfigseries_CC")
	_runconfigtests_header=$(printf "$_runconfigtests_header\n CFLAGS=\"%s\"" "$_runconfigseries_CFLAGS")
	_runconfigtests_header=$(printf "$_runconfigtests_header\n LONG_BIT=%s" "$_runconfigtests_LONG_BIT")
	_runconfigtests_header=$(printf "$_runconfigtests_header\n GEN_HOST=%s" "$_runconfigtests_GEN_HOST")

	header "$_runconfigtests_header"

	build "$_runconfigtests_CFLAGS" "$_runconfigtests_CC" \
	"$_runconfigtests_configure_flags" "$_runconfigtests_GEN_HOST" \
	"$_runconfigtests_LONG_BIT"

	if [ "$_runconfigtests_run_tests" -ne 0 ]; then
	runtest
	fi

	do_make clean

	build "$_runconfigtests_CFLAGS" "$_runconfigtests_CC" \
	"$_runconfigtests_configure_flags -b" "$_runconfigtests_GEN_HOST" \
	"$_runconfigtests_LONG_BIT"

	if [ "$_runconfigtests_run_tests" -ne 0 ]; then
	runtest
	fi

	do_make clean

	build "$_runconfigtests_CFLAGS" "$_runconfigtests_CC" \
	"$_runconfigtests_configure_flags -d" "$_runconfigtests_GEN_HOST" \
	"$_runconfigtests_LONG_BIT"

	if [ "$_runconfigtests_run_tests" -ne 0 ]; then
	runtest
	fi

	do_make clean
	}

	runconfigseries() {

	_runconfigseries_CFLAGS="$1"
	shift

	_runconfigseries_CC="$1"
	shift

	_runconfigseries_configure_flags="$1"
	shift

	_runconfigseries_run_tests="$1"
	shift

	if [ "$run_64_bit" -ne 0 ]; then

	- runconfigtests "$_runconfigseries_CFLAGS" "$_runconfigseries_CC" \
	- "$_runconfigseries_configure_flags" 1 64 "$_runconfigseries_run_tests"
	+ if [ "$test_128_bit" -ne 0 ]; then
	+ runconfigtests "$_runconfigseries_CFLAGS" "$_runconfigseries_CC" \
	+ "$_runconfigseries_configure_flags" 1 64 "$_runconfigseries_run_tests"
	+ fi

	if [ "$run_gen_script" -ne 0 ]; then
	runconfigtests "$_runconfigseries_CFLAGS" "$_runconfigseries_CC" \
	"$_runconfigseries_configure_flags" 0 64 "$_runconfigseries_run_tests"
	fi

	runconfigtests "$_runconfigseries_CFLAGS -DBC_RAND_BUILTIN=0" "$_runconfigseries_CC" \
	"$_runconfigseries_configure_flags" 1 64 "$_runconfigseries_run_tests"

	fi

	runconfigtests "$_runconfigseries_CFLAGS" "$_runconfigseries_CC" \
	"$_runconfigseries_configure_flags" 1 32 "$_runconfigseries_run_tests"

	if [ "$run_gen_script" -ne 0 ]; then
	runconfigtests "$_runconfigseries_CFLAGS" "$_runconfigseries_CC" \
	"$_runconfigseries_configure_flags" 0 32 "$_runconfigseries_run_tests"
	fi
	}

	runtestseries() {

	_runtestseries_CFLAGS="$1"
	shift

	_runtestseries_CC="$1"
	shift

	_runtestseries_configure_flags="$1"
	shift

	_runtestseries_run_tests="$1"
	shift

	_runtestseries_flags="E H N P EH EN EP HN HP NP EHN EHP ENP HNP EHNP"

	runconfigseries "$_runtestseries_CFLAGS" "$_runtestseries_CC" \
	"$_runtestseries_configure_flags" "$_runtestseries_run_tests"

	for f in $_runtestseries_flags; do
	runconfigseries "$_runtestseries_CFLAGS" "$_runtestseries_CC" \
	"$_runtestseries_configure_flags -$f" "$_runtestseries_run_tests"
	done
	}

	runlibtests() {

	_runlibtests_CFLAGS="$1"
	shift

	_runlibtests_CC="$1"
	shift

	_runlibtests_configure_flags="$1"
	shift

	_runlibtests_run_tests="$1"
	shift

	_runlibtests_configure_flags="$_runlibtests_configure_flags -a"

	build "$_runlibtests_CFLAGS" "$_runlibtests_CC" "$_runlibtests_configure_flags" 1 64

	if [ "$_runlibtests_run_tests" -ne 0 ]; then
	runtest
	fi

	build "$_runlibtests_CFLAGS" "$_runlibtests_CC" "$_runlibtests_configure_flags" 1 32

	if [ "$_runlibtests_run_tests" -ne 0 ]; then
	runtest
	fi
	}

	runtests() {

	_runtests_CFLAGS="$1"
	shift

	_runtests_CC="$1"
	shift

	_runtests_configure_flags="$1"
	shift

	_runtests_run_tests="$1"
	shift

	runtestseries "-std=c99 $_runtests_CFLAGS" "$_runtests_CC" "$_runtests_configure_flags" "$_runtests_run_tests"
	- runtestseries "-std=c11 $_runtests_CFLAGS" "$_runtests_CC" "$_runtests_configure_flags" "$_runtests_run_tests"
	+
	+ if [ "$test_c11" -ne 0 ]; then
	+ runtestseries "-std=c11 $_runtests_CFLAGS" "$_runtests_CC" "$_runtests_configure_flags" "$_runtests_run_tests"
	+ fi
	}

	karatsuba() {

	header "Running Karatsuba tests"
	do_make karatsuba_test
	}

	vg() {

	header "Running valgrind"

	if [ "$run_64_bit" -ne 0 ]; then
	_vg_bits=64
	else
	_vg_bits=32
	fi

	build "$debug" "gcc" "-O0 -gv" "1" "$_vg_bits"
	runtest test

	do_make clean_config

	build "$debug" "gcc" "-O0 -gvb" "1" "$_vg_bits"
	runtest test

	do_make clean_config

	build "$debug" "gcc" "-O0 -gvd" "1" "$_vg_bits"
	runtest test

	do_make clean_config
	}

	debug() {

	_debug_CC="$1"
	shift

	_debug_run_tests="$1"
	shift

	runtests "$debug" "$_debug_CC" "-g" "$_debug_run_tests"

	if [ "$_debug_CC" = "clang" -a "$run_sanitizers" -ne 0 ]; then
	runtests "$debug -fsanitize=undefined" "$_debug_CC" "-g" "$_debug_run_tests"
	fi

	runlibtests "$debug" "$_debug_CC" "-g" "$_debug_run_tests"

	if [ "$_debug_CC" = "clang" -a "$run_sanitizers" -ne 0 ]; then
	runlibtests "$debug -fsanitize=undefined" "$_debug_CC" "-g" "$_debug_run_tests"
	fi
	}

	release() {

	_release_CC="$1"
	shift

	_release_run_tests="$1"
	shift

	runtests "$release" "$_release_CC" "-O3" "$_release_run_tests"

	runlibtests "$release" "$_release_CC" "-O3" "$_release_run_tests"
	}

	reldebug() {

	_reldebug_CC="$1"
	shift

	_reldebug_run_tests="$1"
	shift

	runtests "$debug" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"

	if [ "$_reldebug_CC" = "clang" -a "$run_sanitizers" -ne 0 ]; then
	runtests "$debug -fsanitize=address" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"
	runtests "$debug -fsanitize=memory" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"
	fi

	runlibtests "$debug" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"

	if [ "$_reldebug_CC" = "clang" -a "$run_sanitizers" -ne 0 ]; then
	runlibtests "$debug -fsanitize=address" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"
	runlibtests "$debug -fsanitize=memory" "$_reldebug_CC" "-gO3" "$_reldebug_run_tests"
	fi
	}

	minsize() {

	_minsize_CC="$1"
	shift

	_minsize_run_tests="$1"
	shift

	runtests "$release" "$_minsize_CC" "-Os" "$_minsize_run_tests"

	runlibtests "$release" "$_minsize_CC" "-Os" "$_minsize_run_tests"
	}

	build_set() {

	_build_set_CC="$1"
	shift

	_build_set_run_tests="$1"
	shift

	debug "$_build_set_CC" "$_build_set_run_tests"
	release "$_build_set_CC" "$_build_set_run_tests"
	reldebug "$_build_set_CC" "$_build_set_run_tests"
	minsize "$_build_set_CC" "$_build_set_run_tests"
	}

	clang_flags="-Weverything -Wno-padded -Wno-switch-enum -Wno-format-nonliteral"
	clang_flags="$clang_flags -Wno-cast-align -Wno-missing-noreturn -Wno-disabled-macro-expansion"
	clang_flags="$clang_flags -Wno-unreachable-code -Wno-unreachable-code-return"
	clang_flags="$clang_flags -Wno-implicit-fallthrough"
	gcc_flags="-Wno-maybe-uninitialized -Wno-clobbered"

	cflags="-Wall -Wextra -Werror -pedantic -Wno-conditional-uninitialized"

	debug="$cflags -fno-omit-frame-pointer"
	release="$cflags -DNDEBUG"

	set -e

	script="$0"
	scriptdir=$(dirname "$script")

	if [ "$#" -gt 0 ]; then
	run_tests="$1"
	shift
	else
	run_tests=1
	fi

	if [ "$#" -gt 0 ]; then
	gen_tests="$1"
	shift
	else
	gen_tests=1
	fi

	if [ "$#" -gt 0 ]; then
	test_with_clang="$1"
	shift
	else
	test_with_clang=1
	fi

	if [ "$#" -gt 0 ]; then
	test_with_gcc="$1"
	shift
	else
	test_with_gcc=1
	fi

	if [ "$#" -gt 0 ]; then
	run_sanitizers="$1"
	shift
	else
	run_sanitizers=1
	fi

	if [ "$#" -gt 0 ]; then
	run_valgrind="$1"
	shift
	else
	run_valgrind=1
	fi

	if [ "$#" -gt 0 ]; then
	run_64_bit="$1"
	shift
	else
	run_64_bit=1
	fi

	if [ "$#" -gt 0 ]; then
	run_gen_script="$1"
	shift
	else
	run_gen_script=0
	fi

	+if [ "$#" -gt 0 ]; then
	+ test_c11="$1"
	+ shift
	+else
	+ test_c11=0
	+fi
	+
	+if [ "$#" -gt 0 ]; then
	+ test_128_bit="$1"
	+ shift
	+else
	+ test_128_bit=0
	+fi
	+
	if [ "$run_64_bit" -ne 0 ]; then
	bits=64
	else
	bits=32
	fi

	cd "$scriptdir"

	if [ "$test_with_clang" -ne 0 ]; then
	defcc="clang"
	elif [ "$test_with_gcc" -ne 0 ]; then
	defcc="gcc"
	else
	defcc="c99"
	fi

	export ASAN_OPTIONS="abort_on_error=1,allocator_may_return_null=1"
	export UBSAN_OPTIONS="print_stack_trace=1,silence_unsigned_overflow=1"

	build "$debug" "$defcc" "-g" "1" "$bits"

	header "Running math library under --standard"

	printf 'quit\n' \| bin/bc -ls

	-version=$(make version)
	-
	do_make clean_tests

	if [ "$test_with_clang" -ne 0 ]; then
	build_set "clang" "$run_tests"
	fi

	if [ "$test_with_gcc" -ne 0 ]; then
	build_set "gcc" "$run_tests"
	fi

	if [ "$run_tests" -ne 0 ]; then

	build "$release" "$defcc" "-O3" "1" "$bits"

	karatsuba

	if [ "$run_valgrind" -ne 0 -a "$test_with_gcc" -ne 0 ]; then
	vg
	fi

	printf '\n'
	printf 'Tests successful.\n'

	set +e

	command -v afl-gcc > /dev/null 2>&1
	err="$?"

	set -e

	if [ "$err" -eq 0 ]; then

	header "Configuring for afl-gcc..."

	configure "$debug $gcc_flags -DBC_ENABLE_RAND=0" "afl-gcc" "-HNP -gO3" "1" "$bits"

	printf '\n'
	printf 'Run make\n'
	printf '\n'
	printf 'Then run %s/tests/randmath.py and the fuzzer.\n' "$scriptdir"
	printf '\n'
	printf 'Then run ASan on the fuzzer test cases with the following build:\n'
	printf '\n'
	printf ' CFLAGS="-fsanitize=address -fno-omit-frame-pointer -DBC_ENABLE_RAND=0" ./configure.sh -gO3 -HNPS\n'
	printf ' make\n'
	printf '\n'
	printf 'Then run the GitHub release script as follows:\n'
	printf '\n'
	- printf ' <github_release> %s release.sh RELEASE.md\\\n' "$version"
	- printf ' tests/afl.py tests/radamsa.sh tests/radamsa.txt tests/randmath.py \\\n'
	+ printf ' <github_release> <version> .gitignore .gitattributes\\\n'
	+ printf ' manpage.sh release.sh RELEASE.md tests/afl.py\\\n'
	+ printf ' tests/radamsa.sh tests/radamsa.txt tests/randmath.py\\\n'
	printf ' tests/fuzzing/ tests/bc/scripts/timeconst.bc\n'

	fi

	fi
	diff --git a/contrib/bc/src/args.c b/contrib/bc/src/args.c
	index 9c26b7c18790..c764ca837e2a 100644
	--- a/contrib/bc/src/args.c
	+++ b/contrib/bc/src/args.c
	@@ -1,221 +1,230 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code for processing command-line arguments.
	*
	*/

	#include <assert.h>
	#include <ctype.h>
	#include <stdbool.h>
	#include <stdlib.h>
	#include <string.h>

	+#ifndef _WIN32
	#include <unistd.h>
	+#endif // _WIN32

	#include <vector.h>
	#include <read.h>
	#include <args.h>
	#include <opt.h>

	static const BcOptLong bc_args_lopt[] = {

	{ "expression", BC_OPT_REQUIRED, 'e' },
	{ "file", BC_OPT_REQUIRED, 'f' },
	{ "help", BC_OPT_NONE, 'h' },
	{ "interactive", BC_OPT_NONE, 'i' },
	{ "no-prompt", BC_OPT_NONE, 'P' },
	+ { "no-read-prompt", BC_OPT_NONE, 'R' },
	#if BC_ENABLED
	{ "global-stacks", BC_OPT_BC_ONLY, 'g' },
	{ "mathlib", BC_OPT_BC_ONLY, 'l' },
	{ "quiet", BC_OPT_BC_ONLY, 'q' },
	{ "standard", BC_OPT_BC_ONLY, 's' },
	{ "warn", BC_OPT_BC_ONLY, 'w' },
	#endif // BC_ENABLED
	{ "version", BC_OPT_NONE, 'v' },
	{ "version", BC_OPT_NONE, 'V' },
	#if DC_ENABLED
	{ "extended-register", BC_OPT_DC_ONLY, 'x' },
	#endif // DC_ENABLED
	{ NULL, 0, 0 },

	};

	static void bc_args_exprs(const char *str) {
	BC_SIG_ASSERT_LOCKED;
	if (vm.exprs.v == NULL) bc_vec_init(&vm.exprs, sizeof(uchar), NULL);
	bc_vec_concat(&vm.exprs, str);
	bc_vec_concat(&vm.exprs, "\n");
	}

	static void bc_args_file(const char *file) {

	char *buf;

	BC_SIG_ASSERT_LOCKED;

	vm.file = file;

	bc_read_file(file, &buf);
	bc_args_exprs(buf);
	free(buf);
	}

	void bc_args(int argc, char *argv[], bool exit_exprs) {

	int c;
	size_t i;
	bool do_exit = false, version = false;
	BcOpt opts;

	BC_SIG_ASSERT_LOCKED;

	bc_opt_init(&opts, argv);

	while ((c = bc_opt_parse(&opts, bc_args_lopt)) != -1) {

	switch (c) {

	case 'e':
	{
	if (vm.no_exit_exprs)
	bc_vm_verr(BC_ERR_FATAL_OPTION, "-e (--expression)");
	bc_args_exprs(opts.optarg);
	vm.exit_exprs = (exit_exprs \|\| vm.exit_exprs);
	break;
	}

	case 'f':
	{
	if (!strcmp(opts.optarg, "-")) vm.no_exit_exprs = true;
	else {
	if (vm.no_exit_exprs)
	bc_vm_verr(BC_ERR_FATAL_OPTION, "-f (--file)");
	bc_args_file(opts.optarg);
	vm.exit_exprs = (exit_exprs \|\| vm.exit_exprs);
	}
	break;
	}

	case 'h':
	{
	bc_vm_info(vm.help);
	do_exit = true;
	break;
	}

	case 'i':
	{
	vm.flags \|= BC_FLAG_I;
	break;
	}

	case 'P':
	{
	vm.flags \|= BC_FLAG_P;
	break;
	}

	+ case 'R':
	+ {
	+ vm.flags \|= BC_FLAG_R;
	+ break;
	+ }
	+
	#if BC_ENABLED
	case 'g':
	{
	assert(BC_IS_BC);
	vm.flags \|= BC_FLAG_G;
	break;
	}

	case 'l':
	{
	assert(BC_IS_BC);
	vm.flags \|= BC_FLAG_L;
	break;
	}

	case 'q':
	{
	assert(BC_IS_BC);
	// Do nothing.
	break;
	}

	case 's':
	{
	assert(BC_IS_BC);
	vm.flags \|= BC_FLAG_S;
	break;
	}

	case 'w':
	{
	assert(BC_IS_BC);
	vm.flags \|= BC_FLAG_W;
	break;
	}
	#endif // BC_ENABLED

	case 'V':
	case 'v':
	{
	do_exit = version = true;
	break;
	}

	#if DC_ENABLED
	case 'x':
	{
	assert(BC_IS_DC);
	vm.flags \|= DC_FLAG_X;
	break;
	}
	#endif // DC_ENABLED

	#ifndef NDEBUG
	// We shouldn't get here because bc_opt_error()/bc_vm_error() should
	// longjmp() out.
	case '?':
	case ':':
	default:
	{
	abort();
	}
	#endif // NDEBUG
	}
	}

	if (version) bc_vm_info(NULL);
	if (do_exit) exit((int) vm.status);

	if (opts.optind < (size_t) argc && vm.files.v == NULL)
	bc_vec_init(&vm.files, sizeof(char*), NULL);

	for (i = opts.optind; i < (size_t) argc; ++i)
	bc_vec_push(&vm.files, argv + i);
	}
	diff --git a/contrib/bc/src/data.c b/contrib/bc/src/data.c
	index 08b8b19b5692..7611d4f05171 100644
	--- a/contrib/bc/src/data.c
	+++ b/contrib/bc/src/data.c
	@@ -1,1025 +1,1031 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Constant data for bc.
	*
	*/

	#include <args.h>
	#include <lex.h>
	#include <parse.h>
	#include <bc.h>
	#include <dc.h>
	#include <num.h>
	#include <rand.h>
	#include <program.h>
	#include <vm.h>

	#if !BC_ENABLE_LIBRARY

	#if BC_ENABLED
	const char bc_sig_msg[] = "\ninterrupt (type \"quit\" to exit)\n";
	const uchar bc_sig_msg_len = (uchar) (sizeof(bc_sig_msg) - 1);
	#endif // BC_ENABLED
	#if DC_ENABLED
	const char dc_sig_msg[] = "\ninterrupt (type \"q\" to exit)\n";
	const uchar dc_sig_msg_len = (uchar) (sizeof(dc_sig_msg) - 1);
	#endif // DC_ENABLED

	const char bc_copyright[] =
	"Copyright (c) 2018-2021 Gavin D. Howard and contributors\n"
	"Report bugs at: https://git.yzena.com/gavin/bc\n\n"
	"This is free software with ABSOLUTELY NO WARRANTY.\n";

	const char* const bc_err_func_header = "Function:";
	const char* const bc_err_line = ":%zu";

	const char *bc_errs[] = {
	"Math error:",
	"Parse error:",
	"Runtime error:",
	"Fatal error:",
	#if BC_ENABLED
	"Warning:",
	#endif // BC_ENABLED
	};

	const uchar bc_err_ids[] = {

	BC_ERR_IDX_MATH, BC_ERR_IDX_MATH, BC_ERR_IDX_MATH, BC_ERR_IDX_MATH,

	BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL,
	BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL, BC_ERR_IDX_FATAL,

	BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC,
	BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC,
	BC_ERR_IDX_EXEC, BC_ERR_IDX_EXEC,

	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE,
	#if BC_ENABLED
	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,

	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE, BC_ERR_IDX_PARSE,
	BC_ERR_IDX_PARSE,
	#endif // BC_ENABLED

	};

	const char* const bc_err_msgs[] = {

	"negative number",
	"non-integer number",
	"overflow: number cannot fit",
	"divide by 0",

	"memory allocation failed",
	"I/O error",
	"cannot open file: %s",
	"file is not ASCII: %s",
	"path is a directory: %s",
	"bad command-line option: \"%s\"",
	"option requires an argument: '%c' (\"%s\")",
	"option takes no arguments: '%c' (\"%s\")",

	"bad ibase: must be [%lu, %lu]",
	"bad obase: must be [%lu, %lu]",
	"bad scale: must be [%lu, %lu]",
	"bad read() expression",
	"read() call inside of a read() call",
	"variable or array element is the wrong type",
	#if DC_ENABLED
	"stack has too few elements",
	#else // DC_ENABLED
	NULL,
	#endif // DC_ENABLED
	#if BC_ENABLED
	"wrong number of parameters; need %zu, have %zu",
	"undefined function: %s()",
	"cannot use a void value in an expression",
	#else
	NULL, NULL, NULL,
	#endif // BC_ENABLED

	"end of file",
	"bad character '%c'",
	"string end cannot be found",
	"comment end cannot be found",
	"bad token",
	#if BC_ENABLED
	"bad expression",
	"empty expression",
	"bad print statement",
	"bad function definition",
	("bad assignment: left side must be scale, ibase, "
	"obase, seed, last, var, or array element"),
	"no auto variable found",
	"function parameter or auto \"%s%s\" already exists",
	"block end cannot be found",
	"cannot return a value from void function: %s()",
	"var cannot be a reference: %s",

	"POSIX does not allow names longer than 1 character: %s",
	"POSIX does not allow '#' script comments",
	"POSIX does not allow the following keyword: %s",
	"POSIX does not allow a period ('.') as a shortcut for the last result",
	"POSIX requires parentheses around return expressions",
	"POSIX does not allow the following operator: %s",
	"POSIX does not allow comparison operators outside if statements or loops",
	"POSIX requires 0 or 1 comparison operators per condition",
	"POSIX requires all 3 parts of a for loop to be non-empty",
	#if BC_ENABLE_EXTRA_MATH
	"POSIX does not allow exponential notation",
	#else
	NULL,
	#endif // BC_ENABLE_EXTRA_MATH
	"POSIX does not allow array references as function parameters",
	"POSIX does not allow void functions",
	"POSIX requires the left brace be on the same line as the function header",
	#endif // BC_ENABLED

	};

	+#if BC_ENABLE_HISTORY
	+const BcFlushType bc_flush_none = BC_FLUSH_NO_EXTRAS_NO_CLEAR;
	+const BcFlushType bc_flush_err = BC_FLUSH_NO_EXTRAS_CLEAR;
	+const BcFlushType bc_flush_save = BC_FLUSH_SAVE_EXTRAS_CLEAR;
	+#endif // BC_ENABLE_HISTORY
	+
	#if BC_ENABLE_HISTORY
	const char *bc_history_bad_terms[] = { "dumb", "cons25", "emacs", NULL };

	const char bc_history_tab[] = " ";
	const size_t bc_history_tab_len = sizeof(bc_history_tab) - 1;

	// These are listed in ascending order for efficiency.
	const uint32_t bc_history_wchars[][2] = {
	{ 0x1100, 0x115F },
	{ 0x231A, 0x231B },
	{ 0x2329, 0x232A },
	{ 0x23E9, 0x23EC },
	{ 0x23F0, 0x23F0 },
	{ 0x23F3, 0x23F3 },
	{ 0x25FD, 0x25FE },
	{ 0x2614, 0x2615 },
	{ 0x2648, 0x2653 },
	{ 0x267F, 0x267F },
	{ 0x2693, 0x2693 },
	{ 0x26A1, 0x26A1 },
	{ 0x26AA, 0x26AB },
	{ 0x26BD, 0x26BE },
	{ 0x26C4, 0x26C5 },
	{ 0x26CE, 0x26CE },
	{ 0x26D4, 0x26D4 },
	{ 0x26EA, 0x26EA },
	{ 0x26F2, 0x26F3 },
	{ 0x26F5, 0x26F5 },
	{ 0x26FA, 0x26FA },
	{ 0x26FD, 0x26FD },
	{ 0x2705, 0x2705 },
	{ 0x270A, 0x270B },
	{ 0x2728, 0x2728 },
	{ 0x274C, 0x274C },
	{ 0x274E, 0x274E },
	{ 0x2753, 0x2755 },
	{ 0x2757, 0x2757 },
	{ 0x2795, 0x2797 },
	{ 0x27B0, 0x27B0 },
	{ 0x27BF, 0x27BF },
	{ 0x2B1B, 0x2B1C },
	{ 0x2B50, 0x2B50 },
	{ 0x2B55, 0x2B55 },
	{ 0x2E80, 0x2E99 },
	{ 0x2E9B, 0x2EF3 },
	{ 0x2F00, 0x2FD5 },
	{ 0x2FF0, 0x2FFB },
	{ 0x3001, 0x303E },
	{ 0x3041, 0x3096 },
	{ 0x3099, 0x30FF },
	{ 0x3105, 0x312D },
	{ 0x3131, 0x318E },
	{ 0x3190, 0x31BA },
	{ 0x31C0, 0x31E3 },
	{ 0x31F0, 0x321E },
	{ 0x3220, 0x3247 },
	{ 0x3250, 0x32FE },
	{ 0x3300, 0x4DBF },
	{ 0x4E00, 0xA48C },
	{ 0xA490, 0xA4C6 },
	{ 0xA960, 0xA97C },
	{ 0xAC00, 0xD7A3 },
	{ 0xF900, 0xFAFF },
	{ 0xFE10, 0xFE19 },
	{ 0xFE30, 0xFE52 },
	{ 0xFE54, 0xFE66 },
	{ 0xFE68, 0xFE6B },
	{ 0x16FE0, 0x16FE0 },
	{ 0x17000, 0x187EC },
	{ 0x18800, 0x18AF2 },
	{ 0x1B000, 0x1B001 },
	{ 0x1F004, 0x1F004 },
	{ 0x1F0CF, 0x1F0CF },
	{ 0x1F18E, 0x1F18E },
	{ 0x1F191, 0x1F19A },
	{ 0x1F200, 0x1F202 },
	{ 0x1F210, 0x1F23B },
	{ 0x1F240, 0x1F248 },
	{ 0x1F250, 0x1F251 },
	{ 0x1F300, 0x1F320 },
	{ 0x1F32D, 0x1F335 },
	{ 0x1F337, 0x1F37C },
	{ 0x1F37E, 0x1F393 },
	{ 0x1F3A0, 0x1F3CA },
	{ 0x1F3CF, 0x1F3D3 },
	{ 0x1F3E0, 0x1F3F0 },
	{ 0x1F3F4, 0x1F3F4 },
	{ 0x1F3F8, 0x1F43E },
	{ 0x1F440, 0x1F440 },
	{ 0x1F442, 0x1F4FC },
	{ 0x1F4FF, 0x1F53D },
	{ 0x1F54B, 0x1F54E },
	{ 0x1F550, 0x1F567 },
	{ 0x1F57A, 0x1F57A },
	{ 0x1F595, 0x1F596 },
	{ 0x1F5A4, 0x1F5A4 },
	{ 0x1F5FB, 0x1F64F },
	{ 0x1F680, 0x1F6C5 },
	{ 0x1F6CC, 0x1F6CC },
	{ 0x1F6D0, 0x1F6D2 },
	{ 0x1F6EB, 0x1F6EC },
	{ 0x1F6F4, 0x1F6F6 },
	{ 0x1F910, 0x1F91E },
	{ 0x1F920, 0x1F927 },
	{ 0x1F930, 0x1F930 },
	{ 0x1F933, 0x1F93E },
	{ 0x1F940, 0x1F94B },
	{ 0x1F950, 0x1F95E },
	{ 0x1F980, 0x1F991 },
	{ 0x1F9C0, 0x1F9C0 },
	{ 0x20000, 0x2FFFD },
	{ 0x30000, 0x3FFFD },
	};

	const size_t bc_history_wchars_len =
	sizeof(bc_history_wchars) / sizeof(bc_history_wchars[0]);

	// These are listed in ascending order for efficiency.
	const uint32_t bc_history_combo_chars[] = {
	0x0300,0x0301,0x0302,0x0303,0x0304,0x0305,0x0306,0x0307,
	0x0308,0x0309,0x030A,0x030B,0x030C,0x030D,0x030E,0x030F,
	0x0310,0x0311,0x0312,0x0313,0x0314,0x0315,0x0316,0x0317,
	0x0318,0x0319,0x031A,0x031B,0x031C,0x031D,0x031E,0x031F,
	0x0320,0x0321,0x0322,0x0323,0x0324,0x0325,0x0326,0x0327,
	0x0328,0x0329,0x032A,0x032B,0x032C,0x032D,0x032E,0x032F,
	0x0330,0x0331,0x0332,0x0333,0x0334,0x0335,0x0336,0x0337,
	0x0338,0x0339,0x033A,0x033B,0x033C,0x033D,0x033E,0x033F,
	0x0340,0x0341,0x0342,0x0343,0x0344,0x0345,0x0346,0x0347,
	0x0348,0x0349,0x034A,0x034B,0x034C,0x034D,0x034E,0x034F,
	0x0350,0x0351,0x0352,0x0353,0x0354,0x0355,0x0356,0x0357,
	0x0358,0x0359,0x035A,0x035B,0x035C,0x035D,0x035E,0x035F,
	0x0360,0x0361,0x0362,0x0363,0x0364,0x0365,0x0366,0x0367,
	0x0368,0x0369,0x036A,0x036B,0x036C,0x036D,0x036E,0x036F,
	0x0483,0x0484,0x0485,0x0486,0x0487,0x0591,0x0592,0x0593,
	0x0594,0x0595,0x0596,0x0597,0x0598,0x0599,0x059A,0x059B,
	0x059C,0x059D,0x059E,0x059F,0x05A0,0x05A1,0x05A2,0x05A3,
	0x05A4,0x05A5,0x05A6,0x05A7,0x05A8,0x05A9,0x05AA,0x05AB,
	0x05AC,0x05AD,0x05AE,0x05AF,0x05B0,0x05B1,0x05B2,0x05B3,
	0x05B4,0x05B5,0x05B6,0x05B7,0x05B8,0x05B9,0x05BA,0x05BB,
	0x05BC,0x05BD,0x05BF,0x05C1,0x05C2,0x05C4,0x05C5,0x05C7,
	0x0610,0x0611,0x0612,0x0613,0x0614,0x0615,0x0616,0x0617,
	0x0618,0x0619,0x061A,0x064B,0x064C,0x064D,0x064E,0x064F,
	0x0650,0x0651,0x0652,0x0653,0x0654,0x0655,0x0656,0x0657,
	0x0658,0x0659,0x065A,0x065B,0x065C,0x065D,0x065E,0x065F,
	0x0670,0x06D6,0x06D7,0x06D8,0x06D9,0x06DA,0x06DB,0x06DC,
	0x06DF,0x06E0,0x06E1,0x06E2,0x06E3,0x06E4,0x06E7,0x06E8,
	0x06EA,0x06EB,0x06EC,0x06ED,0x0711,0x0730,0x0731,0x0732,
	0x0733,0x0734,0x0735,0x0736,0x0737,0x0738,0x0739,0x073A,
	0x073B,0x073C,0x073D,0x073E,0x073F,0x0740,0x0741,0x0742,
	0x0743,0x0744,0x0745,0x0746,0x0747,0x0748,0x0749,0x074A,
	0x07A6,0x07A7,0x07A8,0x07A9,0x07AA,0x07AB,0x07AC,0x07AD,
	0x07AE,0x07AF,0x07B0,0x07EB,0x07EC,0x07ED,0x07EE,0x07EF,
	0x07F0,0x07F1,0x07F2,0x07F3,0x0816,0x0817,0x0818,0x0819,
	0x081B,0x081C,0x081D,0x081E,0x081F,0x0820,0x0821,0x0822,
	0x0823,0x0825,0x0826,0x0827,0x0829,0x082A,0x082B,0x082C,
	0x082D,0x0859,0x085A,0x085B,0x08D4,0x08D5,0x08D6,0x08D7,
	0x08D8,0x08D9,0x08DA,0x08DB,0x08DC,0x08DD,0x08DE,0x08DF,
	0x08E0,0x08E1,0x08E3,0x08E4,0x08E5,0x08E6,0x08E7,0x08E8,
	0x08E9,0x08EA,0x08EB,0x08EC,0x08ED,0x08EE,0x08EF,0x08F0,
	0x08F1,0x08F2,0x08F3,0x08F4,0x08F5,0x08F6,0x08F7,0x08F8,
	0x08F9,0x08FA,0x08FB,0x08FC,0x08FD,0x08FE,0x08FF,0x0900,
	0x0901,0x0902,0x093A,0x093C,0x0941,0x0942,0x0943,0x0944,
	0x0945,0x0946,0x0947,0x0948,0x094D,0x0951,0x0952,0x0953,
	0x0954,0x0955,0x0956,0x0957,0x0962,0x0963,0x0981,0x09BC,
	0x09C1,0x09C2,0x09C3,0x09C4,0x09CD,0x09E2,0x09E3,0x0A01,
	0x0A02,0x0A3C,0x0A41,0x0A42,0x0A47,0x0A48,0x0A4B,0x0A4C,
	0x0A4D,0x0A51,0x0A70,0x0A71,0x0A75,0x0A81,0x0A82,0x0ABC,
	0x0AC1,0x0AC2,0x0AC3,0x0AC4,0x0AC5,0x0AC7,0x0AC8,0x0ACD,
	0x0AE2,0x0AE3,0x0B01,0x0B3C,0x0B3F,0x0B41,0x0B42,0x0B43,
	0x0B44,0x0B4D,0x0B56,0x0B62,0x0B63,0x0B82,0x0BC0,0x0BCD,
	0x0C00,0x0C3E,0x0C3F,0x0C40,0x0C46,0x0C47,0x0C48,0x0C4A,
	0x0C4B,0x0C4C,0x0C4D,0x0C55,0x0C56,0x0C62,0x0C63,0x0C81,
	0x0CBC,0x0CBF,0x0CC6,0x0CCC,0x0CCD,0x0CE2,0x0CE3,0x0D01,
	0x0D41,0x0D42,0x0D43,0x0D44,0x0D4D,0x0D62,0x0D63,0x0DCA,
	0x0DD2,0x0DD3,0x0DD4,0x0DD6,0x0E31,0x0E34,0x0E35,0x0E36,
	0x0E37,0x0E38,0x0E39,0x0E3A,0x0E47,0x0E48,0x0E49,0x0E4A,
	0x0E4B,0x0E4C,0x0E4D,0x0E4E,0x0EB1,0x0EB4,0x0EB5,0x0EB6,
	0x0EB7,0x0EB8,0x0EB9,0x0EBB,0x0EBC,0x0EC8,0x0EC9,0x0ECA,
	0x0ECB,0x0ECC,0x0ECD,0x0F18,0x0F19,0x0F35,0x0F37,0x0F39,
	0x0F71,0x0F72,0x0F73,0x0F74,0x0F75,0x0F76,0x0F77,0x0F78,
	0x0F79,0x0F7A,0x0F7B,0x0F7C,0x0F7D,0x0F7E,0x0F80,0x0F81,
	0x0F82,0x0F83,0x0F84,0x0F86,0x0F87,0x0F8D,0x0F8E,0x0F8F,
	0x0F90,0x0F91,0x0F92,0x0F93,0x0F94,0x0F95,0x0F96,0x0F97,
	0x0F99,0x0F9A,0x0F9B,0x0F9C,0x0F9D,0x0F9E,0x0F9F,0x0FA0,
	0x0FA1,0x0FA2,0x0FA3,0x0FA4,0x0FA5,0x0FA6,0x0FA7,0x0FA8,
	0x0FA9,0x0FAA,0x0FAB,0x0FAC,0x0FAD,0x0FAE,0x0FAF,0x0FB0,
	0x0FB1,0x0FB2,0x0FB3,0x0FB4,0x0FB5,0x0FB6,0x0FB7,0x0FB8,
	0x0FB9,0x0FBA,0x0FBB,0x0FBC,0x0FC6,0x102D,0x102E,0x102F,
	0x1030,0x1032,0x1033,0x1034,0x1035,0x1036,0x1037,0x1039,
	0x103A,0x103D,0x103E,0x1058,0x1059,0x105E,0x105F,0x1060,
	0x1071,0x1072,0x1073,0x1074,0x1082,0x1085,0x1086,0x108D,
	0x109D,0x135D,0x135E,0x135F,0x1712,0x1713,0x1714,0x1732,
	0x1733,0x1734,0x1752,0x1753,0x1772,0x1773,0x17B4,0x17B5,
	0x17B7,0x17B8,0x17B9,0x17BA,0x17BB,0x17BC,0x17BD,0x17C6,
	0x17C9,0x17CA,0x17CB,0x17CC,0x17CD,0x17CE,0x17CF,0x17D0,
	0x17D1,0x17D2,0x17D3,0x17DD,0x180B,0x180C,0x180D,0x1885,
	0x1886,0x18A9,0x1920,0x1921,0x1922,0x1927,0x1928,0x1932,
	0x1939,0x193A,0x193B,0x1A17,0x1A18,0x1A1B,0x1A56,0x1A58,
	0x1A59,0x1A5A,0x1A5B,0x1A5C,0x1A5D,0x1A5E,0x1A60,0x1A62,
	0x1A65,0x1A66,0x1A67,0x1A68,0x1A69,0x1A6A,0x1A6B,0x1A6C,
	0x1A73,0x1A74,0x1A75,0x1A76,0x1A77,0x1A78,0x1A79,0x1A7A,
	0x1A7B,0x1A7C,0x1A7F,0x1AB0,0x1AB1,0x1AB2,0x1AB3,0x1AB4,
	0x1AB5,0x1AB6,0x1AB7,0x1AB8,0x1AB9,0x1ABA,0x1ABB,0x1ABC,
	0x1ABD,0x1B00,0x1B01,0x1B02,0x1B03,0x1B34,0x1B36,0x1B37,
	0x1B38,0x1B39,0x1B3A,0x1B3C,0x1B42,0x1B6B,0x1B6C,0x1B6D,
	0x1B6E,0x1B6F,0x1B70,0x1B71,0x1B72,0x1B73,0x1B80,0x1B81,
	0x1BA2,0x1BA3,0x1BA4,0x1BA5,0x1BA8,0x1BA9,0x1BAB,0x1BAC,
	0x1BAD,0x1BE6,0x1BE8,0x1BE9,0x1BED,0x1BEF,0x1BF0,0x1BF1,
	0x1C2C,0x1C2D,0x1C2E,0x1C2F,0x1C30,0x1C31,0x1C32,0x1C33,
	0x1C36,0x1C37,0x1CD0,0x1CD1,0x1CD2,0x1CD4,0x1CD5,0x1CD6,
	0x1CD7,0x1CD8,0x1CD9,0x1CDA,0x1CDB,0x1CDC,0x1CDD,0x1CDE,
	0x1CDF,0x1CE0,0x1CE2,0x1CE3,0x1CE4,0x1CE5,0x1CE6,0x1CE7,
	0x1CE8,0x1CED,0x1CF4,0x1CF8,0x1CF9,0x1DC0,0x1DC1,0x1DC2,
	0x1DC3,0x1DC4,0x1DC5,0x1DC6,0x1DC7,0x1DC8,0x1DC9,0x1DCA,
	0x1DCB,0x1DCC,0x1DCD,0x1DCE,0x1DCF,0x1DD0,0x1DD1,0x1DD2,
	0x1DD3,0x1DD4,0x1DD5,0x1DD6,0x1DD7,0x1DD8,0x1DD9,0x1DDA,
	0x1DDB,0x1DDC,0x1DDD,0x1DDE,0x1DDF,0x1DE0,0x1DE1,0x1DE2,
	0x1DE3,0x1DE4,0x1DE5,0x1DE6,0x1DE7,0x1DE8,0x1DE9,0x1DEA,
	0x1DEB,0x1DEC,0x1DED,0x1DEE,0x1DEF,0x1DF0,0x1DF1,0x1DF2,
	0x1DF3,0x1DF4,0x1DF5,0x1DFB,0x1DFC,0x1DFD,0x1DFE,0x1DFF,
	0x20D0,0x20D1,0x20D2,0x20D3,0x20D4,0x20D5,0x20D6,0x20D7,
	0x20D8,0x20D9,0x20DA,0x20DB,0x20DC,0x20E1,0x20E5,0x20E6,
	0x20E7,0x20E8,0x20E9,0x20EA,0x20EB,0x20EC,0x20ED,0x20EE,
	0x20EF,0x20F0,0x2CEF,0x2CF0,0x2CF1,0x2D7F,0x2DE0,0x2DE1,
	0x2DE2,0x2DE3,0x2DE4,0x2DE5,0x2DE6,0x2DE7,0x2DE8,0x2DE9,
	0x2DEA,0x2DEB,0x2DEC,0x2DED,0x2DEE,0x2DEF,0x2DF0,0x2DF1,
	0x2DF2,0x2DF3,0x2DF4,0x2DF5,0x2DF6,0x2DF7,0x2DF8,0x2DF9,
	0x2DFA,0x2DFB,0x2DFC,0x2DFD,0x2DFE,0x2DFF,0x302A,0x302B,
	0x302C,0x302D,0x3099,0x309A,0xA66F,0xA674,0xA675,0xA676,
	0xA677,0xA678,0xA679,0xA67A,0xA67B,0xA67C,0xA67D,0xA69E,
	0xA69F,0xA6F0,0xA6F1,0xA802,0xA806,0xA80B,0xA825,0xA826,
	0xA8C4,0xA8C5,0xA8E0,0xA8E1,0xA8E2,0xA8E3,0xA8E4,0xA8E5,
	0xA8E6,0xA8E7,0xA8E8,0xA8E9,0xA8EA,0xA8EB,0xA8EC,0xA8ED,
	0xA8EE,0xA8EF,0xA8F0,0xA8F1,0xA926,0xA927,0xA928,0xA929,
	0xA92A,0xA92B,0xA92C,0xA92D,0xA947,0xA948,0xA949,0xA94A,
	0xA94B,0xA94C,0xA94D,0xA94E,0xA94F,0xA950,0xA951,0xA980,
	0xA981,0xA982,0xA9B3,0xA9B6,0xA9B7,0xA9B8,0xA9B9,0xA9BC,
	0xA9E5,0xAA29,0xAA2A,0xAA2B,0xAA2C,0xAA2D,0xAA2E,0xAA31,
	0xAA32,0xAA35,0xAA36,0xAA43,0xAA4C,0xAA7C,0xAAB0,0xAAB2,
	0xAAB3,0xAAB4,0xAAB7,0xAAB8,0xAABE,0xAABF,0xAAC1,0xAAEC,
	0xAAED,0xAAF6,0xABE5,0xABE8,0xABED,0xFB1E,0xFE00,0xFE01,
	0xFE02,0xFE03,0xFE04,0xFE05,0xFE06,0xFE07,0xFE08,0xFE09,
	0xFE0A,0xFE0B,0xFE0C,0xFE0D,0xFE0E,0xFE0F,0xFE20,0xFE21,
	0xFE22,0xFE23,0xFE24,0xFE25,0xFE26,0xFE27,0xFE28,0xFE29,
	0xFE2A,0xFE2B,0xFE2C,0xFE2D,0xFE2E,0xFE2F,
	0x101FD,0x102E0,0x10376,0x10377,0x10378,0x10379,0x1037A,0x10A01,
	0x10A02,0x10A03,0x10A05,0x10A06,0x10A0C,0x10A0D,0x10A0E,0x10A0F,
	0x10A38,0x10A39,0x10A3A,0x10A3F,0x10AE5,0x10AE6,0x11001,0x11038,
	0x11039,0x1103A,0x1103B,0x1103C,0x1103D,0x1103E,0x1103F,0x11040,
	0x11041,0x11042,0x11043,0x11044,0x11045,0x11046,0x1107F,0x11080,
	0x11081,0x110B3,0x110B4,0x110B5,0x110B6,0x110B9,0x110BA,0x11100,
	0x11101,0x11102,0x11127,0x11128,0x11129,0x1112A,0x1112B,0x1112D,
	0x1112E,0x1112F,0x11130,0x11131,0x11132,0x11133,0x11134,0x11173,
	0x11180,0x11181,0x111B6,0x111B7,0x111B8,0x111B9,0x111BA,0x111BB,
	0x111BC,0x111BD,0x111BE,0x111CA,0x111CB,0x111CC,0x1122F,0x11230,
	0x11231,0x11234,0x11236,0x11237,0x1123E,0x112DF,0x112E3,0x112E4,
	0x112E5,0x112E6,0x112E7,0x112E8,0x112E9,0x112EA,0x11300,0x11301,
	0x1133C,0x11340,0x11366,0x11367,0x11368,0x11369,0x1136A,0x1136B,
	0x1136C,0x11370,0x11371,0x11372,0x11373,0x11374,0x11438,0x11439,
	0x1143A,0x1143B,0x1143C,0x1143D,0x1143E,0x1143F,0x11442,0x11443,
	0x11444,0x11446,0x114B3,0x114B4,0x114B5,0x114B6,0x114B7,0x114B8,
	0x114BA,0x114BF,0x114C0,0x114C2,0x114C3,0x115B2,0x115B3,0x115B4,
	0x115B5,0x115BC,0x115BD,0x115BF,0x115C0,0x115DC,0x115DD,0x11633,
	0x11634,0x11635,0x11636,0x11637,0x11638,0x11639,0x1163A,0x1163D,
	0x1163F,0x11640,0x116AB,0x116AD,0x116B0,0x116B1,0x116B2,0x116B3,
	0x116B4,0x116B5,0x116B7,0x1171D,0x1171E,0x1171F,0x11722,0x11723,
	0x11724,0x11725,0x11727,0x11728,0x11729,0x1172A,0x1172B,0x11C30,
	0x11C31,0x11C32,0x11C33,0x11C34,0x11C35,0x11C36,0x11C38,0x11C39,
	0x11C3A,0x11C3B,0x11C3C,0x11C3D,0x11C3F,0x11C92,0x11C93,0x11C94,
	0x11C95,0x11C96,0x11C97,0x11C98,0x11C99,0x11C9A,0x11C9B,0x11C9C,
	0x11C9D,0x11C9E,0x11C9F,0x11CA0,0x11CA1,0x11CA2,0x11CA3,0x11CA4,
	0x11CA5,0x11CA6,0x11CA7,0x11CAA,0x11CAB,0x11CAC,0x11CAD,0x11CAE,
	0x11CAF,0x11CB0,0x11CB2,0x11CB3,0x11CB5,0x11CB6,0x16AF0,0x16AF1,
	0x16AF2,0x16AF3,0x16AF4,0x16B30,0x16B31,0x16B32,0x16B33,0x16B34,
	0x16B35,0x16B36,0x16F8F,0x16F90,0x16F91,0x16F92,0x1BC9D,0x1BC9E,
	0x1D167,0x1D168,0x1D169,0x1D17B,0x1D17C,0x1D17D,0x1D17E,0x1D17F,
	0x1D180,0x1D181,0x1D182,0x1D185,0x1D186,0x1D187,0x1D188,0x1D189,
	0x1D18A,0x1D18B,0x1D1AA,0x1D1AB,0x1D1AC,0x1D1AD,0x1D242,0x1D243,
	0x1D244,0x1DA00,0x1DA01,0x1DA02,0x1DA03,0x1DA04,0x1DA05,0x1DA06,
	0x1DA07,0x1DA08,0x1DA09,0x1DA0A,0x1DA0B,0x1DA0C,0x1DA0D,0x1DA0E,
	0x1DA0F,0x1DA10,0x1DA11,0x1DA12,0x1DA13,0x1DA14,0x1DA15,0x1DA16,
	0x1DA17,0x1DA18,0x1DA19,0x1DA1A,0x1DA1B,0x1DA1C,0x1DA1D,0x1DA1E,
	0x1DA1F,0x1DA20,0x1DA21,0x1DA22,0x1DA23,0x1DA24,0x1DA25,0x1DA26,
	0x1DA27,0x1DA28,0x1DA29,0x1DA2A,0x1DA2B,0x1DA2C,0x1DA2D,0x1DA2E,
	0x1DA2F,0x1DA30,0x1DA31,0x1DA32,0x1DA33,0x1DA34,0x1DA35,0x1DA36,
	0x1DA3B,0x1DA3C,0x1DA3D,0x1DA3E,0x1DA3F,0x1DA40,0x1DA41,0x1DA42,
	0x1DA43,0x1DA44,0x1DA45,0x1DA46,0x1DA47,0x1DA48,0x1DA49,0x1DA4A,
	0x1DA4B,0x1DA4C,0x1DA4D,0x1DA4E,0x1DA4F,0x1DA50,0x1DA51,0x1DA52,
	0x1DA53,0x1DA54,0x1DA55,0x1DA56,0x1DA57,0x1DA58,0x1DA59,0x1DA5A,
	0x1DA5B,0x1DA5C,0x1DA5D,0x1DA5E,0x1DA5F,0x1DA60,0x1DA61,0x1DA62,
	0x1DA63,0x1DA64,0x1DA65,0x1DA66,0x1DA67,0x1DA68,0x1DA69,0x1DA6A,
	0x1DA6B,0x1DA6C,0x1DA75,0x1DA84,0x1DA9B,0x1DA9C,0x1DA9D,0x1DA9E,
	0x1DA9F,0x1DAA1,0x1DAA2,0x1DAA3,0x1DAA4,0x1DAA5,0x1DAA6,0x1DAA7,
	0x1DAA8,0x1DAA9,0x1DAAA,0x1DAAB,0x1DAAC,0x1DAAD,0x1DAAE,0x1DAAF,
	0x1E000,0x1E001,0x1E002,0x1E003,0x1E004,0x1E005,0x1E006,0x1E008,
	0x1E009,0x1E00A,0x1E00B,0x1E00C,0x1E00D,0x1E00E,0x1E00F,0x1E010,
	0x1E011,0x1E012,0x1E013,0x1E014,0x1E015,0x1E016,0x1E017,0x1E018,
	0x1E01B,0x1E01C,0x1E01D,0x1E01E,0x1E01F,0x1E020,0x1E021,0x1E023,
	0x1E024,0x1E026,0x1E027,0x1E028,0x1E029,0x1E02A,0x1E8D0,0x1E8D1,
	0x1E8D2,0x1E8D3,0x1E8D4,0x1E8D5,0x1E8D6,0x1E944,0x1E945,0x1E946,
	0x1E947,0x1E948,0x1E949,0x1E94A,0xE0100,0xE0101,0xE0102,0xE0103,
	0xE0104,0xE0105,0xE0106,0xE0107,0xE0108,0xE0109,0xE010A,0xE010B,
	0xE010C,0xE010D,0xE010E,0xE010F,0xE0110,0xE0111,0xE0112,0xE0113,
	0xE0114,0xE0115,0xE0116,0xE0117,0xE0118,0xE0119,0xE011A,0xE011B,
	0xE011C,0xE011D,0xE011E,0xE011F,0xE0120,0xE0121,0xE0122,0xE0123,
	0xE0124,0xE0125,0xE0126,0xE0127,0xE0128,0xE0129,0xE012A,0xE012B,
	0xE012C,0xE012D,0xE012E,0xE012F,0xE0130,0xE0131,0xE0132,0xE0133,
	0xE0134,0xE0135,0xE0136,0xE0137,0xE0138,0xE0139,0xE013A,0xE013B,
	0xE013C,0xE013D,0xE013E,0xE013F,0xE0140,0xE0141,0xE0142,0xE0143,
	0xE0144,0xE0145,0xE0146,0xE0147,0xE0148,0xE0149,0xE014A,0xE014B,
	0xE014C,0xE014D,0xE014E,0xE014F,0xE0150,0xE0151,0xE0152,0xE0153,
	0xE0154,0xE0155,0xE0156,0xE0157,0xE0158,0xE0159,0xE015A,0xE015B,
	0xE015C,0xE015D,0xE015E,0xE015F,0xE0160,0xE0161,0xE0162,0xE0163,
	0xE0164,0xE0165,0xE0166,0xE0167,0xE0168,0xE0169,0xE016A,0xE016B,
	0xE016C,0xE016D,0xE016E,0xE016F,0xE0170,0xE0171,0xE0172,0xE0173,
	0xE0174,0xE0175,0xE0176,0xE0177,0xE0178,0xE0179,0xE017A,0xE017B,
	0xE017C,0xE017D,0xE017E,0xE017F,0xE0180,0xE0181,0xE0182,0xE0183,
	0xE0184,0xE0185,0xE0186,0xE0187,0xE0188,0xE0189,0xE018A,0xE018B,
	0xE018C,0xE018D,0xE018E,0xE018F,0xE0190,0xE0191,0xE0192,0xE0193,
	0xE0194,0xE0195,0xE0196,0xE0197,0xE0198,0xE0199,0xE019A,0xE019B,
	0xE019C,0xE019D,0xE019E,0xE019F,0xE01A0,0xE01A1,0xE01A2,0xE01A3,
	0xE01A4,0xE01A5,0xE01A6,0xE01A7,0xE01A8,0xE01A9,0xE01AA,0xE01AB,
	0xE01AC,0xE01AD,0xE01AE,0xE01AF,0xE01B0,0xE01B1,0xE01B2,0xE01B3,
	0xE01B4,0xE01B5,0xE01B6,0xE01B7,0xE01B8,0xE01B9,0xE01BA,0xE01BB,
	0xE01BC,0xE01BD,0xE01BE,0xE01BF,0xE01C0,0xE01C1,0xE01C2,0xE01C3,
	0xE01C4,0xE01C5,0xE01C6,0xE01C7,0xE01C8,0xE01C9,0xE01CA,0xE01CB,
	0xE01CC,0xE01CD,0xE01CE,0xE01CF,0xE01D0,0xE01D1,0xE01D2,0xE01D3,
	0xE01D4,0xE01D5,0xE01D6,0xE01D7,0xE01D8,0xE01D9,0xE01DA,0xE01DB,
	0xE01DC,0xE01DD,0xE01DE,0xE01DF,0xE01E0,0xE01E1,0xE01E2,0xE01E3,
	0xE01E4,0xE01E5,0xE01E6,0xE01E7,0xE01E8,0xE01E9,0xE01EA,0xE01EB,
	0xE01EC,0xE01ED,0xE01EE,0xE01EF,
	};

	const size_t bc_history_combo_chars_len =
	sizeof(bc_history_combo_chars) / sizeof(bc_history_combo_chars[0]);

	#if BC_DEBUG_CODE
	BcFile bc_history_debug_fp;
	char *bc_history_debug_buf;
	#endif // BC_DEBUG_CODE
	#endif // BC_ENABLE_HISTORY

	const char bc_func_main[] = "(main)";
	const char bc_func_read[] = "(read)";

	#if BC_DEBUG_CODE
	const char* bc_inst_names[] = {

	#if BC_ENABLED
	"BC_INST_INC",
	"BC_INST_DEC",
	#endif // BC_ENABLED

	"BC_INST_NEG",
	"BC_INST_BOOL_NOT",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_TRUNC",
	#endif // BC_ENABLE_EXTRA_MATH

	"BC_INST_POWER",
	"BC_INST_MULTIPLY",
	"BC_INST_DIVIDE",
	"BC_INST_MODULUS",
	"BC_INST_PLUS",
	"BC_INST_MINUS",

	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_PLACES",

	"BC_INST_LSHIFT",
	"BC_INST_RSHIFT",
	#endif // BC_ENABLE_EXTRA_MATH

	"BC_INST_REL_EQ",
	"BC_INST_REL_LE",
	"BC_INST_REL_GE",
	"BC_INST_REL_NE",
	"BC_INST_REL_LT",
	"BC_INST_REL_GT",

	"BC_INST_BOOL_OR",
	"BC_INST_BOOL_AND",

	#if BC_ENABLED
	"BC_INST_ASSIGN_POWER",
	"BC_INST_ASSIGN_MULTIPLY",
	"BC_INST_ASSIGN_DIVIDE",
	"BC_INST_ASSIGN_MODULUS",
	"BC_INST_ASSIGN_PLUS",
	"BC_INST_ASSIGN_MINUS",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_ASSIGN_PLACES",
	"BC_INST_ASSIGN_LSHIFT",
	"BC_INST_ASSIGN_RSHIFT",
	#endif // BC_ENABLE_EXTRA_MATH
	"BC_INST_ASSIGN",

	"BC_INST_ASSIGN_POWER_NO_VAL",
	"BC_INST_ASSIGN_MULTIPLY_NO_VAL",
	"BC_INST_ASSIGN_DIVIDE_NO_VAL",
	"BC_INST_ASSIGN_MODULUS_NO_VAL",
	"BC_INST_ASSIGN_PLUS_NO_VAL",
	"BC_INST_ASSIGN_MINUS_NO_VAL",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_ASSIGN_PLACES_NO_VAL",
	"BC_INST_ASSIGN_LSHIFT_NO_VAL",
	"BC_INST_ASSIGN_RSHIFT_NO_VAL",
	#endif // BC_ENABLE_EXTRA_MATH
	#endif // BC_ENABLED
	"BC_INST_ASSIGN_NO_VAL",

	"BC_INST_NUM",
	"BC_INST_VAR",
	"BC_INST_ARRAY_ELEM",
	#if BC_ENABLED
	"BC_INST_ARRAY",
	#endif // BC_ENABLED

	"BC_INST_ZERO",
	"BC_INST_ONE",

	#if BC_ENABLED
	"BC_INST_LAST",
	#endif // BC_ENABLED
	"BC_INST_IBASE",
	"BC_INST_OBASE",
	"BC_INST_SCALE",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_SEED",
	#endif // BC_ENABLE_EXTRA_MATH
	"BC_INST_LENGTH",
	"BC_INST_SCALE_FUNC",
	"BC_INST_SQRT",
	"BC_INST_ABS",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_IRAND",
	#endif // BC_ENABLE_EXTRA_MATH
	"BC_INST_READ",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_RAND",
	#endif // BC_ENABLE_EXTRA_MATH
	"BC_INST_MAXIBASE",
	"BC_INST_MAXOBASE",
	"BC_INST_MAXSCALE",
	#if BC_ENABLE_EXTRA_MATH
	"BC_INST_MAXRAND",
	#endif // BC_ENABLE_EXTRA_MATH

	"BC_INST_PRINT",
	"BC_INST_PRINT_POP",
	"BC_INST_STR",
	"BC_INST_PRINT_STR",

	#if BC_ENABLED
	"BC_INST_JUMP",
	"BC_INST_JUMP_ZERO",

	"BC_INST_CALL",

	"BC_INST_RET",
	"BC_INST_RET0",
	"BC_INST_RET_VOID",

	"BC_INST_HALT",
	#endif // BC_ENABLED

	#if DC_ENABLED
	"BC_INST_POP",
	"BC_INST_POP_EXEC",
	"BC_INST_MODEXP",
	"BC_INST_DIVMOD",

	"BC_INST_EXECUTE",
	"BC_INST_EXEC_COND",

	"BC_INST_ASCIIFY",
	"BC_INST_PRINT_STREAM",

	"BC_INST_PRINT_STACK",
	"BC_INST_CLEAR_STACK",
	"BC_INST_STACK_LEN",
	"BC_INST_DUPLICATE",
	"BC_INST_SWAP",

	"BC_INST_LOAD",
	"BC_INST_PUSH_VAR",
	"BC_INST_PUSH_TO_VAR",

	"BC_INST_QUIT",
	"BC_INST_NQUIT",
	#endif // DC_ENABLED
	};
	#endif // BC_DEBUG_CODE

	const char bc_parse_zero[2] = "0";
	const char bc_parse_one[2] = "1";

	#if BC_ENABLED
	const BcLexKeyword bc_lex_kws[] = {
	BC_LEX_KW_ENTRY("auto", 4, true),
	BC_LEX_KW_ENTRY("break", 5, true),
	BC_LEX_KW_ENTRY("continue", 8, false),
	BC_LEX_KW_ENTRY("define", 6, true),
	BC_LEX_KW_ENTRY("for", 3, true),
	BC_LEX_KW_ENTRY("if", 2, true),
	BC_LEX_KW_ENTRY("limits", 6, false),
	BC_LEX_KW_ENTRY("return", 6, true),
	BC_LEX_KW_ENTRY("while", 5, true),
	BC_LEX_KW_ENTRY("halt", 4, false),
	BC_LEX_KW_ENTRY("last", 4, false),
	BC_LEX_KW_ENTRY("ibase", 5, true),
	BC_LEX_KW_ENTRY("obase", 5, true),
	BC_LEX_KW_ENTRY("scale", 5, true),
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("seed", 4, false),
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("length", 6, true),
	BC_LEX_KW_ENTRY("print", 5, false),
	BC_LEX_KW_ENTRY("sqrt", 4, true),
	BC_LEX_KW_ENTRY("abs", 3, false),
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("irand", 5, false),
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("quit", 4, true),
	BC_LEX_KW_ENTRY("read", 4, false),
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("rand", 4, false),
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("maxibase", 8, false),
	BC_LEX_KW_ENTRY("maxobase", 8, false),
	BC_LEX_KW_ENTRY("maxscale", 8, false),
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("maxrand", 7, false),
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_ENTRY("else", 4, false),
	};

	const size_t bc_lex_kws_len = sizeof(bc_lex_kws) / sizeof(BcLexKeyword);

	// This is an array that corresponds to token types. An entry is
	// true if the token is valid in an expression, false otherwise.
	const uint8_t bc_parse_exprs[] = {
	BC_PARSE_EXPR_ENTRY(false, false, true, true, true, true, true, true),
	BC_PARSE_EXPR_ENTRY(true, true, true, true, true, true, true, true),
	BC_PARSE_EXPR_ENTRY(true, true, true, true, true, true, true, true),
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_PARSE_EXPR_ENTRY(true, true, true, true, true, true, true, true),
	BC_PARSE_EXPR_ENTRY(true, true, false, false, true, true, false, false),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, true, true, false),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, false, false, false),
	BC_PARSE_EXPR_ENTRY(false, true, true, true, true, true, true, false),
	BC_PARSE_EXPR_ENTRY(true, true, true, false, true, true, true, true),
	BC_PARSE_EXPR_ENTRY(true, true, false, 0, 0, 0, 0, 0)
	#elif BC_ENABLE_EXTRA_MATH // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_PARSE_EXPR_ENTRY(true, true, true, true, true, true, true, true),
	BC_PARSE_EXPR_ENTRY(true, true, false, false, true, true, false, false),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, true, true, false),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, false, false, false),
	BC_PARSE_EXPR_ENTRY(false, true, true, true, true, true, false, true),
	BC_PARSE_EXPR_ENTRY(true, false, true, true, true, true, false, 0),
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_PARSE_EXPR_ENTRY(true, true, true, false, false, true, true, false),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, false, true, true),
	BC_PARSE_EXPR_ENTRY(false, false, false, false, false, false, false, false),
	BC_PARSE_EXPR_ENTRY(false, false, true, true, true, true, true, false),
	BC_PARSE_EXPR_ENTRY(true, true, false, true, true, true, true, false)
	#endif // BC_ENABLE_EXTRA_MATH
	};

	// This is an array of data for operators that correspond to token types.
	const uchar bc_parse_ops[] = {
	BC_PARSE_OP(0, false), BC_PARSE_OP(0, false),
	BC_PARSE_OP(1, false), BC_PARSE_OP(1, false),
	#if BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(2, false),
	#endif // BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(4, false),
	BC_PARSE_OP(5, true), BC_PARSE_OP(5, true), BC_PARSE_OP(5, true),
	BC_PARSE_OP(6, true), BC_PARSE_OP(6, true),
	#if BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(3, false),
	BC_PARSE_OP(7, true), BC_PARSE_OP(7, true),
	#endif // BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(9, true), BC_PARSE_OP(9, true), BC_PARSE_OP(9, true),
	BC_PARSE_OP(9, true), BC_PARSE_OP(9, true), BC_PARSE_OP(9, true),
	BC_PARSE_OP(11, true), BC_PARSE_OP(10, true),
	BC_PARSE_OP(8, false), BC_PARSE_OP(8, false), BC_PARSE_OP(8, false),
	BC_PARSE_OP(8, false), BC_PARSE_OP(8, false), BC_PARSE_OP(8, false),
	#if BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(8, false), BC_PARSE_OP(8, false), BC_PARSE_OP(8, false),
	#endif // BC_ENABLE_EXTRA_MATH
	BC_PARSE_OP(8, false),
	};

	// These identify what tokens can come after expressions in certain cases.
	const BcParseNext bc_parse_next_expr =
	BC_PARSE_NEXT(4, BC_LEX_NLINE, BC_LEX_SCOLON, BC_LEX_RBRACE, BC_LEX_EOF);
	const BcParseNext bc_parse_next_param =
	BC_PARSE_NEXT(2, BC_LEX_RPAREN, BC_LEX_COMMA);
	const BcParseNext bc_parse_next_print =
	BC_PARSE_NEXT(4, BC_LEX_COMMA, BC_LEX_NLINE, BC_LEX_SCOLON, BC_LEX_EOF);
	const BcParseNext bc_parse_next_rel = BC_PARSE_NEXT(1, BC_LEX_RPAREN);
	const BcParseNext bc_parse_next_elem = BC_PARSE_NEXT(1, BC_LEX_RBRACKET);
	const BcParseNext bc_parse_next_for = BC_PARSE_NEXT(1, BC_LEX_SCOLON);
	const BcParseNext bc_parse_next_read =
	BC_PARSE_NEXT(2, BC_LEX_NLINE, BC_LEX_EOF);
	#endif // BC_ENABLED

	#if DC_ENABLED
	const uint8_t dc_lex_regs[] = {
	BC_LEX_OP_REL_EQ, BC_LEX_OP_REL_LE, BC_LEX_OP_REL_GE, BC_LEX_OP_REL_NE,
	BC_LEX_OP_REL_LT, BC_LEX_OP_REL_GT, BC_LEX_SCOLON, BC_LEX_COLON,
	BC_LEX_KW_ELSE, BC_LEX_LOAD, BC_LEX_LOAD_POP, BC_LEX_OP_ASSIGN,
	BC_LEX_STORE_PUSH,
	};

	const size_t dc_lex_regs_len = sizeof(dc_lex_regs) / sizeof(uint8_t);

	const uchar dc_lex_tokens[] = {
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_IRAND,
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#if BC_ENABLE_EXTRA_MATH
	BC_LEX_OP_TRUNC,
	#else // BC_ENABLE_EXTRA_MATH
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_LEX_OP_MODULUS, BC_LEX_INVALID,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_RAND,
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_LPAREN, BC_LEX_RPAREN, BC_LEX_OP_MULTIPLY, BC_LEX_OP_PLUS,
	BC_LEX_INVALID, BC_LEX_OP_MINUS, BC_LEX_INVALID, BC_LEX_OP_DIVIDE,
	BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID,
	BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID,
	BC_LEX_INVALID, BC_LEX_INVALID,
	BC_LEX_COLON, BC_LEX_SCOLON, BC_LEX_OP_REL_GT, BC_LEX_OP_REL_EQ,
	BC_LEX_OP_REL_LT, BC_LEX_KW_READ,
	#if BC_ENABLE_EXTRA_MATH
	BC_LEX_OP_PLACES,
	#else // BC_ENABLE_EXTRA_MATH
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_INVALID,
	BC_LEX_INVALID, BC_LEX_INVALID, BC_LEX_EQ_NO_REG,
	#if BC_ENABLE_EXTRA_MATH
	BC_LEX_OP_LSHIFT,
	#else // BC_ENABLE_EXTRA_MATH
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_LEX_KW_IBASE,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_SEED,
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_SCALE, BC_LEX_LOAD_POP, BC_LEX_OP_BOOL_AND, BC_LEX_OP_BOOL_NOT,
	BC_LEX_KW_OBASE, BC_LEX_PRINT_STREAM, BC_LEX_NQUIT, BC_LEX_POP,
	BC_LEX_STORE_PUSH, BC_LEX_KW_MAXIBASE, BC_LEX_KW_MAXOBASE,
	BC_LEX_KW_MAXSCALE,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_KW_MAXRAND,
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_SCALE_FACTOR,
	BC_LEX_INVALID, BC_LEX_KW_LENGTH, BC_LEX_INVALID, BC_LEX_INVALID,
	BC_LEX_INVALID, BC_LEX_OP_POWER, BC_LEX_NEG, BC_LEX_INVALID,
	BC_LEX_ASCIIFY, BC_LEX_KW_ABS, BC_LEX_CLEAR_STACK, BC_LEX_DUPLICATE,
	BC_LEX_KW_ELSE, BC_LEX_PRINT_STACK, BC_LEX_INVALID,
	#if BC_ENABLE_EXTRA_MATH
	BC_LEX_OP_RSHIFT,
	#else // BC_ENABLE_EXTRA_MATH
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_LEX_STORE_IBASE,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_STORE_SEED,
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_LEX_STORE_SCALE, BC_LEX_LOAD,
	BC_LEX_OP_BOOL_OR, BC_LEX_PRINT_POP, BC_LEX_STORE_OBASE, BC_LEX_KW_PRINT,
	BC_LEX_KW_QUIT, BC_LEX_SWAP, BC_LEX_OP_ASSIGN, BC_LEX_INVALID,
	BC_LEX_INVALID, BC_LEX_KW_SQRT, BC_LEX_INVALID, BC_LEX_EXECUTE,
	BC_LEX_INVALID, BC_LEX_STACK_LEVEL,
	BC_LEX_LBRACE, BC_LEX_OP_MODEXP, BC_LEX_RBRACE, BC_LEX_OP_DIVMOD,
	BC_LEX_INVALID
	};

	const uchar dc_parse_insts[] = {
	BC_INST_INVALID, BC_INST_INVALID,
	#if BC_ENABLED
	BC_INST_INVALID, BC_INST_INVALID,
	#endif // BC_ENABLED
	BC_INST_INVALID, BC_INST_BOOL_NOT,
	#if BC_ENABLE_EXTRA_MATH
	BC_INST_TRUNC,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_INST_POWER, BC_INST_MULTIPLY, BC_INST_DIVIDE, BC_INST_MODULUS,
	BC_INST_PLUS, BC_INST_MINUS,
	#if BC_ENABLE_EXTRA_MATH
	BC_INST_PLACES,
	BC_INST_LSHIFT, BC_INST_RSHIFT,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_BOOL_OR, BC_INST_BOOL_AND,
	#if BC_ENABLED
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_INVALID, BC_INST_INVALID,
	#if BC_ENABLE_EXTRA_MATH
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	#endif // BC_ENABLED
	BC_INST_INVALID,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_REL_GT, BC_INST_REL_LT,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID, BC_INST_REL_GE,
	BC_INST_INVALID, BC_INST_REL_LE,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	#if BC_ENABLED
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	#endif // BC_ENABLED
	BC_INST_IBASE, BC_INST_OBASE, BC_INST_SCALE,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_SEED,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_LENGTH, BC_INST_PRINT,
	BC_INST_SQRT, BC_INST_ABS,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_IRAND,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_QUIT, BC_INST_INVALID,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_RAND,
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_MAXIBASE,
	BC_INST_MAXOBASE, BC_INST_MAXSCALE,
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	BC_INST_MAXRAND,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_INST_INVALID,
	BC_INST_REL_EQ, BC_INST_MODEXP, BC_INST_DIVMOD, BC_INST_INVALID,
	BC_INST_EXECUTE, BC_INST_PRINT_STACK, BC_INST_CLEAR_STACK,
	BC_INST_STACK_LEN, BC_INST_DUPLICATE, BC_INST_SWAP, BC_INST_POP,
	BC_INST_ASCIIFY, BC_INST_PRINT_STREAM,
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	#if BC_ENABLE_EXTRA_MATH
	BC_INST_INVALID,
	#endif // BC_ENABLE_EXTRA_MATH
	BC_INST_INVALID, BC_INST_INVALID, BC_INST_INVALID,
	BC_INST_PRINT_POP, BC_INST_NQUIT, BC_INST_SCALE_FUNC,
	};
	#endif // DC_ENABLED

	#endif // !BC_ENABLE_LIBRARY

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	const BcRandState bc_rand_multiplier = BC_RAND_MULTIPLIER;

	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	#if BC_LONG_BIT >= 64
	const BcDig bc_num_bigdigMax[] = {
	709551616U,
	446744073U,
	18U,
	};
	const BcDig bc_num_bigdigMax2[] = {
	768211456U,
	374607431U,
	938463463U,
	282366920U,
	340U,
	};
	#else // BC_LONG_BIT >= 64
	const BcDig bc_num_bigdigMax[] = {
	7296U,
	9496U,
	42U,
	};
	const BcDig bc_num_bigdigMax2[] = {
	1616U,
	955U,
	737U,
	6744U,
	1844U,
	};
	#endif // BC_LONG_BIT >= 64

	const size_t bc_num_bigdigMax_size = sizeof(bc_num_bigdigMax) / sizeof(BcDig);
	const size_t bc_num_bigdigMax2_size = sizeof(bc_num_bigdigMax2) / sizeof(BcDig);

	const char bc_num_hex_digits[] = "0123456789ABCDEF";

	const BcBigDig bc_num_pow10[BC_BASE_DIGS + 1] = {
	1,
	10,
	100,
	1000,
	10000,
	#if BC_BASE_DIGS > 4
	100000,
	1000000,
	10000000,
	100000000,
	1000000000,
	#endif // BC_BASE_DIGS > 4
	};

	#if !BC_ENABLE_LIBRARY

	const BcNumBinaryOp bc_program_ops[] = {
	bc_num_pow, bc_num_mul, bc_num_div, bc_num_mod, bc_num_add, bc_num_sub,
	#if BC_ENABLE_EXTRA_MATH
	bc_num_places, bc_num_lshift, bc_num_rshift,
	#endif // BC_ENABLE_EXTRA_MATH
	};

	const BcNumBinaryOpReq bc_program_opReqs[] = {
	bc_num_powReq, bc_num_mulReq, bc_num_divReq, bc_num_divReq,
	bc_num_addReq, bc_num_addReq,
	#if BC_ENABLE_EXTRA_MATH
	bc_num_placesReq, bc_num_placesReq, bc_num_placesReq,
	#endif // BC_ENABLE_EXTRA_MATH
	};

	const BcProgramUnary bc_program_unarys[] = {
	bc_program_negate, bc_program_not,
	#if BC_ENABLE_EXTRA_MATH
	bc_program_trunc,
	#endif // BC_ENABLE_EXTRA_MATH
	};

	const char bc_program_exprs_name[] = "<exprs>";

	const char bc_program_stdin_name[] = "<stdin>";
	const char bc_program_ready_msg[] = "ready for more input\n";
	const size_t bc_program_ready_msg_len = sizeof(bc_program_ready_msg) - 1;
	const char bc_program_esc_chars[] = "ab\\efnqrt";
	const char bc_program_esc_seqs[] = "\a\b\\\\\f\n\"\r\t";

	#endif // !BC_ENABLE_LIBRARY
	diff --git a/contrib/bc/src/file.c b/contrib/bc/src/file.c
	index e69092f6207a..fb904423f1b6 100644
	--- a/contrib/bc/src/file.c
	+++ b/contrib/bc/src/file.c
	@@ -1,225 +1,250 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code for implementing buffered I/O on my own terms.
	*
	*/

	#include <assert.h>
	#include <errno.h>
	#include <string.h>
	+
	+#ifndef _WIN32
	#include <unistd.h>
	+#endif // _WIN32

	#include <file.h>
	#include <vm.h>

	static void bc_file_ultoa(unsigned long long val, char buf[BC_FILE_ULL_LENGTH])
	{
	char buf2[BC_FILE_ULL_LENGTH];
	size_t i, len;

	memset(buf2, 0, BC_FILE_ULL_LENGTH);

	// The i = 1 is to ensure that there is a null byte at the end.
	for (i = 1; val; ++i) {
	unsigned long long mod = val % 10;
	buf2[i] = ((char) mod) + '0';
	val /= 10;
	}

	len = i;

	for (i = 0; i < len; ++i) buf[i] = buf2[len - i - 1];
	}

	static BcStatus bc_file_output(int fd, const char *buf, size_t n) {

	size_t bytes = 0;
	sig_atomic_t lock;

	BC_SIG_TRYLOCK(lock);

	while (bytes < n) {

	ssize_t written = write(fd, buf + bytes, n - bytes);

	if (BC_ERR(written == -1))
	return errno == EPIPE ? BC_STATUS_EOF : BC_STATUS_ERROR_FATAL;

	bytes += (size_t) written;
	}

	BC_SIG_TRYUNLOCK(lock);

	return BC_STATUS_SUCCESS;
	}

	-BcStatus bc_file_flushErr(BcFile *restrict f) {
	-
	+BcStatus bc_file_flushErr(BcFile *restrict f, BcFlushType type)
	+{
	BcStatus s;

	if (f->len) {
	+
	+#if BC_ENABLE_HISTORY
	+ if (BC_TTY) {
	+ if (f->buf[f->len - 1] != '\n' &&
	+ (type == BC_FLUSH_SAVE_EXTRAS_CLEAR \|\|
	+ type == BC_FLUSH_SAVE_EXTRAS_NO_CLEAR))
	+ {
	+ size_t i;
	+
	+ for (i = f->len - 2; i < f->len && f->buf[i] != '\n'; --i);
	+
	+ i += 1;
	+
	+ bc_vec_string(&vm.history.extras, f->len - i, f->buf + i);
	+ }
	+ else if (type >= BC_FLUSH_NO_EXTRAS_CLEAR) {
	+ bc_vec_popAll(&vm.history.extras);
	+ }
	+ }
	+#endif // BC_ENABLE_HISTORY
	+
	s = bc_file_output(f->fd, f->buf, f->len);
	f->len = 0;
	}
	else s = BC_STATUS_SUCCESS;

	return s;
	}

	-void bc_file_flush(BcFile *restrict f) {
	+void bc_file_flush(BcFile *restrict f, BcFlushType type) {

	- BcStatus s = bc_file_flushErr(f);
	+ BcStatus s = bc_file_flushErr(f, type);

	if (BC_ERR(s)) {

	if (s == BC_STATUS_EOF) {
	vm.status = (sig_atomic_t) s;
	BC_VM_JMP;
	}
	else bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);
	}
	}

	-void bc_file_write(BcFile restrict f, const char buf, size_t n) {
	-
	+void bc_file_write(BcFile *restrict f, BcFlushType type,
	+ const char *buf, size_t n)
	+{
	if (n > f->cap - f->len) {
	- bc_file_flush(f);
	+ bc_file_flush(f, type);
	assert(!f->len);
	}

	if (BC_UNLIKELY(n > f->cap - f->len)) bc_file_output(f->fd, buf, n);
	else {
	memcpy(f->buf + f->len, buf, n);
	f->len += n;
	}
	}

	-void bc_file_printf(BcFile restrict f, const char fmt, ...) {
	-
	+void bc_file_printf(BcFile restrict f, const char fmt, ...)
	+{
	va_list args;

	va_start(args, fmt);
	bc_file_vprintf(f, fmt, args);
	va_end(args);
	}

	void bc_file_vprintf(BcFile restrict f, const char fmt, va_list args) {

	char *percent;
	const char *ptr = fmt;
	char buf[BC_FILE_ULL_LENGTH];

	while ((percent = strchr(ptr, '%')) != NULL) {

	char c;

	if (percent != ptr) {
	size_t len = (size_t) (percent - ptr);
	- bc_file_write(f, ptr, len);
	+ bc_file_write(f, bc_flush_none, ptr, len);
	}

	c = percent[1];

	if (c == 'c') {

	uchar uc = (uchar) va_arg(args, int);

	- bc_file_putchar(f, uc);
	+ bc_file_putchar(f, bc_flush_none, uc);
	}
	else if (c == 's') {

	char s = va_arg(args, char);

	- bc_file_puts(f, s);
	+ bc_file_puts(f, bc_flush_none, s);
	}
	#if BC_DEBUG_CODE
	else if (c == 'd') {

	int d = va_arg(args, int);

	if (d < 0) {
	- bc_file_putchar(f, '-');
	+ bc_file_putchar(f, bc_flush_none, '-');
	d = -d;
	}

	- if (!d) bc_file_putchar(f, '0');
	+ if (!d) bc_file_putchar(f, bc_flush_none, '0');
	else {
	bc_file_ultoa((unsigned long long) d, buf);
	- bc_file_puts(f, buf);
	+ bc_file_puts(f, bc_flush_none, buf);
	}
	}
	#endif // BC_DEBUG_CODE
	else {

	unsigned long long ull;

	assert((c == 'l' \|\| c == 'z') && percent[2] == 'u');

	if (c == 'z') ull = (unsigned long long) va_arg(args, size_t);
	else ull = (unsigned long long) va_arg(args, unsigned long);

	- if (!ull) bc_file_putchar(f, '0');
	+ if (!ull) bc_file_putchar(f, bc_flush_none, '0');
	else {
	bc_file_ultoa(ull, buf);
	- bc_file_puts(f, buf);
	+ bc_file_puts(f, bc_flush_none, buf);
	}
	}

	ptr = percent + 2 + (c == 'l' \|\| c == 'z');
	}

	- if (ptr[0]) bc_file_puts(f, ptr);
	+ if (ptr[0]) bc_file_puts(f, bc_flush_none, ptr);
	}

	-void bc_file_puts(BcFile restrict f, const char str) {
	- bc_file_write(f, str, strlen(str));
	+void bc_file_puts(BcFile restrict f, BcFlushType type, const char str) {
	+ bc_file_write(f, type, str, strlen(str));
	}

	-void bc_file_putchar(BcFile *restrict f, uchar c) {
	- if (f->len == f->cap) bc_file_flush(f);
	+void bc_file_putchar(BcFile *restrict f, BcFlushType type, uchar c) {
	+ if (f->len == f->cap) bc_file_flush(f, type);
	assert(f->len < f->cap);
	f->buf[f->len] = (char) c;
	f->len += 1;
	}

	void bc_file_init(BcFile f, int fd, char buf, size_t cap) {
	BC_SIG_ASSERT_LOCKED;
	f->fd = fd;
	f->buf = buf;
	f->len = 0;
	f->cap = cap;
	}

	void bc_file_free(BcFile *f) {
	BC_SIG_ASSERT_LOCKED;
	- bc_file_flush(f);
	+ bc_file_flush(f, bc_flush_none);
	}
	diff --git a/contrib/bc/src/history.c b/contrib/bc/src/history.c
	index 7c4f0ceb0f39..c0d54fe35234 100644
	--- a/contrib/bc/src/history.c
	+++ b/contrib/bc/src/history.c
	@@ -1,1450 +1,1465 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Adapted from the following:
	*
	* linenoise.c -- guerrilla line editing library against the idea that a
	* line editing lib needs to be 20,000 lines of C code.
	*
	* You can find the original source code at:
	* http://github.com/antirez/linenoise
	*
	* You can find the fork that this code is based on at:
	* https://github.com/rain-1/linenoise-mob
	*
	* ------------------------------------------------------------------------
	*
	* This code is also under the following license:
	*
	* Copyright (c) 2010-2016, Salvatore Sanfilippo <antirez at gmail dot com>
	* Copyright (c) 2010-2013, Pieter Noordhuis <pcnoordhuis at gmail dot com>
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are
	* met:
	*
	* * Redistributions of source code must retain the above copyright
	* notice, this list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT
	* HOLDER 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.
	*
	* ------------------------------------------------------------------------
	*
	* Does a number of crazy assumptions that happen to be true in 99.9999% of
	* the 2010 UNIX computers around.
	*
	* References:
	* - http://invisible-island.net/xterm/ctlseqs/ctlseqs.html
	* - http://www.3waylabs.com/nw/WWW/products/wizcon/vt220.html
	*
	* Todo list:
	* - Filter bogus Ctrl+<char> combinations.
	* - Win32 support
	*
	* Bloat:
	* - History search like Ctrl+r in readline?
	*
	* List of escape sequences used by this program, we do everything just
	* with three sequences. In order to be so cheap we may have some
	* flickering effect with some slow terminal, but the lesser sequences
	* the more compatible.
	*
	* EL (Erase Line)
	* Sequence: ESC [ n K
	* Effect: if n is 0 or missing, clear from cursor to end of line
	* Effect: if n is 1, clear from beginning of line to cursor
	* Effect: if n is 2, clear entire line
	*
	* CUF (CUrsor Forward)
	* Sequence: ESC [ n C
	* Effect: moves cursor forward n chars
	*
	* CUB (CUrsor Backward)
	* Sequence: ESC [ n D
	* Effect: moves cursor backward n chars
	*
	* The following is used to get the terminal width if getting
	* the width with the TIOCGWINSZ ioctl fails
	*
	* DSR (Device Status Report)
	* Sequence: ESC [ 6 n
	* Effect: reports the current cusor position as ESC [ n ; m R
	* where n is the row and m is the column
	*
	* When multi line mode is enabled, we also use two additional escape
	* sequences. However multi line editing is disabled by default.
	*
	* CUU (CUrsor Up)
	* Sequence: ESC [ n A
	* Effect: moves cursor up of n chars.
	*
	* CUD (CUrsor Down)
	* Sequence: ESC [ n B
	* Effect: moves cursor down of n chars.
	*
	* When bc_history_clearScreen() is called, two additional escape sequences
	* are used in order to clear the screen and position the cursor at home
	* position.
	*
	* CUP (CUrsor Position)
	* Sequence: ESC [ H
	* Effect: moves the cursor to upper left corner
	*
	* ED (Erase Display)
	* Sequence: ESC [ 2 J
	* Effect: clear the whole screen
	*
	* *****************************************************************************
	*
	* Code for line history.
	*
	*/

	#if BC_ENABLE_HISTORY

	#include <assert.h>
	#include <stdlib.h>
	#include <errno.h>
	#include <string.h>
	#include <strings.h>
	#include <ctype.h>

	#include <signal.h>

	#include <termios.h>
	#include <unistd.h>
	#include <sys/stat.h>
	#include <sys/types.h>
	#include <sys/ioctl.h>
	#include <sys/select.h>

	#include <vector.h>
	#include <history.h>
	#include <read.h>
	#include <file.h>
	#include <vm.h>

	static void bc_history_add(BcHistory h, char line);
	static void bc_history_add_empty(BcHistory *h);

	/**
	* Check if the code is a wide character.
	*/
	static bool bc_history_wchar(uint32_t cp) {

	size_t i;

	for (i = 0; i < bc_history_wchars_len; ++i) {

	// Ranges are listed in ascending order. Therefore, once the
	// whole range is higher than the codepoint we're testing, the
	// codepoint won't be found in any remaining range => bail early.
	if (bc_history_wchars[i][0] > cp) return false;

	// Test this range.
	if (bc_history_wchars[i][0] <= cp && cp <= bc_history_wchars[i][1])
	return true;
	}

	return false;
	}

	/**
	* Check if the code is a combining character.
	*/
	static bool bc_history_comboChar(uint32_t cp) {

	size_t i;

	for (i = 0; i < bc_history_combo_chars_len; ++i) {

	// Combining chars are listed in ascending order, so once we pass
	// the codepoint of interest, we know it's not a combining char.
	if (bc_history_combo_chars[i] > cp) return false;
	if (bc_history_combo_chars[i] == cp) return true;
	}

	return false;
	}

	/**
	* Get length of previous UTF8 character.
	*/
	static size_t bc_history_prevCharLen(const char *buf, size_t pos) {
	size_t end = pos;
	for (pos -= 1; pos < end && (buf[pos] & 0xC0) == 0x80; --pos);
	return end - (pos >= end ? 0 : pos);
	}

	/**
	* Convert UTF-8 to Unicode code point.
	*/
	static size_t bc_history_codePoint(const char s, size_t len, uint32_t cp) {

	if (len) {

	uchar byte = (uchar) s[0];

	if ((byte & 0x80) == 0) {
	*cp = byte;
	return 1;
	}
	else if ((byte & 0xE0) == 0xC0) {

	if (len >= 2) {
	*cp = (((uint32_t) (s[0] & 0x1F)) << 6) \|
	((uint32_t) (s[1] & 0x3F));
	return 2;
	}
	}
	else if ((byte & 0xF0) == 0xE0) {

	if (len >= 3) {
	*cp = (((uint32_t) (s[0] & 0x0F)) << 12) \|
	(((uint32_t) (s[1] & 0x3F)) << 6) \|
	((uint32_t) (s[2] & 0x3F));
	return 3;
	}
	}
	else if ((byte & 0xF8) == 0xF0) {

	if (len >= 4) {
	*cp = (((uint32_t) (s[0] & 0x07)) << 18) \|
	(((uint32_t) (s[1] & 0x3F)) << 12) \|
	(((uint32_t) (s[2] & 0x3F)) << 6) \|
	((uint32_t) (s[3] & 0x3F));
	return 4;
	}
	}
	else {
	*cp = 0xFFFD;
	return 1;
	}
	}

	*cp = 0;

	return 1;
	}

	/**
	* Get length of next grapheme.
	*/
	static size_t bc_history_nextLen(const char *buf, size_t buf_len,
	size_t pos, size_t *col_len)
	{
	uint32_t cp;
	size_t beg = pos;
	size_t len = bc_history_codePoint(buf + pos, buf_len - pos, &cp);

	if (bc_history_comboChar(cp)) {
	// Currently unreachable?
	return 0;
	}

	if (col_len != NULL) *col_len = bc_history_wchar(cp) ? 2 : 1;

	pos += len;

	while (pos < buf_len) {

	len = bc_history_codePoint(buf + pos, buf_len - pos, &cp);

	if (!bc_history_comboChar(cp)) return pos - beg;

	pos += len;
	}

	return pos - beg;
	}

	/**
	* Get length of previous grapheme.
	*/
	static size_t bc_history_prevLen(const char buf, size_t pos, size_t col_len) {

	size_t end = pos;

	while (pos > 0) {

	uint32_t cp;
	size_t len = bc_history_prevCharLen(buf, pos);

	pos -= len;
	bc_history_codePoint(buf + pos, len, &cp);

	if (!bc_history_comboChar(cp)) {
	if (col_len != NULL) *col_len = 1 + (bc_history_wchar(cp) != 0);
	return end - pos;
	}
	}

	// Currently unreachable?
	return 0;
	}

	static ssize_t bc_history_read(char *buf, size_t n) {

	ssize_t ret;

	BC_SIG_LOCK;

	do {
	ret = read(STDIN_FILENO, buf, n);
	} while (ret == EINTR);

	BC_SIG_UNLOCK;

	return ret;
	}

	/**
	* Read a Unicode code point from a file.
	*/
	static BcStatus bc_history_readCode(char *buf, size_t buf_len,
	uint32_t cp, size_t nread)
	{
	ssize_t n;

	assert(buf_len >= 1);

	n = bc_history_read(buf, 1);
	if (BC_ERR(n <= 0)) goto err;

	uchar byte = (uchar) buf[0];

	if ((byte & 0x80) != 0) {

	if ((byte & 0xE0) == 0xC0) {
	assert(buf_len >= 2);
	n = bc_history_read(buf + 1, 1);
	if (BC_ERR(n <= 0)) goto err;
	}
	else if ((byte & 0xF0) == 0xE0) {
	assert(buf_len >= 3);
	n = bc_history_read(buf + 1, 2);
	if (BC_ERR(n <= 0)) goto err;
	}
	else if ((byte & 0xF8) == 0xF0) {
	assert(buf_len >= 3);
	n = bc_history_read(buf + 1, 3);
	if (BC_ERR(n <= 0)) goto err;
	}
	else {
	n = -1;
	goto err;
	}
	}

	*nread = bc_history_codePoint(buf, buf_len, cp);

	return BC_STATUS_SUCCESS;

	err:
	if (BC_ERR(n < 0)) bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);
	else *nread = (size_t) n;
	return BC_STATUS_EOF;
	}

	/**
	* Get column length from begining of buffer to current byte position.
	*/
	static size_t bc_history_colPos(const char *buf, size_t buf_len, size_t pos) {

	size_t ret = 0, off = 0;

	while (off < pos) {

	size_t col_len, len;

	len = bc_history_nextLen(buf, buf_len, off, &col_len);

	off += len;
	ret += col_len;
	}

	return ret;
	}

	/**
	* Return true if the terminal name is in the list of terminals we know are
	* not able to understand basic escape sequences.
	*/
	static inline bool bc_history_isBadTerm(void) {

	size_t i;
	char *term = getenv("TERM");

	if (term == NULL) return false;

	for (i = 0; bc_history_bad_terms[i]; ++i) {
	if (!strcasecmp(term, bc_history_bad_terms[i])) return true;
	}

	return false;
	}

	/**
	* Raw mode: 1960's black magic.
	*/
	static void bc_history_enableRaw(BcHistory *h) {

	struct termios raw;
	int err;

	assert(BC_TTYIN);

	if (h->rawMode) return;

	BC_SIG_LOCK;

	if (BC_ERR(tcgetattr(STDIN_FILENO, &h->orig_termios) == -1))
	bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	BC_SIG_UNLOCK;

	// Modify the original mode.
	raw = h->orig_termios;

	// Input modes: no break, no CR to NL, no parity check, no strip char,
	// no start/stop output control.
	raw.c_iflag &= (unsigned int) (~(BRKINT \| ICRNL \| INPCK \| ISTRIP \| IXON));

	// Control modes - set 8 bit chars.
	raw.c_cflag \|= (CS8);

	// Local modes - choing off, canonical off, no extended functions,
	// no signal chars (^Z,^C).
	raw.c_lflag &= (unsigned int) (~(ECHO \| ICANON \| IEXTEN \| ISIG));

	// Control chars - set return condition: min number of bytes and timer.
	// We want read to give every single byte, w/o timeout (1 byte, no timer).
	raw.c_cc[VMIN] = 1;
	raw.c_cc[VTIME] = 0;

	BC_SIG_LOCK;

	// Put terminal in raw mode after flushing.
	do {
	err = tcsetattr(STDIN_FILENO, TCSAFLUSH, &raw);
	} while (BC_ERR(err < 0) && errno == EINTR);

	BC_SIG_UNLOCK;

	if (BC_ERR(err < 0)) bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	h->rawMode = true;
	}

	static void bc_history_disableRaw(BcHistory *h) {

	sig_atomic_t lock;

	// Don't even check the return value as it's too late.
	if (!h->rawMode) return;

	BC_SIG_TRYLOCK(lock);

	if (BC_ERR(tcsetattr(STDIN_FILENO, TCSAFLUSH, &h->orig_termios) != -1))
	h->rawMode = false;

	BC_SIG_TRYUNLOCK(lock);
	}

	/**
	* Use the ESC [6n escape sequence to query the horizontal cursor position
	* and return it. On error -1 is returned, on success the position of the
	* cursor.
	*/
	static size_t bc_history_cursorPos(void) {

	char buf[BC_HIST_SEQ_SIZE];
	char ptr, ptr2;
	size_t cols, rows, i;

	// Report cursor location.
	- bc_file_write(&vm.fout, "\x1b[6n", 4);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, "\x1b[6n", 4);
	+ bc_file_flush(&vm.fout, bc_flush_none);

	// Read the response: ESC [ rows ; cols R.
	for (i = 0; i < sizeof(buf) - 1; ++i) {
	if (bc_history_read(buf + i, 1) != 1 \|\| buf[i] == 'R') break;
	}

	buf[i] = '\0';

	if (BC_ERR(buf[0] != BC_ACTION_ESC \|\| buf[1] != '[')) return SIZE_MAX;

	// Parse it.
	ptr = buf + 2;
	rows = strtoul(ptr, &ptr2, 10);

	if (BC_ERR(!rows \|\| ptr2[0] != ';')) return SIZE_MAX;

	ptr = ptr2 + 1;
	cols = strtoul(ptr, NULL, 10);

	if (BC_ERR(!cols)) return SIZE_MAX;

	return cols <= UINT16_MAX ? cols : 0;
	}

	/**
	* Try to get the number of columns in the current terminal, or assume 80
	* if it fails.
	*/
	static size_t bc_history_columns(void) {

	struct winsize ws;
	int ret;

	BC_SIG_LOCK;

	ret = ioctl(vm.fout.fd, TIOCGWINSZ, &ws);

	BC_SIG_UNLOCK;

	if (BC_ERR(ret == -1 \|\| !ws.ws_col)) {

	// Calling ioctl() failed. Try to query the terminal itself.
	size_t start, cols;

	// Get the initial position so we can restore it later.
	start = bc_history_cursorPos();
	if (BC_ERR(start == SIZE_MAX)) return BC_HIST_DEF_COLS;

	// Go to right margin and get position.
	- bc_file_write(&vm.fout, "\x1b[999C", 6);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, "\x1b[999C", 6);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	cols = bc_history_cursorPos();
	if (BC_ERR(cols == SIZE_MAX)) return BC_HIST_DEF_COLS;

	// Restore position.
	if (cols > start) {
	bc_file_printf(&vm.fout, "\x1b[%zuD", cols - start);
	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}

	return cols;
	}

	return ws.ws_col;
	}

	#if BC_ENABLE_PROMPT
	/**
	* Check if text is an ANSI escape sequence.
	*/
	static bool bc_history_ansiEscape(const char buf, size_t buf_len, size_t len)
	{
	if (buf_len > 2 && !memcmp("\033[", buf, 2)) {

	size_t off = 2;

	while (off < buf_len) {

	char c = buf[off++];

	if ((c >= 'A' && c <= 'K' && c != 'I') \|\|
	c == 'S' \|\| c == 'T' \|\| c == 'f' \|\| c == 'm')
	{
	*len = off;
	return true;
	}
	}
	}

	return false;
	}

	/**
	* Get column length of prompt text.
	*/
	static size_t bc_history_promptColLen(const char *prompt, size_t plen) {

	char buf[BC_HIST_MAX_LINE + 1];
	size_t buf_len = 0, off = 0;

	while (off < plen) {

	size_t len;

	if (bc_history_ansiEscape(prompt + off, plen - off, &len)) {
	off += len;
	continue;
	}

	buf[buf_len++] = prompt[off++];
	}

	return bc_history_colPos(buf, buf_len, buf_len);
	}
	#endif // BC_ENABLE_PROMPT

	/**
	* Rewrites the currently edited line accordingly to the buffer content,
	* cursor position, and number of columns of the terminal.
	*/
	static void bc_history_refresh(BcHistory *h) {

	char* buf = h->buf.v;
	size_t colpos, len = BC_HIST_BUF_LEN(h), pos = h->pos;

	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_none);

	while(h->pcol + bc_history_colPos(buf, len, pos) >= h->cols) {

	size_t chlen = bc_history_nextLen(buf, len, 0, NULL);

	buf += chlen;
	len -= chlen;
	pos -= chlen;
	}

	while (h->pcol + bc_history_colPos(buf, len, len) > h->cols)
	len -= bc_history_prevLen(buf, len, NULL);

	// Cursor to left edge.
	- bc_file_write(&vm.fout, "\r", 1);
	+ bc_file_write(&vm.fout, bc_flush_none, "\r", 1);
	+
	+ // Take the extra stuff into account.
	+ if (h->extras.len > 1) {
	+ len += h->extras.len - 1;
	+ pos += h->extras.len - 1;
	+ bc_file_write(&vm.fout, bc_flush_none, h->extras.v, h->extras.len - 1);
	+ }

	// Write the prompt, if desired.
	#if BC_ENABLE_PROMPT
	- if (BC_USE_PROMPT) bc_file_write(&vm.fout, h->prompt, h->plen);
	+ if (BC_USE_PROMPT)
	+ bc_file_write(&vm.fout, bc_flush_none, h->prompt, h->plen);
	#endif // BC_ENABLE_PROMPT

	- bc_file_write(&vm.fout, buf, BC_HIST_BUF_LEN(h));
	+ bc_file_write(&vm.fout, bc_flush_none, buf, BC_HIST_BUF_LEN(h));

	// Erase to right.
	- bc_file_write(&vm.fout, "\x1b[0K", 4);
	+ bc_file_write(&vm.fout, bc_flush_none, "\x1b[0K", 4);

	// Move cursor to original position.
	colpos = bc_history_colPos(buf, len, pos) + h->pcol;

	if (colpos) bc_file_printf(&vm.fout, "\r\x1b[%zuC", colpos);

	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}

	/**
	* Insert the character 'c' at cursor current position.
	*/
	static void bc_history_edit_insert(BcHistory h, const char cbuf, size_t clen)
	{
	bc_vec_grow(&h->buf, clen);

	if (h->pos == BC_HIST_BUF_LEN(h)) {

	size_t colpos = 0, len;

	memcpy(bc_vec_item(&h->buf, h->pos), cbuf, clen);

	h->pos += clen;
	h->buf.len += clen - 1;
	bc_vec_pushByte(&h->buf, '\0');

	- len = BC_HIST_BUF_LEN(h);
	+ len = BC_HIST_BUF_LEN(h) + h->extras.len - 1;
	#if BC_ENABLE_PROMPT
	colpos = bc_history_promptColLen(h->prompt, h->plen);
	#endif // BC_ENABLE_PROMPT
	colpos += bc_history_colPos(h->buf.v, len, len);

	if (colpos < h->cols) {

	// Avoid a full update of the line in the trivial case.
	- bc_file_write(&vm.fout, cbuf, clen);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, cbuf, clen);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}
	else bc_history_refresh(h);
	}
	else {

	size_t amt = BC_HIST_BUF_LEN(h) - h->pos;

	memmove(h->buf.v + h->pos + clen, h->buf.v + h->pos, amt);
	memcpy(h->buf.v + h->pos, cbuf, clen);

	h->pos += clen;
	h->buf.len += clen;
	h->buf.v[BC_HIST_BUF_LEN(h)] = '\0';

	bc_history_refresh(h);
	}
	}

	/**
	* Move cursor to the left.
	*/
	static void bc_history_edit_left(BcHistory *h) {

	if (h->pos <= 0) return;

	h->pos -= bc_history_prevLen(h->buf.v, h->pos, NULL);

	bc_history_refresh(h);
	}

	/**
	* Move cursor on the right.
	*/
	static void bc_history_edit_right(BcHistory *h) {

	if (h->pos == BC_HIST_BUF_LEN(h)) return;

	h->pos += bc_history_nextLen(h->buf.v, BC_HIST_BUF_LEN(h), h->pos, NULL);

	bc_history_refresh(h);
	}

	/**
	* Move cursor to the end of the current word.
	*/
	static void bc_history_edit_wordEnd(BcHistory *h) {

	size_t len = BC_HIST_BUF_LEN(h);

	if (!len \|\| h->pos >= len) return;

	while (h->pos < len && isspace(h->buf.v[h->pos])) h->pos += 1;
	while (h->pos < len && !isspace(h->buf.v[h->pos])) h->pos += 1;

	bc_history_refresh(h);
	}

	/**
	* Move cursor to the start of the current word.
	*/
	static void bc_history_edit_wordStart(BcHistory *h) {

	size_t len = BC_HIST_BUF_LEN(h);

	if (!len) return;

	while (h->pos > 0 && isspace(h->buf.v[h->pos - 1])) h->pos -= 1;
	while (h->pos > 0 && !isspace(h->buf.v[h->pos - 1])) h->pos -= 1;

	bc_history_refresh(h);
	}

	/**
	* Move cursor to the start of the line.
	*/
	static void bc_history_edit_home(BcHistory *h) {

	if (!h->pos) return;

	h->pos = 0;

	bc_history_refresh(h);
	}

	/**
	* Move cursor to the end of the line.
	*/
	static void bc_history_edit_end(BcHistory *h) {

	if (h->pos == BC_HIST_BUF_LEN(h)) return;

	h->pos = BC_HIST_BUF_LEN(h);

	bc_history_refresh(h);
	}

	/**
	* Substitute the currently edited line with the next or previous history
	* entry as specified by 'dir' (direction).
	*/
	static void bc_history_edit_next(BcHistory *h, bool dir) {

	const char dup, str;

	if (h->history.len <= 1) return;

	BC_SIG_LOCK;

	if (h->buf.v[0]) dup = bc_vm_strdup(h->buf.v);
	else dup = "";

	// Update the current history entry before
	// overwriting it with the next one.
	bc_vec_replaceAt(&h->history, h->history.len - 1 - h->idx, &dup);

	BC_SIG_UNLOCK;

	// Show the new entry.
	h->idx += (dir == BC_HIST_PREV ? 1 : SIZE_MAX);

	if (h->idx == SIZE_MAX) {
	h->idx = 0;
	return;
	}
	else if (h->idx >= h->history.len) {
	h->idx = h->history.len - 1;
	return;
	}

	str = ((char*) bc_vec_item(&h->history, h->history.len - 1 - h->idx));
	bc_vec_string(&h->buf, strlen(str), str);
	assert(h->buf.len > 0);

	h->pos = BC_HIST_BUF_LEN(h);

	bc_history_refresh(h);
	}

	/**
	* Delete the character at the right of the cursor without altering the cursor
	* position. Basically this is what happens with the "Delete" keyboard key.
	*/
	static void bc_history_edit_delete(BcHistory *h) {

	size_t chlen, len = BC_HIST_BUF_LEN(h);

	if (!len \|\| h->pos >= len) return;

	chlen = bc_history_nextLen(h->buf.v, len, h->pos, NULL);

	memmove(h->buf.v + h->pos, h->buf.v + h->pos + chlen, len - h->pos - chlen);

	h->buf.len -= chlen;
	h->buf.v[BC_HIST_BUF_LEN(h)] = '\0';

	bc_history_refresh(h);
	}

	static void bc_history_edit_backspace(BcHistory *h) {

	size_t chlen, len = BC_HIST_BUF_LEN(h);

	if (!h->pos \|\| !len) return;

	chlen = bc_history_prevLen(h->buf.v, h->pos, NULL);

	memmove(h->buf.v + h->pos - chlen, h->buf.v + h->pos, len - h->pos);

	h->pos -= chlen;
	h->buf.len -= chlen;
	h->buf.v[BC_HIST_BUF_LEN(h)] = '\0';

	bc_history_refresh(h);
	}

	/**
	* Delete the previous word, maintaining the cursor at the start of the
	* current word.
	*/
	static void bc_history_edit_deletePrevWord(BcHistory *h) {

	size_t diff, old_pos = h->pos;

	while (h->pos > 0 && h->buf.v[h->pos - 1] == ' ') --h->pos;
	while (h->pos > 0 && h->buf.v[h->pos - 1] != ' ') --h->pos;

	diff = old_pos - h->pos;
	memmove(h->buf.v + h->pos, h->buf.v + old_pos,
	BC_HIST_BUF_LEN(h) - old_pos + 1);
	h->buf.len -= diff;

	bc_history_refresh(h);
	}

	/**
	* Delete the next word, maintaining the cursor at the same position.
	*/
	static void bc_history_edit_deleteNextWord(BcHistory *h) {

	size_t next_end = h->pos, len = BC_HIST_BUF_LEN(h);

	while (next_end < len && h->buf.v[next_end] == ' ') ++next_end;
	while (next_end < len && h->buf.v[next_end] != ' ') ++next_end;

	memmove(h->buf.v + h->pos, h->buf.v + next_end, len - next_end);

	h->buf.len -= next_end - h->pos;

	bc_history_refresh(h);
	}

	static void bc_history_swap(BcHistory *h) {

	size_t pcl, ncl;
	char auxb[5];

	pcl = bc_history_prevLen(h->buf.v, h->pos, NULL);
	ncl = bc_history_nextLen(h->buf.v, BC_HIST_BUF_LEN(h), h->pos, NULL);

	// To perform a swap we need:
	// * nonzero char length to the left
	// * not at the end of the line
	if (pcl && h->pos != BC_HIST_BUF_LEN(h) && pcl < 5 && ncl < 5) {

	memcpy(auxb, h->buf.v + h->pos - pcl, pcl);
	memcpy(h->buf.v + h->pos - pcl, h->buf.v + h->pos, ncl);
	memcpy(h->buf.v + h->pos - pcl + ncl, auxb, pcl);

	h->pos += -pcl + ncl;

	bc_history_refresh(h);
	}
	}

	/**
	* Handle escape sequences.
	*/
	static void bc_history_escape(BcHistory *h) {

	char c, seq[3];

	if (BC_ERR(BC_HIST_READ(seq, 1))) return;

	c = seq[0];

	// ESC ? sequences.
	if (c != '[' && c != 'O') {
	if (c == 'f') bc_history_edit_wordEnd(h);
	else if (c == 'b') bc_history_edit_wordStart(h);
	else if (c == 'd') bc_history_edit_deleteNextWord(h);
	}
	else {

	if (BC_ERR(BC_HIST_READ(seq + 1, 1)))
	bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	// ESC [ sequences.
	if (c == '[') {

	c = seq[1];

	if (c >= '0' && c <= '9') {

	// Extended escape, read additional byte.
	if (BC_ERR(BC_HIST_READ(seq + 2, 1)))
	bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	if (seq[2] == '~' && c == '3') bc_history_edit_delete(h);
	else if(seq[2] == ';') {

	if (BC_ERR(BC_HIST_READ(seq, 2)))
	bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	if (seq[0] != '5') return;
	else if (seq[1] == 'C') bc_history_edit_wordEnd(h);
	else if (seq[1] == 'D') bc_history_edit_wordStart(h);
	}
	}
	else {

	switch(c) {

	// Up.
	case 'A':
	{
	bc_history_edit_next(h, BC_HIST_PREV);
	break;
	}

	// Down.
	case 'B':
	{
	bc_history_edit_next(h, BC_HIST_NEXT);
	break;
	}

	// Right.
	case 'C':
	{
	bc_history_edit_right(h);
	break;
	}

	// Left.
	case 'D':
	{
	bc_history_edit_left(h);
	break;
	}

	// Home.
	case 'H':
	case '1':
	{
	bc_history_edit_home(h);
	break;
	}

	// End.
	case 'F':
	case '4':
	{
	bc_history_edit_end(h);
	break;
	}

	case 'd':
	{
	bc_history_edit_deleteNextWord(h);
	break;
	}
	}
	}
	}
	// ESC O sequences.
	else if (c == 'O') {

	switch (seq[1]) {

	case 'A':
	{
	bc_history_edit_next(h, BC_HIST_PREV);
	break;
	}

	case 'B':
	{
	bc_history_edit_next(h, BC_HIST_NEXT);
	break;
	}

	case 'C':
	{
	bc_history_edit_right(h);
	break;
	}

	case 'D':
	{
	bc_history_edit_left(h);
	break;
	}

	case 'F':
	{
	bc_history_edit_end(h);
	break;
	}

	case 'H':
	{
	bc_history_edit_home(h);
	break;
	}
	}
	}
	}
	}

	static void bc_history_reset(BcHistory *h) {

	h->oldcolpos = h->pos = h->idx = 0;
	h->cols = bc_history_columns();

	// The latest history entry is always our current buffer, that
	// initially is just an empty string.
	bc_history_add_empty(h);

	// Buffer starts empty.
	bc_vec_empty(&h->buf);
	}

	static void bc_history_printCtrl(BcHistory *h, unsigned int c) {

	char str[3] = "^A";
	const char newline[2] = "\n";

	str[1] = (char) (c + 'A' - BC_ACTION_CTRL_A);

	bc_vec_concat(&h->buf, str);

	bc_history_refresh(h);

	bc_vec_npop(&h->buf, sizeof(str));
	bc_vec_pushByte(&h->buf, '\0');

	if (c != BC_ACTION_CTRL_C && c != BC_ACTION_CTRL_D) {
	- bc_file_write(&vm.fout, newline, sizeof(newline) - 1);
	+ bc_file_write(&vm.fout, bc_flush_none, newline, sizeof(newline) - 1);
	bc_history_refresh(h);
	}
	}

	/**
	* This function is the core of the line editing capability of bc history.
	* It expects 'fd' to be already in "raw mode" so that every key pressed
	* will be returned ASAP to read().
	*/
	static BcStatus bc_history_edit(BcHistory h, const char prompt) {

	bc_history_reset(h);

	+ // Don't write the saved output the first time. This is because it has
	+ // already been written to output. In other words, don't uncomment the
	+ // line below or add anything like it.
	+ // bc_file_write(&vm.fout, bc_flush_none, h->extras.v, h->extras.len - 1);
	+
	#if BC_ENABLE_PROMPT
	if (BC_USE_PROMPT) {

	h->prompt = prompt;
	h->plen = strlen(prompt);
	h->pcol = bc_history_promptColLen(prompt, h->plen);

	- bc_file_write(&vm.fout, prompt, h->plen);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, prompt, h->plen);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}
	#endif // BC_ENABLE_PROMPT

	for (;;) {

	BcStatus s;
	// Large enough for any encoding?
	char cbuf[32];
	unsigned int c = 0;
	size_t nread = 0;

	s = bc_history_readCode(cbuf, sizeof(cbuf), &c, &nread);
	if (BC_ERR(s)) return s;

	switch (c) {

	case BC_ACTION_LINE_FEED:
	case BC_ACTION_ENTER:
	{
	bc_vec_pop(&h->history);
	return s;
	}

	case BC_ACTION_TAB:
	{
	memcpy(cbuf, bc_history_tab, bc_history_tab_len + 1);
	bc_history_edit_insert(h, cbuf, bc_history_tab_len);
	break;
	}

	case BC_ACTION_CTRL_C:
	{
	bc_history_printCtrl(h, c);
	- bc_file_write(&vm.fout, vm.sigmsg, vm.siglen);
	- bc_file_write(&vm.fout, bc_program_ready_msg,
	+ bc_file_write(&vm.fout, bc_flush_none, vm.sigmsg, vm.siglen);
	+ bc_file_write(&vm.fout, bc_flush_none, bc_program_ready_msg,
	bc_program_ready_msg_len);
	bc_history_reset(h);
	bc_history_refresh(h);
	break;
	}

	case BC_ACTION_BACKSPACE:
	case BC_ACTION_CTRL_H:
	{
	bc_history_edit_backspace(h);
	break;
	}

	// Act as end-of-file.
	case BC_ACTION_CTRL_D:
	{
	bc_history_printCtrl(h, c);
	return BC_STATUS_EOF;
	}

	// Swaps current character with previous.
	case BC_ACTION_CTRL_T:
	{
	bc_history_swap(h);
	break;
	}

	case BC_ACTION_CTRL_B:
	{
	bc_history_edit_left(h);
	break;
	}

	case BC_ACTION_CTRL_F:
	{
	bc_history_edit_right(h);
	break;
	}

	case BC_ACTION_CTRL_P:
	{
	bc_history_edit_next(h, BC_HIST_PREV);
	break;
	}

	case BC_ACTION_CTRL_N:
	{
	bc_history_edit_next(h, BC_HIST_NEXT);
	break;
	}

	case BC_ACTION_ESC:
	{
	bc_history_escape(h);
	break;
	}

	// Delete the whole line.
	case BC_ACTION_CTRL_U:
	{
	bc_vec_string(&h->buf, 0, "");
	h->pos = 0;

	bc_history_refresh(h);

	break;
	}

	// Delete from current to end of line.
	case BC_ACTION_CTRL_K:
	{
	bc_vec_npop(&h->buf, h->buf.len - h->pos);
	bc_vec_pushByte(&h->buf, '\0');
	bc_history_refresh(h);
	break;
	}

	// Go to the start of the line.
	case BC_ACTION_CTRL_A:
	{
	bc_history_edit_home(h);
	break;
	}

	// Go to the end of the line.
	case BC_ACTION_CTRL_E:
	{
	bc_history_edit_end(h);
	break;
	}

	// Clear screen.
	case BC_ACTION_CTRL_L:
	{
	- bc_file_write(&vm.fout, "\x1b[H\x1b[2J", 7);
	+ bc_file_write(&vm.fout, bc_flush_none, "\x1b[H\x1b[2J", 7);
	bc_history_refresh(h);
	break;
	}

	// Delete previous word.
	case BC_ACTION_CTRL_W:
	{
	bc_history_edit_deletePrevWord(h);
	break;
	}

	default:
	{
	if (c >= BC_ACTION_CTRL_A && c <= BC_ACTION_CTRL_Z)
	bc_history_printCtrl(h, c);
	else bc_history_edit_insert(h, cbuf, nread);
	break;
	}
	}
	}

	return BC_STATUS_SUCCESS;
	}

	static inline bool bc_history_stdinHasData(BcHistory *h) {
	int n;
	return pselect(1, &h->rdset, NULL, NULL, &h->ts, &h->sigmask) > 0 \|\|
	(ioctl(STDIN_FILENO, FIONREAD, &n) >= 0 && n > 0);
	}

	/**
	* This function calls the line editing function bc_history_edit()
	* using the STDIN file descriptor set in raw mode.
	*/
	static BcStatus bc_history_raw(BcHistory h, const char prompt) {

	BcStatus s;

	assert(vm.fout.len == 0);

	bc_history_enableRaw(h);

	s = bc_history_edit(h, prompt);

	h->stdin_has_data = bc_history_stdinHasData(h);
	if (!h->stdin_has_data) bc_history_disableRaw(h);

	- bc_file_write(&vm.fout, "\n", 1);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, "\n", 1);
	+ bc_file_flush(&vm.fout, bc_flush_none);

	return s;
	}

	BcStatus bc_history_line(BcHistory h, BcVec vec, const char *prompt) {

	BcStatus s;
	char* line;

	s = bc_history_raw(h, prompt);
	assert(!s \|\| s == BC_STATUS_EOF);

	bc_vec_string(vec, BC_HIST_BUF_LEN(h), h->buf.v);

	if (h->buf.v[0]) {

	BC_SIG_LOCK;

	line = bc_vm_strdup(h->buf.v);

	BC_SIG_UNLOCK;

	bc_history_add(h, line);
	}
	else bc_history_add_empty(h);

	bc_vec_concat(vec, "\n");

	return s;
	}

	static void bc_history_add(BcHistory h, char line) {

	if (h->history.len) {

	char s = ((char**) bc_vec_item_rev(&h->history, 0));

	if (!strcmp(s, line)) {

	BC_SIG_LOCK;

	free(line);

	BC_SIG_UNLOCK;

	return;
	}
	}

	bc_vec_push(&h->history, &line);
	}

	static void bc_history_add_empty(BcHistory *h) {

	const char *line = "";

	if (h->history.len) {

	char s = ((char**) bc_vec_item_rev(&h->history, 0));

	if (!s[0]) return;
	}

	bc_vec_push(&h->history, &line);
	}

	static void bc_history_string_free(void *str) {
	char s = ((char**) str);
	BC_SIG_ASSERT_LOCKED;
	if (s[0]) free(s);
	}

	void bc_history_init(BcHistory *h) {

	BC_SIG_ASSERT_LOCKED;

	bc_vec_init(&h->buf, sizeof(char), NULL);
	bc_vec_init(&h->history, sizeof(char*), bc_history_string_free);
	+ bc_vec_init(&h->extras, sizeof(char), NULL);

	FD_ZERO(&h->rdset);
	FD_SET(STDIN_FILENO, &h->rdset);
	h->ts.tv_sec = 0;
	h->ts.tv_nsec = 0;

	sigemptyset(&h->sigmask);
	sigaddset(&h->sigmask, SIGINT);

	h->rawMode = h->stdin_has_data = false;
	h->badTerm = bc_history_isBadTerm();
	}

	void bc_history_free(BcHistory *h) {
	BC_SIG_ASSERT_LOCKED;
	bc_history_disableRaw(h);
	#ifndef NDEBUG
	bc_vec_free(&h->buf);
	bc_vec_free(&h->history);
	+ bc_vec_free(&h->extras);
	#endif // NDEBUG
	}

	/**
	* This special mode is used by bc history in order to print scan codes
	* on screen for debugging / development purposes.
	*/
	#if BC_DEBUG_CODE
	void bc_history_printKeyCodes(BcHistory *h) {

	char quit[4];

	bc_vm_printf("Linenoise key codes debugging mode.\n"
	"Press keys to see scan codes. "
	"Type 'quit' at any time to exit.\n");

	bc_history_enableRaw(h);
	memset(quit, ' ', 4);

	while(true) {

	char c;
	ssize_t nread;

	nread = bc_history_read(&c, 1);
	if (nread <= 0) continue;

	// Shift string to left.
	memmove(quit, quit + 1, sizeof(quit) - 1);

	// Insert current char on the right.
	quit[sizeof(quit) - 1] = c;
	if (!memcmp(quit, "quit", sizeof(quit))) break;

	bc_vm_printf("'%c' %lu (type quit to exit)\n",
	isprint(c) ? c : '?', (unsigned long) c);

	// Go left edge manually, we are in raw mode.
	- bc_vm_putchar('\r');
	- bc_file_flush(&vm.fout);
	+ bc_vm_putchar('\r', bc_flush_none);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}

	bc_history_disableRaw(h);
	}
	#endif // BC_DEBUG_CODE

	#endif // BC_ENABLE_HISTORY
	diff --git a/contrib/bc/src/main.c b/contrib/bc/src/main.c
	index 84a48ff7e301..afe2fd8bb2ac 100644
	--- a/contrib/bc/src/main.c
	+++ b/contrib/bc/src/main.c
	@@ -1,81 +1,85 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* The entry point for bc.
	*
	*/

	#include <assert.h>
	#include <stdlib.h>
	#include <string.h>

	#include <locale.h>
	+
	+#ifndef _WIN32
	#include <libgen.h>
	+#endif // _WIN32

	#include <setjmp.h>

	+#include <version.h>
	#include <status.h>
	#include <vm.h>
	#include <bc.h>
	#include <dc.h>

	int main(int argc, char *argv[]) {

	char *name;
	size_t len = strlen(BC_EXECPREFIX);

	vm.locale = setlocale(LC_ALL, "");

	- name = strrchr(argv[0], '/');
	+ name = strrchr(argv[0], BC_FILE_SEP);
	vm.name = (name == NULL) ? argv[0] : name + 1;

	if (strlen(vm.name) > len) vm.name += len;

	BC_SIG_LOCK;

	bc_vec_init(&vm.jmp_bufs, sizeof(sigjmp_buf), NULL);

	BC_SETJMP_LOCKED(exit);

	#if !DC_ENABLED
	bc_main(argc, argv);
	#elif !BC_ENABLED
	dc_main(argc, argv);
	#else
	if (BC_IS_BC) bc_main(argc, argv);
	else dc_main(argc, argv);
	#endif

	exit:
	BC_SIG_MAYLOCK;

	return bc_vm_atexit((int) vm.status);
	}
	diff --git a/contrib/bc/src/num.c b/contrib/bc/src/num.c
	index 6131034ac535..5b84c2b88600 100644
	--- a/contrib/bc/src/num.c
	+++ b/contrib/bc/src/num.c
	@@ -1,2971 +1,2974 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code for the number type.
	*
	*/

	#include <assert.h>
	#include <ctype.h>
	#include <stdbool.h>
	#include <stdlib.h>
	#include <string.h>
	#include <setjmp.h>
	#include <limits.h>

	#include <num.h>
	#include <rand.h>
	#include <vm.h>

	static void bc_num_m(BcNum a, BcNum b, BcNum *restrict c, size_t scale);

	static inline ssize_t bc_num_neg(size_t n, bool neg) {
	return (((ssize_t) n) ^ -((ssize_t) neg)) + neg;
	}

	ssize_t bc_num_cmpZero(const BcNum *n) {
	return bc_num_neg((n)->len != 0, BC_NUM_NEG(n));
	}

	static inline size_t bc_num_int(const BcNum *n) {
	return n->len ? n->len - BC_NUM_RDX_VAL(n) : 0;
	}

	static void bc_num_expand(BcNum *restrict n, size_t req) {

	assert(n != NULL);

	req = req >= BC_NUM_DEF_SIZE ? req : BC_NUM_DEF_SIZE;

	if (req > n->cap) {

	BC_SIG_LOCK;

	n->num = bc_vm_realloc(n->num, BC_NUM_SIZE(req));
	n->cap = req;

	BC_SIG_UNLOCK;
	}
	}

	static void bc_num_setToZero(BcNum *restrict n, size_t scale) {
	assert(n != NULL);
	n->scale = scale;
	n->len = n->rdx = 0;
	}

	void bc_num_zero(BcNum *restrict n) {
	bc_num_setToZero(n, 0);
	}

	void bc_num_one(BcNum *restrict n) {
	bc_num_zero(n);
	n->len = 1;
	n->num[0] = 1;
	}

	static void bc_num_clean(BcNum *restrict n) {

	while (BC_NUM_NONZERO(n) && !n->num[n->len - 1]) n->len -= 1;

	if (BC_NUM_ZERO(n)) n->rdx = 0;
	else {
	size_t rdx = BC_NUM_RDX_VAL(n);
	if (n->len < rdx) n->len = rdx;
	}
	}

	static size_t bc_num_log10(size_t i) {
	size_t len;
	for (len = 1; i; i /= BC_BASE, ++len);
	assert(len - 1 <= BC_BASE_DIGS + 1);
	return len - 1;
	}

	static inline size_t bc_num_zeroDigits(const BcDig *n) {
	assert(*n >= 0);
	assert(((size_t) *n) < BC_BASE_POW);
	return BC_BASE_DIGS - bc_num_log10((size_t) *n);
	}

	static size_t bc_num_intDigits(const BcNum *n) {
	size_t digits = bc_num_int(n) * BC_BASE_DIGS;
	if (digits > 0) digits -= bc_num_zeroDigits(n->num + n->len - 1);
	return digits;
	}

	static size_t bc_num_nonzeroLen(const BcNum *restrict n) {
	size_t i, len = n->len;
	assert(len == BC_NUM_RDX_VAL(n));
	for (i = len - 1; i < len && !n->num[i]; --i);
	assert(i + 1 > 0);
	return i + 1;
	}

	static BcDig bc_num_addDigits(BcDig a, BcDig b, bool *carry) {

	assert(((BcBigDig) BC_BASE_POW) * 2 == ((BcDig) BC_BASE_POW) * 2);
	assert(a < BC_BASE_POW);
	assert(b < BC_BASE_POW);

	a += b + *carry;
	*carry = (a >= BC_BASE_POW);
	if (*carry) a -= BC_BASE_POW;

	assert(a >= 0);
	assert(a < BC_BASE_POW);

	return a;
	}

	static BcDig bc_num_subDigits(BcDig a, BcDig b, bool *carry) {

	assert(a < BC_BASE_POW);
	assert(b < BC_BASE_POW);

	b += *carry;
	*carry = (a < b);
	if (*carry) a += BC_BASE_POW;

	assert(a - b >= 0);
	assert(a - b < BC_BASE_POW);

	return a - b;
	}

	static void bc_num_addArrays(BcDig restrict a, const BcDig restrict b,
	size_t len)
	{
	size_t i;
	bool carry = false;

	for (i = 0; i < len; ++i) a[i] = bc_num_addDigits(a[i], b[i], &carry);

	for (; carry; ++i) a[i] = bc_num_addDigits(a[i], 0, &carry);
	}

	static void bc_num_subArrays(BcDig restrict a, const BcDig restrict b,
	size_t len)
	{
	size_t i;
	bool carry = false;

	for (i = 0; i < len; ++i) a[i] = bc_num_subDigits(a[i], b[i], &carry);

	for (; carry; ++i) a[i] = bc_num_subDigits(a[i], 0, &carry);
	}

	static void bc_num_mulArray(const BcNum *restrict a, BcBigDig b,
	BcNum *restrict c)
	{
	size_t i;
	BcBigDig carry = 0;

	assert(b <= BC_BASE_POW);

	if (a->len + 1 > c->cap) bc_num_expand(c, a->len + 1);

	memset(c->num, 0, BC_NUM_SIZE(c->cap));

	for (i = 0; i < a->len; ++i) {
	BcBigDig in = ((BcBigDig) a->num[i]) * b + carry;
	c->num[i] = in % BC_BASE_POW;
	carry = in / BC_BASE_POW;
	}

	assert(carry < BC_BASE_POW);
	c->num[i] = (BcDig) carry;
	c->len = a->len;
	c->len += (carry != 0);

	bc_num_clean(c);

	assert(!BC_NUM_NEG(c) \|\| BC_NUM_NONZERO(c));
	assert(BC_NUM_RDX_VAL(c) <= c->len \|\| !c->len);
	assert(!c->len \|\| c->num[c->len - 1] \|\| BC_NUM_RDX_VAL(c) == c->len);
	}

	static void bc_num_divArray(const BcNum *restrict a, BcBigDig b,
	BcNum restrict c, BcBigDig rem)
	{
	size_t i;
	BcBigDig carry = 0;

	assert(c->cap >= a->len);

	for (i = a->len - 1; i < a->len; --i) {
	BcBigDig in = ((BcBigDig) a->num[i]) + carry * BC_BASE_POW;
	assert(in / b < BC_BASE_POW);
	c->num[i] = (BcDig) (in / b);
	carry = in % b;
	}

	c->len = a->len;
	bc_num_clean(c);
	*rem = carry;

	assert(!BC_NUM_NEG(c) \|\| BC_NUM_NONZERO(c));
	assert(BC_NUM_RDX_VAL(c) <= c->len \|\| !c->len);
	assert(!c->len \|\| c->num[c->len - 1] \|\| BC_NUM_RDX_VAL(c) == c->len);
	}

	static ssize_t bc_num_compare(const BcDig restrict a, const BcDig restrict b,
	size_t len)
	{
	size_t i;
	BcDig c = 0;
	for (i = len - 1; i < len && !(c = a[i] - b[i]); --i);
	return bc_num_neg(i + 1, c < 0);
	}

	ssize_t bc_num_cmp(const BcNum a, const BcNum b) {

	size_t i, min, a_int, b_int, diff, ardx, brdx;
	BcDig max_num, min_num;
	bool a_max, neg = false;
	ssize_t cmp;

	assert(a != NULL && b != NULL);

	if (a == b) return 0;
	if (BC_NUM_ZERO(a)) return bc_num_neg(b->len != 0, !BC_NUM_NEG(b));
	if (BC_NUM_ZERO(b)) return bc_num_cmpZero(a);
	if (BC_NUM_NEG(a)) {
	if (BC_NUM_NEG(b)) neg = true;
	else return -1;
	}
	else if (BC_NUM_NEG(b)) return 1;

	a_int = bc_num_int(a);
	b_int = bc_num_int(b);
	a_int -= b_int;

	if (a_int) return neg ? -((ssize_t) a_int) : (ssize_t) a_int;

	ardx = BC_NUM_RDX_VAL(a);
	brdx = BC_NUM_RDX_VAL(b);
	a_max = (ardx > brdx);

	if (a_max) {
	min = brdx;
	diff = ardx - brdx;
	max_num = a->num + diff;
	min_num = b->num;
	}
	else {
	min = ardx;
	diff = brdx - ardx;
	max_num = b->num + diff;
	min_num = a->num;
	}

	cmp = bc_num_compare(max_num, min_num, b_int + min);

	if (cmp) return bc_num_neg((size_t) cmp, !a_max == !neg);

	for (max_num -= diff, i = diff - 1; i < diff; --i) {
	if (max_num[i]) return bc_num_neg(1, !a_max == !neg);
	}

	return 0;
	}

	void bc_num_truncate(BcNum *restrict n, size_t places) {

	size_t nrdx, places_rdx;

	if (!places) return;

	nrdx = BC_NUM_RDX_VAL(n);
	places_rdx = nrdx ? nrdx - BC_NUM_RDX(n->scale - places) : 0;
	assert(places <= n->scale && (BC_NUM_ZERO(n) \|\| places_rdx <= n->len));

	n->scale -= places;
	BC_NUM_RDX_SET(n, nrdx - places_rdx);

	if (BC_NUM_NONZERO(n)) {

	size_t pow;

	pow = n->scale % BC_BASE_DIGS;
	pow = pow ? BC_BASE_DIGS - pow : 0;
	pow = bc_num_pow10[pow];

	n->len -= places_rdx;
	memmove(n->num, n->num + places_rdx, BC_NUM_SIZE(n->len));

	// Clear the lower part of the last digit.
	if (BC_NUM_NONZERO(n)) n->num[0] -= n->num[0] % (BcDig) pow;

	bc_num_clean(n);
	}
	}

	void bc_num_extend(BcNum *restrict n, size_t places) {

	size_t nrdx, places_rdx;

	if (!places) return;
	if (BC_NUM_ZERO(n)) {
	n->scale += places;
	return;
	}

	nrdx = BC_NUM_RDX_VAL(n);
	places_rdx = BC_NUM_RDX(places + n->scale) - nrdx;

	if (places_rdx) {
	bc_num_expand(n, bc_vm_growSize(n->len, places_rdx));
	memmove(n->num + places_rdx, n->num, BC_NUM_SIZE(n->len));
	memset(n->num, 0, BC_NUM_SIZE(places_rdx));
	}

	BC_NUM_RDX_SET(n, nrdx + places_rdx);
	n->scale += places;
	n->len += places_rdx;

	assert(BC_NUM_RDX_VAL(n) == BC_NUM_RDX(n->scale));
	}

	static void bc_num_retireMul(BcNum *restrict n, size_t scale,
	bool neg1, bool neg2)
	{
	if (n->scale < scale) bc_num_extend(n, scale - n->scale);
	else bc_num_truncate(n, n->scale - scale);

	bc_num_clean(n);
	if (BC_NUM_NONZERO(n)) n->rdx = BC_NUM_NEG_VAL(n, !neg1 != !neg2);
	}

	static void bc_num_split(const BcNum *restrict n, size_t idx,
	BcNum restrict a, BcNum restrict b)
	{
	assert(BC_NUM_ZERO(a));
	assert(BC_NUM_ZERO(b));

	if (idx < n->len) {

	b->len = n->len - idx;
	a->len = idx;
	a->scale = b->scale = 0;
	BC_NUM_RDX_SET(a, 0);
	BC_NUM_RDX_SET(b, 0);

	assert(a->cap >= a->len);
	assert(b->cap >= b->len);

	memcpy(b->num, n->num + idx, BC_NUM_SIZE(b->len));
	memcpy(a->num, n->num, BC_NUM_SIZE(idx));

	bc_num_clean(b);
	}
	else bc_num_copy(a, n);

	bc_num_clean(a);
	}

	static size_t bc_num_shiftZero(BcNum *restrict n) {

	size_t i;

	assert(!BC_NUM_RDX_VAL(n) \|\| BC_NUM_ZERO(n));

	for (i = 0; i < n->len && !n->num[i]; ++i);

	n->len -= i;
	n->num += i;

	return i;
	}

	static void bc_num_unshiftZero(BcNum *restrict n, size_t places_rdx) {
	n->len += places_rdx;
	n->num -= places_rdx;
	}

	static void bc_num_shift(BcNum *restrict n, BcBigDig dig) {

	size_t i, len = n->len;
	BcBigDig carry = 0, pow;
	BcDig *ptr = n->num;

	assert(dig < BC_BASE_DIGS);

	pow = bc_num_pow10[dig];
	dig = bc_num_pow10[BC_BASE_DIGS - dig];

	for (i = len - 1; i < len; --i) {
	BcBigDig in, temp;
	in = ((BcBigDig) ptr[i]);
	temp = carry * dig;
	carry = in % pow;
	ptr[i] = ((BcDig) (in / pow)) + (BcDig) temp;
	}

	assert(!carry);
	}

	static void bc_num_shiftLeft(BcNum *restrict n, size_t places) {

	BcBigDig dig;
	size_t places_rdx;
	bool shift;

	if (!places) return;
	if (places > n->scale) {
	size_t size = bc_vm_growSize(BC_NUM_RDX(places - n->scale), n->len);
	if (size > SIZE_MAX - 1) bc_vm_err(BC_ERR_MATH_OVERFLOW);
	}
	if (BC_NUM_ZERO(n)) {
	if (n->scale >= places) n->scale -= places;
	else n->scale = 0;
	return;
	}

	dig = (BcBigDig) (places % BC_BASE_DIGS);
	shift = (dig != 0);
	places_rdx = BC_NUM_RDX(places);

	if (n->scale) {

	size_t nrdx = BC_NUM_RDX_VAL(n);

	if (nrdx >= places_rdx) {

	size_t mod = n->scale % BC_BASE_DIGS, revdig;

	mod = mod ? mod : BC_BASE_DIGS;
	revdig = dig ? BC_BASE_DIGS - dig : 0;

	if (mod + revdig > BC_BASE_DIGS) places_rdx = 1;
	else places_rdx = 0;
	}
	else places_rdx -= nrdx;
	}

	if (places_rdx) {
	bc_num_expand(n, bc_vm_growSize(n->len, places_rdx));
	memmove(n->num + places_rdx, n->num, BC_NUM_SIZE(n->len));
	memset(n->num, 0, BC_NUM_SIZE(places_rdx));
	n->len += places_rdx;
	}

	if (places > n->scale) {
	n->scale = 0;
	BC_NUM_RDX_SET(n, 0);
	}
	else {
	n->scale -= places;
	BC_NUM_RDX_SET(n, BC_NUM_RDX(n->scale));
	}

	if (shift) bc_num_shift(n, BC_BASE_DIGS - dig);

	bc_num_clean(n);
	}

	void bc_num_shiftRight(BcNum *restrict n, size_t places) {

	BcBigDig dig;
	size_t places_rdx, scale, scale_mod, int_len, expand;
	bool shift;

	if (!places) return;
	if (BC_NUM_ZERO(n)) {
	n->scale += places;
	bc_num_expand(n, BC_NUM_RDX(n->scale));
	return;
	}

	dig = (BcBigDig) (places % BC_BASE_DIGS);
	shift = (dig != 0);
	scale = n->scale;
	scale_mod = scale % BC_BASE_DIGS;
	scale_mod = scale_mod ? scale_mod : BC_BASE_DIGS;
	int_len = bc_num_int(n);
	places_rdx = BC_NUM_RDX(places);

	if (scale_mod + dig > BC_BASE_DIGS) {
	expand = places_rdx - 1;
	places_rdx = 1;
	}
	else {
	expand = places_rdx;
	places_rdx = 0;
	}

	if (expand > int_len) expand -= int_len;
	else expand = 0;

	bc_num_extend(n, places_rdx * BC_BASE_DIGS);
	bc_num_expand(n, bc_vm_growSize(expand, n->len));
	memset(n->num + n->len, 0, BC_NUM_SIZE(expand));
	n->len += expand;
	n->scale = 0;
	BC_NUM_RDX_SET(n, 0);

	if (shift) bc_num_shift(n, dig);

	n->scale = scale + places;
	BC_NUM_RDX_SET(n, BC_NUM_RDX(n->scale));

	bc_num_clean(n);

	assert(BC_NUM_RDX_VAL(n) <= n->len && n->len <= n->cap);
	assert(BC_NUM_RDX_VAL(n) == BC_NUM_RDX(n->scale));
	}

	static void bc_num_inv(BcNum a, BcNum b, size_t scale) {

	BcNum one;
	BcDig num[2];

	assert(BC_NUM_NONZERO(a));

	bc_num_setup(&one, num, sizeof(num) / sizeof(BcDig));
	bc_num_one(&one);

	bc_num_div(&one, a, b, scale);
	}

	#if BC_ENABLE_EXTRA_MATH
	static void bc_num_intop(const BcNum a, const BcNum b, BcNum *restrict c,
	BcBigDig *v)
	{
	if (BC_ERR(BC_NUM_RDX_VAL(b))) bc_vm_err(BC_ERR_MATH_NON_INTEGER);
	bc_num_copy(c, a);
	bc_num_bigdig(b, v);
	}
	#endif // BC_ENABLE_EXTRA_MATH

	static void bc_num_as(BcNum a, BcNum b, BcNum *restrict c, size_t sub) {

	BcDig ptr_c, ptr_l, *ptr_r;
	size_t i, min_rdx, max_rdx, diff, a_int, b_int, min_len, max_len, max_int;
	size_t len_l, len_r, ardx, brdx;
	bool b_neg, do_sub, do_rev_sub, carry, c_neg;

	// Because this function doesn't need to use scale (per the bc spec),
	// I am hijacking it to say whether it's doing an add or a subtract.
	// Convert substraction to addition of negative second operand.

	if (BC_NUM_ZERO(b)) {
	bc_num_copy(c, a);
	return;
	}
	if (BC_NUM_ZERO(a)) {
	bc_num_copy(c, b);
	c->rdx = BC_NUM_NEG_VAL(c, BC_NUM_NEG(b) != sub);
	return;
	}

	// Invert sign of b if it is to be subtracted. This operation must
	// preced the tests for any of the operands being zero.
	b_neg = (BC_NUM_NEG(b) != sub);

	// Actually add the numbers if their signs are equal, else subtract.
	do_sub = (BC_NUM_NEG(a) != b_neg);

	a_int = bc_num_int(a);
	b_int = bc_num_int(b);
	max_int = BC_MAX(a_int, b_int);

	ardx = BC_NUM_RDX_VAL(a);
	brdx = BC_NUM_RDX_VAL(b);
	min_rdx = BC_MIN(ardx, brdx);
	max_rdx = BC_MAX(ardx, brdx);
	diff = max_rdx - min_rdx;

	max_len = max_int + max_rdx;

	if (do_sub) {

	// Check whether b has to be subtracted from a or a from b.
	if (a_int != b_int) do_rev_sub = (a_int < b_int);
	else if (ardx > brdx)
	do_rev_sub = (bc_num_compare(a->num + diff, b->num, b->len) < 0);
	else
	do_rev_sub = (bc_num_compare(a->num, b->num + diff, a->len) <= 0);
	}
	else {

	// The result array of the addition might come out one element
	// longer than the bigger of the operand arrays.
	max_len += 1;
	do_rev_sub = (a_int < b_int);
	}

	assert(max_len <= c->cap);

	if (do_rev_sub) {
	ptr_l = b->num;
	ptr_r = a->num;
	len_l = b->len;
	len_r = a->len;
	}
	else {
	ptr_l = a->num;
	ptr_r = b->num;
	len_l = a->len;
	len_r = b->len;
	}

	ptr_c = c->num;
	carry = false;

	if (diff) {

	// If the rdx values of the operands do not match, the result will
	// have low end elements that are the positive or negative trailing
	// elements of the operand with higher rdx value.
	if ((ardx > brdx) != do_rev_sub) {

	// !do_rev_sub && ardx > brdx \|\| do_rev_sub && brdx > ardx
	// The left operand has BcDig values that need to be copied,
	// either from a or from b (in case of a reversed subtraction).
	memcpy(ptr_c, ptr_l, BC_NUM_SIZE(diff));
	ptr_l += diff;
	len_l -= diff;
	}
	else {

	// The right operand has BcDig values that need to be copied
	// or subtracted from zero (in case of a subtraction).
	if (do_sub) {

	// do_sub (do_rev_sub && ardx > brdx \|\|
	// !do_rev_sub && brdx > ardx)
	for (i = 0; i < diff; i++)
	ptr_c[i] = bc_num_subDigits(0, ptr_r[i], &carry);
	}
	else {

	// !do_sub && brdx > ardx
	memcpy(ptr_c, ptr_r, BC_NUM_SIZE(diff));
	}

	ptr_r += diff;
	len_r -= diff;
	}

	ptr_c += diff;
	}

	min_len = BC_MIN(len_l, len_r);

	// After dealing with possible low array elements that depend on only one
	// operand, the actual add or subtract can be performed as if the rdx of
	// both operands was the same.
	// Inlining takes care of eliminating constant zero arguments to
	// addDigit/subDigit (checked in disassembly of resulting bc binary
	// compiled with gcc and clang).
	if (do_sub) {
	for (i = 0; i < min_len; ++i)
	ptr_c[i] = bc_num_subDigits(ptr_l[i], ptr_r[i], &carry);
	for (; i < len_l; ++i) ptr_c[i] = bc_num_subDigits(ptr_l[i], 0, &carry);
	}
	else {
	for (i = 0; i < min_len; ++i)
	ptr_c[i] = bc_num_addDigits(ptr_l[i], ptr_r[i], &carry);
	for (; i < len_l; ++i) ptr_c[i] = bc_num_addDigits(ptr_l[i], 0, &carry);
	ptr_c[i] = bc_num_addDigits(0, 0, &carry);
	}

	assert(carry == false);

	// The result has the same sign as a, unless the operation was a
	// reverse subtraction (b - a).
	c_neg = BC_NUM_NEG(a) != (do_sub && do_rev_sub);
	BC_NUM_RDX_SET_NEG(c, max_rdx, c_neg);
	c->len = max_len;
	c->scale = BC_MAX(a->scale, b->scale);

	bc_num_clean(c);
	}

	static void bc_num_m_simp(const BcNum a, const BcNum b, BcNum *restrict c)
	{
	size_t i, alen = a->len, blen = b->len, clen;
	BcDig ptr_a = a->num, ptr_b = b->num, *ptr_c;
	BcBigDig sum = 0, carry = 0;

	assert(sizeof(sum) >= sizeof(BcDig) * 2);
	assert(!BC_NUM_RDX_VAL(a) && !BC_NUM_RDX_VAL(b));

	clen = bc_vm_growSize(alen, blen);
	bc_num_expand(c, bc_vm_growSize(clen, 1));

	ptr_c = c->num;
	memset(ptr_c, 0, BC_NUM_SIZE(c->cap));

	for (i = 0; i < clen; ++i) {

	ssize_t sidx = (ssize_t) (i - blen + 1);
	size_t j = (size_t) BC_MAX(0, sidx), k = BC_MIN(i, blen - 1);

	for (; j < alen && k < blen; ++j, --k) {

	sum += ((BcBigDig) ptr_a[j]) * ((BcBigDig) ptr_b[k]);

	if (sum >= ((BcBigDig) BC_BASE_POW) * BC_BASE_POW) {
	carry += sum / BC_BASE_POW;
	sum %= BC_BASE_POW;
	}
	}

	if (sum >= BC_BASE_POW) {
	carry += sum / BC_BASE_POW;
	sum %= BC_BASE_POW;
	}

	ptr_c[i] = (BcDig) sum;
	assert(ptr_c[i] < BC_BASE_POW);
	sum = carry;
	carry = 0;
	}

	// This should always be true because there should be no carry on the last
	// digit; multiplication never goes above the sum of both lengths.
	assert(!sum);

	c->len = clen;
	}

	static void bc_num_shiftAddSub(BcNum restrict n, const BcNum restrict a,
	size_t shift, BcNumShiftAddOp op)
	{
	assert(n->len >= shift + a->len);
	assert(!BC_NUM_RDX_VAL(n) && !BC_NUM_RDX_VAL(a));
	op(n->num + shift, a->num, a->len);
	}

	static void bc_num_k(BcNum a, BcNum b, BcNum *restrict c) {

	size_t max, max2, total;
	BcNum l1, h1, l2, h2, m2, m1, z0, z1, z2, temp;
	BcDig digs, dig_ptr;
	BcNumShiftAddOp op;
	bool aone = BC_NUM_ONE(a);

	assert(BC_NUM_ZERO(c));

	if (BC_NUM_ZERO(a) \|\| BC_NUM_ZERO(b)) return;
	if (aone \|\| BC_NUM_ONE(b)) {
	bc_num_copy(c, aone ? b : a);
	if ((aone && BC_NUM_NEG(a)) \|\| BC_NUM_NEG(b)) BC_NUM_NEG_TGL(c);
	return;
	}
	if (a->len < BC_NUM_KARATSUBA_LEN \|\| b->len < BC_NUM_KARATSUBA_LEN) {
	bc_num_m_simp(a, b, c);
	return;
	}

	max = BC_MAX(a->len, b->len);
	max = BC_MAX(max, BC_NUM_DEF_SIZE);
	max2 = (max + 1) / 2;

	total = bc_vm_arraySize(BC_NUM_KARATSUBA_ALLOCS, max);

	BC_SIG_LOCK;

	digs = dig_ptr = bc_vm_malloc(BC_NUM_SIZE(total));

	bc_num_setup(&l1, dig_ptr, max);
	dig_ptr += max;
	bc_num_setup(&h1, dig_ptr, max);
	dig_ptr += max;
	bc_num_setup(&l2, dig_ptr, max);
	dig_ptr += max;
	bc_num_setup(&h2, dig_ptr, max);
	dig_ptr += max;
	bc_num_setup(&m1, dig_ptr, max);
	dig_ptr += max;
	bc_num_setup(&m2, dig_ptr, max);
	max = bc_vm_growSize(max, 1);
	bc_num_init(&z0, max);
	bc_num_init(&z1, max);
	bc_num_init(&z2, max);
	max = bc_vm_growSize(max, max) + 1;
	bc_num_init(&temp, max);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_split(a, max2, &l1, &h1);
	bc_num_split(b, max2, &l2, &h2);

	bc_num_expand(c, max);
	c->len = max;
	memset(c->num, 0, BC_NUM_SIZE(c->len));

	bc_num_sub(&h1, &l1, &m1, 0);
	bc_num_sub(&l2, &h2, &m2, 0);

	if (BC_NUM_NONZERO(&h1) && BC_NUM_NONZERO(&h2)) {

	assert(BC_NUM_RDX_VALID_NP(h1));
	assert(BC_NUM_RDX_VALID_NP(h2));

	bc_num_m(&h1, &h2, &z2, 0);
	bc_num_clean(&z2);

	bc_num_shiftAddSub(c, &z2, max2 * 2, bc_num_addArrays);
	bc_num_shiftAddSub(c, &z2, max2, bc_num_addArrays);
	}

	if (BC_NUM_NONZERO(&l1) && BC_NUM_NONZERO(&l2)) {

	assert(BC_NUM_RDX_VALID_NP(l1));
	assert(BC_NUM_RDX_VALID_NP(l2));

	bc_num_m(&l1, &l2, &z0, 0);
	bc_num_clean(&z0);

	bc_num_shiftAddSub(c, &z0, max2, bc_num_addArrays);
	bc_num_shiftAddSub(c, &z0, 0, bc_num_addArrays);
	}

	if (BC_NUM_NONZERO(&m1) && BC_NUM_NONZERO(&m2)) {

	assert(BC_NUM_RDX_VALID_NP(m1));
	assert(BC_NUM_RDX_VALID_NP(m1));

	bc_num_m(&m1, &m2, &z1, 0);
	bc_num_clean(&z1);

	op = (BC_NUM_NEG_NP(m1) != BC_NUM_NEG_NP(m2)) ?
	bc_num_subArrays : bc_num_addArrays;
	bc_num_shiftAddSub(c, &z1, max2, op);
	}

	err:
	BC_SIG_MAYLOCK;
	free(digs);
	bc_num_free(&temp);
	bc_num_free(&z2);
	bc_num_free(&z1);
	bc_num_free(&z0);
	BC_LONGJMP_CONT;
	}

	static void bc_num_m(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcNum cpa, cpb;
	size_t ascale, bscale, ardx, brdx, azero = 0, bzero = 0, zero, len, rscale;

	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));

	bc_num_zero(c);
	ascale = a->scale;
	bscale = b->scale;
	scale = BC_MAX(scale, ascale);
	scale = BC_MAX(scale, bscale);

	rscale = ascale + bscale;
	scale = BC_MIN(rscale, scale);

	if ((a->len == 1 \|\| b->len == 1) && !a->rdx && !b->rdx) {

	BcNum *operand;
	BcBigDig dig;

	if (a->len == 1) {
	dig = (BcBigDig) a->num[0];
	operand = b;
	}
	else {
	dig = (BcBigDig) b->num[0];
	operand = a;
	}

	bc_num_mulArray(operand, dig, c);

	if (BC_NUM_NONZERO(c))
	c->rdx = BC_NUM_NEG_VAL(c, BC_NUM_NEG(a) != BC_NUM_NEG(b));

	return;
	}

	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));

	BC_SIG_LOCK;

	bc_num_init(&cpa, a->len + BC_NUM_RDX_VAL(a));
	bc_num_init(&cpb, b->len + BC_NUM_RDX_VAL(b));

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_copy(&cpa, a);
	bc_num_copy(&cpb, b);

	assert(BC_NUM_RDX_VALID_NP(cpa));
	assert(BC_NUM_RDX_VALID_NP(cpb));

	BC_NUM_NEG_CLR_NP(cpa);
	BC_NUM_NEG_CLR_NP(cpb);

	assert(BC_NUM_RDX_VALID_NP(cpa));
	assert(BC_NUM_RDX_VALID_NP(cpb));

	ardx = BC_NUM_RDX_VAL_NP(cpa) * BC_BASE_DIGS;
	bc_num_shiftLeft(&cpa, ardx);

	brdx = BC_NUM_RDX_VAL_NP(cpb) * BC_BASE_DIGS;
	bc_num_shiftLeft(&cpb, brdx);

	// We need to reset the jump here because azero and bzero are used in the
	// cleanup, and local variables are not guaranteed to be the same after a
	// jump.
	BC_SIG_LOCK;

	BC_UNSETJMP;

	azero = bc_num_shiftZero(&cpa);
	bzero = bc_num_shiftZero(&cpb);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_clean(&cpa);
	bc_num_clean(&cpb);

	bc_num_k(&cpa, &cpb, c);

	zero = bc_vm_growSize(azero, bzero);
	len = bc_vm_growSize(c->len, zero);

	bc_num_expand(c, len);
	bc_num_shiftLeft(c, (len - c->len) * BC_BASE_DIGS);
	bc_num_shiftRight(c, ardx + brdx);

	bc_num_retireMul(c, scale, BC_NUM_NEG(a), BC_NUM_NEG(b));

	err:
	BC_SIG_MAYLOCK;
	bc_num_unshiftZero(&cpb, bzero);
	bc_num_free(&cpb);
	bc_num_unshiftZero(&cpa, azero);
	bc_num_free(&cpa);
	BC_LONGJMP_CONT;
	}

	static bool bc_num_nonZeroDig(BcDig *restrict a, size_t len) {
	size_t i;
	bool nonzero = false;
	for (i = len - 1; !nonzero && i < len; --i) nonzero = (a[i] != 0);
	return nonzero;
	}

	static ssize_t bc_num_divCmp(const BcDig a, const BcNum b, size_t len) {

	ssize_t cmp;

	if (b->len > len && a[len]) cmp = bc_num_compare(a, b->num, len + 1);
	else if (b->len <= len) {
	if (a[len]) cmp = 1;
	else cmp = bc_num_compare(a, b->num, len);
	}
	else cmp = -1;

	return cmp;
	}

	static void bc_num_divExtend(BcNum restrict a, BcNum restrict b,
	BcBigDig divisor)
	{
	size_t pow;

	assert(divisor < BC_BASE_POW);

	pow = BC_BASE_DIGS - bc_num_log10((size_t) divisor);

	bc_num_shiftLeft(a, pow);
	bc_num_shiftLeft(b, pow);
	}

	static void bc_num_d_long(BcNum restrict a, BcNum restrict b,
	BcNum *restrict c, size_t scale)
	{
	BcBigDig divisor;
	size_t len, end, i, rdx;
	BcNum cpb;
	bool nonzero = false;

	assert(b->len < a->len);
	len = b->len;
	end = a->len - len;
	assert(len >= 1);

	bc_num_expand(c, a->len);
	memset(c->num, 0, c->cap * sizeof(BcDig));

	BC_NUM_RDX_SET(c, BC_NUM_RDX_VAL(a));
	c->scale = a->scale;
	c->len = a->len;

	divisor = (BcBigDig) b->num[len - 1];

	if (len > 1 && bc_num_nonZeroDig(b->num, len - 1)) {

	nonzero = (divisor > 1 << ((10 * BC_BASE_DIGS) / 6 + 1));

	if (!nonzero) {

	bc_num_divExtend(a, b, divisor);

	len = BC_MAX(a->len, b->len);
	bc_num_expand(a, len + 1);

	if (len + 1 > a->len) a->len = len + 1;

	len = b->len;
	end = a->len - len;
	divisor = (BcBigDig) b->num[len - 1];

	nonzero = bc_num_nonZeroDig(b->num, len - 1);
	}
	}

	divisor += nonzero;

	bc_num_expand(c, a->len);
	memset(c->num, 0, BC_NUM_SIZE(c->cap));

	assert(c->scale >= scale);
	rdx = BC_NUM_RDX_VAL(c) - BC_NUM_RDX(scale);

	BC_SIG_LOCK;

	bc_num_init(&cpb, len + 1);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	i = end - 1;

	for (; i < end && i >= rdx && BC_NUM_NONZERO(a); --i) {

	ssize_t cmp;
	BcDig *n;
	BcBigDig result;

	n = a->num + i;
	assert(n >= a->num);
	result = 0;

	cmp = bc_num_divCmp(n, b, len);

	while (cmp >= 0) {

	BcBigDig n1, dividend, q;

	n1 = (BcBigDig) n[len];
	dividend = n1 * BC_BASE_POW + (BcBigDig) n[len - 1];
	q = (dividend / divisor);

	if (q <= 1) {
	q = 1;
	bc_num_subArrays(n, b->num, len);
	}
	else {

	assert(q <= BC_BASE_POW);

	bc_num_mulArray(b, (BcBigDig) q, &cpb);
	bc_num_subArrays(n, cpb.num, cpb.len);
	}

	result += q;
	assert(result <= BC_BASE_POW);

	if (nonzero) cmp = bc_num_divCmp(n, b, len);
	else cmp = -1;
	}

	assert(result < BC_BASE_POW);

	c->num[i] = (BcDig) result;
	}

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&cpb);
	BC_LONGJMP_CONT;
	}

	static void bc_num_d(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	size_t len, cpardx;
	BcNum cpa, cpb;

	if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO);
	if (BC_NUM_ZERO(a)) {
	bc_num_setToZero(c, scale);
	return;
	}
	if (BC_NUM_ONE(b)) {
	bc_num_copy(c, a);
	bc_num_retireMul(c, scale, BC_NUM_NEG(a), BC_NUM_NEG(b));
	return;
	}
	if (!BC_NUM_RDX_VAL(a) && !BC_NUM_RDX_VAL(b) && b->len == 1 && !scale) {
	BcBigDig rem;
	bc_num_divArray(a, (BcBigDig) b->num[0], c, &rem);
	bc_num_retireMul(c, scale, BC_NUM_NEG(a), BC_NUM_NEG(b));
	return;
	}

	len = bc_num_divReq(a, b, scale);

	BC_SIG_LOCK;

	bc_num_init(&cpa, len);
	bc_num_copy(&cpa, a);
	bc_num_createCopy(&cpb, b);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	len = b->len;

	if (len > cpa.len) {
	bc_num_expand(&cpa, bc_vm_growSize(len, 2));
	bc_num_extend(&cpa, (len - cpa.len) * BC_BASE_DIGS);
	}

	cpardx = BC_NUM_RDX_VAL_NP(cpa);
	cpa.scale = cpardx * BC_BASE_DIGS;

	bc_num_extend(&cpa, b->scale);
	cpardx = BC_NUM_RDX_VAL_NP(cpa) - BC_NUM_RDX(b->scale);
	BC_NUM_RDX_SET_NP(cpa, cpardx);
	cpa.scale = cpardx * BC_BASE_DIGS;

	if (scale > cpa.scale) {
	bc_num_extend(&cpa, scale);
	cpardx = BC_NUM_RDX_VAL_NP(cpa);
	cpa.scale = cpardx * BC_BASE_DIGS;
	}

	if (cpa.cap == cpa.len) bc_num_expand(&cpa, bc_vm_growSize(cpa.len, 1));

	// We want an extra zero in front to make things simpler.
	cpa.num[cpa.len++] = 0;

	if (cpardx == cpa.len) cpa.len = bc_num_nonzeroLen(&cpa);
	if (BC_NUM_RDX_VAL_NP(cpb) == cpb.len) cpb.len = bc_num_nonzeroLen(&cpb);
	cpb.scale = 0;
	BC_NUM_RDX_SET_NP(cpb, 0);

	bc_num_d_long(&cpa, &cpb, c, scale);

	bc_num_retireMul(c, scale, BC_NUM_NEG(a), BC_NUM_NEG(b));

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&cpb);
	bc_num_free(&cpa);
	BC_LONGJMP_CONT;
	}

	static void bc_num_r(BcNum a, BcNum b, BcNum *restrict c,
	BcNum *restrict d, size_t scale, size_t ts)
	{
	BcNum temp;
	bool neg;

	if (BC_NUM_ZERO(b)) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO);
	if (BC_NUM_ZERO(a)) {
	bc_num_setToZero(c, ts);
	bc_num_setToZero(d, ts);
	return;
	}

	BC_SIG_LOCK;

	bc_num_init(&temp, d->cap);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_d(a, b, c, scale);

	if (scale) scale = ts + 1;

	assert(BC_NUM_RDX_VALID(c));
	assert(BC_NUM_RDX_VALID(b));

	bc_num_m(c, b, &temp, scale);
	bc_num_sub(a, &temp, d, scale);

	if (ts > d->scale && BC_NUM_NONZERO(d)) bc_num_extend(d, ts - d->scale);

	neg = BC_NUM_NEG(d);
	bc_num_retireMul(d, ts, BC_NUM_NEG(a), BC_NUM_NEG(b));
	d->rdx = BC_NUM_NEG_VAL(d, BC_NUM_NONZERO(d) ? neg : false);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&temp);
	BC_LONGJMP_CONT;
	}

	static void bc_num_rem(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcNum c1;
	size_t ts;

	ts = bc_vm_growSize(scale, b->scale);
	ts = BC_MAX(ts, a->scale);

	BC_SIG_LOCK;

	bc_num_init(&c1, bc_num_mulReq(a, b, ts));

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_r(a, b, &c1, c, scale, ts);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&c1);
	BC_LONGJMP_CONT;
	}

	static void bc_num_p(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcNum copy;
	BcBigDig pow = 0;
	size_t i, powrdx, resrdx;
	bool neg, zero;

	if (BC_ERR(BC_NUM_RDX_VAL(b))) bc_vm_err(BC_ERR_MATH_NON_INTEGER);

	if (BC_NUM_ZERO(b)) {
	bc_num_one(c);
	return;
	}
	if (BC_NUM_ZERO(a)) {
	if (BC_NUM_NEG(b)) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO);
	bc_num_setToZero(c, scale);
	return;
	}
	if (BC_NUM_ONE(b)) {
	if (!BC_NUM_NEG(b)) bc_num_copy(c, a);
	else bc_num_inv(a, c, scale);
	return;
	}

	BC_SIG_LOCK;

	neg = BC_NUM_NEG(b);
	BC_NUM_NEG_CLR(b);
	bc_num_bigdig(b, &pow);
	b->rdx = BC_NUM_NEG_VAL(b, neg);

	bc_num_createCopy(&copy, a);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	if (!neg) {
	size_t max = BC_MAX(scale, a->scale), scalepow = a->scale * pow;
	scale = BC_MIN(scalepow, max);
	}

	for (powrdx = a->scale; !(pow & 1); pow >>= 1) {
	powrdx <<= 1;
	assert(BC_NUM_RDX_VALID_NP(copy));
	bc_num_mul(&copy, &copy, &copy, powrdx);
	}

	bc_num_copy(c, &copy);
	resrdx = powrdx;

	while (pow >>= 1) {

	powrdx <<= 1;
	assert(BC_NUM_RDX_VALID_NP(copy));
	bc_num_mul(&copy, &copy, &copy, powrdx);

	if (pow & 1) {
	resrdx += powrdx;
	assert(BC_NUM_RDX_VALID(c));
	assert(BC_NUM_RDX_VALID_NP(copy));
	bc_num_mul(c, &copy, c, resrdx);
	}
	}

	if (neg) bc_num_inv(c, c, scale);

	if (c->scale > scale) bc_num_truncate(c, c->scale - scale);

	// We can't use bc_num_clean() here.
	for (zero = true, i = 0; zero && i < c->len; ++i) zero = !c->num[i];
	if (zero) bc_num_setToZero(c, scale);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&copy);
	BC_LONGJMP_CONT;
	}

	#if BC_ENABLE_EXTRA_MATH
	static void bc_num_place(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcBigDig val = 0;

	BC_UNUSED(scale);

	bc_num_intop(a, b, c, &val);

	if (val < c->scale) bc_num_truncate(c, c->scale - val);
	else if (val > c->scale) bc_num_extend(c, val - c->scale);
	}

	static void bc_num_left(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcBigDig val = 0;

	BC_UNUSED(scale);

	bc_num_intop(a, b, c, &val);

	bc_num_shiftLeft(c, (size_t) val);
	}

	static void bc_num_right(BcNum a, BcNum b, BcNum *restrict c, size_t scale) {

	BcBigDig val = 0;

	BC_UNUSED(scale);

	bc_num_intop(a, b, c, &val);

	if (BC_NUM_ZERO(c)) return;

	bc_num_shiftRight(c, (size_t) val);
	}
	#endif // BC_ENABLE_EXTRA_MATH

	static void bc_num_binary(BcNum a, BcNum b, BcNum *c, size_t scale,
	- BcNumBinaryOp op, size_t req)
	+ BcNumBinOp op, size_t req)
	{
	BcNum ptr_a, ptr_b, num2;
	bool init = false;

	assert(a != NULL && b != NULL && c != NULL && op != NULL);

	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));

	BC_SIG_LOCK;

	if (c == a) {

	ptr_a = &num2;

	memcpy(ptr_a, c, sizeof(BcNum));
	init = true;
	}
	else {
	ptr_a = a;
	}

	if (c == b) {

	ptr_b = &num2;

	if (c != a) {
	memcpy(ptr_b, c, sizeof(BcNum));
	init = true;
	}
	}
	else {
	ptr_b = b;
	}

	if (init) {

	bc_num_init(c, req);

	BC_SETJMP_LOCKED(err);
	BC_SIG_UNLOCK;
	}
	else {
	BC_SIG_UNLOCK;
	bc_num_expand(c, req);
	}

	op(ptr_a, ptr_b, c, scale);

	assert(!BC_NUM_NEG(c) \|\| BC_NUM_NONZERO(c));
	assert(BC_NUM_RDX_VAL(c) <= c->len \|\| !c->len);
	assert(BC_NUM_RDX_VALID(c));
	assert(!c->len \|\| c->num[c->len - 1] \|\| BC_NUM_RDX_VAL(c) == c->len);

	err:
	if (init) {
	BC_SIG_MAYLOCK;
	bc_num_free(&num2);
	BC_LONGJMP_CONT;
	}
	}

	#if !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY
	bool bc_num_strValid(const char *restrict val) {

	bool radix = false;
	size_t i, len = strlen(val);

	if (!len) return true;

	for (i = 0; i < len; ++i) {

	BcDig c = val[i];

	if (c == '.') {

	if (radix) return false;

	radix = true;
	continue;
	}

	if (!(isdigit(c) \|\| isupper(c))) return false;
	}

	return true;
	}
	#endif // !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY

	static BcBigDig bc_num_parseChar(char c, size_t base_t) {

	if (isupper(c)) {
	c = BC_NUM_NUM_LETTER(c);
	c = ((size_t) c) >= base_t ? (char) base_t - 1 : c;
	}
	else c -= '0';

	return (BcBigDig) (uchar) c;
	}

	static void bc_num_parseDecimal(BcNum restrict n, const char restrict val) {

	size_t len, i, temp, mod;
	const char *ptr;
	bool zero = true, rdx;

	for (i = 0; val[i] == '0'; ++i);

	val += i;
	assert(!val[0] \|\| isalnum(val[0]) \|\| val[0] == '.');

	// All 0's. We can just return, since this
	// procedure expects a virgin (already 0) BcNum.
	if (!val[0]) return;

	len = strlen(val);

	ptr = strchr(val, '.');
	rdx = (ptr != NULL);

	for (i = 0; i < len && (zero = (val[i] == '0' \|\| val[i] == '.')); ++i);

	n->scale = (size_t) (rdx * (((uintptr_t) (val + len)) -
	(((uintptr_t) ptr) + 1)));

	BC_NUM_RDX_SET(n, BC_NUM_RDX(n->scale));
	i = len - (ptr == val ? 0 : i) - rdx;
	temp = BC_NUM_ROUND_POW(i);
	mod = n->scale % BC_BASE_DIGS;
	i = mod ? BC_BASE_DIGS - mod : 0;
	n->len = ((temp + i) / BC_BASE_DIGS);

	bc_num_expand(n, n->len);
	memset(n->num, 0, BC_NUM_SIZE(n->len));

	if (zero) {
	// I think I can set rdx directly to zero here because n should be a
	// new number with sign set to false.
	n->len = n->rdx = 0;
	}
	else {

	BcBigDig exp, pow;

	assert(i <= BC_NUM_BIGDIG_MAX);

	exp = (BcBigDig) i;
	pow = bc_num_pow10[exp];

	for (i = len - 1; i < len; --i, ++exp) {

	char c = val[i];

	if (c == '.') exp -= 1;
	else {

	size_t idx = exp / BC_BASE_DIGS;

	if (isupper(c)) c = '9';
	n->num[idx] += (((BcBigDig) c) - '0') * pow;

	if ((exp + 1) % BC_BASE_DIGS == 0) pow = 1;
	else pow *= BC_BASE;
	}
	}
	}
	}

	static void bc_num_parseBase(BcNum restrict n, const char restrict val,
	BcBigDig base)
	{
	BcNum temp, mult1, mult2, result1, result2, m1, m2, *ptr;
	char c = 0;
	bool zero = true;
	BcBigDig v;
	size_t i, digs, len = strlen(val);

	for (i = 0; zero && i < len; ++i) zero = (val[i] == '.' \|\| val[i] == '0');
	if (zero) return;

	BC_SIG_LOCK;

	bc_num_init(&temp, BC_NUM_BIGDIG_LOG10);
	bc_num_init(&mult1, BC_NUM_BIGDIG_LOG10);

	BC_SETJMP_LOCKED(int_err);

	BC_SIG_UNLOCK;

	for (i = 0; i < len && (c = val[i]) && c != '.'; ++i) {

	v = bc_num_parseChar(c, base);

	bc_num_mulArray(n, base, &mult1);
	bc_num_bigdig2num(&temp, v);
	bc_num_add(&mult1, &temp, n, 0);
	}

	if (i == len && !val[i]) goto int_err;

	assert(val[i] == '.');

	BC_SIG_LOCK;

	BC_UNSETJMP;

	bc_num_init(&mult2, BC_NUM_BIGDIG_LOG10);
	bc_num_init(&result1, BC_NUM_DEF_SIZE);
	bc_num_init(&result2, BC_NUM_DEF_SIZE);
	bc_num_one(&mult1);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	m1 = &mult1;
	m2 = &mult2;

	for (i += 1, digs = 0; i < len && (c = val[i]); ++i, ++digs) {

	size_t rdx;

	v = bc_num_parseChar(c, base);

	bc_num_mulArray(&result1, base, &result2);

	bc_num_bigdig2num(&temp, v);
	bc_num_add(&result2, &temp, &result1, 0);
	bc_num_mulArray(m1, base, m2);

	rdx = BC_NUM_RDX_VAL(m2);

	if (m2->len < rdx) m2->len = rdx;

	ptr = m1;
	m1 = m2;
	m2 = ptr;
	}

	// This one cannot be a divide by 0 because mult starts out at 1, then is
	// multiplied by base, and base cannot be 0, so mult cannot be 0.
	bc_num_div(&result1, m1, &result2, digs * 2);
	bc_num_truncate(&result2, digs);
	bc_num_add(n, &result2, n, digs);

	if (BC_NUM_NONZERO(n)) {
	if (n->scale < digs) bc_num_extend(n, digs - n->scale);
	}
	else bc_num_zero(n);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&result2);
	bc_num_free(&result1);
	bc_num_free(&mult2);
	int_err:
	BC_SIG_MAYLOCK;
	bc_num_free(&mult1);
	bc_num_free(&temp);
	BC_LONGJMP_CONT;
	}

	static inline void bc_num_printNewline(void) {
	#if !BC_ENABLE_LIBRARY
	if (vm.nchars >= vm.line_len - 1) {
	- bc_vm_putchar('\\');
	- bc_vm_putchar('\n');
	+ bc_vm_putchar('\\', bc_flush_none);
	+ bc_vm_putchar('\n', bc_flush_err);
	}
	#endif // !BC_ENABLE_LIBRARY
	}

	static void bc_num_putchar(int c) {
	if (c != '\n') bc_num_printNewline();
	- bc_vm_putchar(c);
	+ bc_vm_putchar(c, bc_flush_save);
	}

	#if DC_ENABLED && !BC_ENABLE_LIBRARY
	static void bc_num_printChar(size_t n, size_t len, bool rdx) {
	BC_UNUSED(rdx);
	BC_UNUSED(len);
	assert(len == 1);
	- bc_vm_putchar((uchar) n);
	+ bc_vm_putchar((uchar) n, bc_flush_save);
	}
	#endif // DC_ENABLED && !BC_ENABLE_LIBRARY

	static void bc_num_printDigits(size_t n, size_t len, bool rdx) {

	size_t exp, pow;

	bc_num_putchar(rdx ? '.' : ' ');

	for (exp = 0, pow = 1; exp < len - 1; ++exp, pow *= BC_BASE);

	for (exp = 0; exp < len; pow /= BC_BASE, ++exp) {
	size_t dig = n / pow;
	n -= dig * pow;
	bc_num_putchar(((uchar) dig) + '0');
	}
	}

	static void bc_num_printHex(size_t n, size_t len, bool rdx) {

	BC_UNUSED(len);

	assert(len == 1);

	if (rdx) bc_num_putchar('.');

	bc_num_putchar(bc_num_hex_digits[n]);
	}

	static void bc_num_printDecimal(const BcNum *restrict n) {

	size_t i, j, rdx = BC_NUM_RDX_VAL(n);
	bool zero = true;
	size_t buffer[BC_BASE_DIGS];

	if (BC_NUM_NEG(n)) bc_num_putchar('-');

	for (i = n->len - 1; i < n->len; --i) {

	BcDig n9 = n->num[i];
	size_t temp;
	bool irdx = (i == rdx - 1);

	zero = (zero & !irdx);
	temp = n->scale % BC_BASE_DIGS;
	temp = i \|\| !temp ? 0 : BC_BASE_DIGS - temp;

	memset(buffer, 0, BC_BASE_DIGS * sizeof(size_t));

	for (j = 0; n9 && j < BC_BASE_DIGS; ++j) {
	buffer[j] = ((size_t) n9) % BC_BASE;
	n9 /= BC_BASE;
	}

	for (j = BC_BASE_DIGS - 1; j < BC_BASE_DIGS && j >= temp; --j) {
	bool print_rdx = (irdx & (j == BC_BASE_DIGS - 1));
	zero = (zero && buffer[j] == 0);
	if (!zero) bc_num_printHex(buffer[j], 1, print_rdx);
	}
	}
	}

	#if BC_ENABLE_EXTRA_MATH
	static void bc_num_printExponent(const BcNum *restrict n, bool eng) {

	size_t places, mod, nrdx = BC_NUM_RDX_VAL(n);
	bool neg = (n->len <= nrdx);
	BcNum temp, exp;
	BcDig digs[BC_NUM_BIGDIG_LOG10];

	BC_SIG_LOCK;

	bc_num_createCopy(&temp, n);

	BC_SETJMP_LOCKED(exit);

	BC_SIG_UNLOCK;

	if (neg) {

	size_t i, idx = bc_num_nonzeroLen(n) - 1;

	places = 1;

	for (i = BC_BASE_DIGS - 1; i < BC_BASE_DIGS; --i) {
	if (bc_num_pow10[i] > (BcBigDig) n->num[idx]) places += 1;
	else break;
	}

	places += (nrdx - (idx + 1)) * BC_BASE_DIGS;
	mod = places % 3;

	if (eng && mod != 0) places += 3 - mod;
	bc_num_shiftLeft(&temp, places);
	}
	else {
	places = bc_num_intDigits(n) - 1;
	mod = places % 3;
	if (eng && mod != 0) places -= 3 - (3 - mod);
	bc_num_shiftRight(&temp, places);
	}

	bc_num_printDecimal(&temp);
	bc_num_putchar('e');

	if (!places) {
	bc_num_printHex(0, 1, false);
	goto exit;
	}

	if (neg) bc_num_putchar('-');

	bc_num_setup(&exp, digs, BC_NUM_BIGDIG_LOG10);
	bc_num_bigdig2num(&exp, (BcBigDig) places);

	bc_num_printDecimal(&exp);

	exit:
	BC_SIG_MAYLOCK;
	bc_num_free(&temp);
	BC_LONGJMP_CONT;
	}
	#endif // BC_ENABLE_EXTRA_MATH

	static void bc_num_printFixup(BcNum *restrict n, BcBigDig rem,
	BcBigDig pow, size_t idx)
	{
	size_t i, len = n->len - idx;
	BcBigDig acc;
	BcDig *a = n->num + idx;

	if (len < 2) return;

	for (i = len - 1; i > 0; --i) {

	acc = ((BcBigDig) a[i]) * rem + ((BcBigDig) a[i - 1]);
	a[i - 1] = (BcDig) (acc % pow);
	acc /= pow;
	acc += (BcBigDig) a[i];

	if (acc >= BC_BASE_POW) {

	if (i == len - 1) {
	len = bc_vm_growSize(len, 1);
	bc_num_expand(n, bc_vm_growSize(len, idx));
	a = n->num + idx;
	a[len - 1] = 0;
	}

	a[i + 1] += acc / BC_BASE_POW;
	acc %= BC_BASE_POW;
	}

	assert(acc < BC_BASE_POW);
	a[i] = (BcDig) acc;
	}

	n->len = len + idx;
	}

	static void bc_num_printPrepare(BcNum *restrict n, BcBigDig rem,
	BcBigDig pow)
	{
	size_t i;

	for (i = 0; i < n->len; ++i) bc_num_printFixup(n, rem, pow, i);

	for (i = 0; i < n->len; ++i) {

	assert(pow == ((BcBigDig) ((BcDig) pow)));

	if (n->num[i] >= (BcDig) pow) {

	if (i + 1 == n->len) {
	n->len = bc_vm_growSize(n->len, 1);
	bc_num_expand(n, n->len);
	n->num[i + 1] = 0;
	}

	assert(pow < BC_BASE_POW);
	n->num[i + 1] += n->num[i] / ((BcDig) pow);
	n->num[i] %= (BcDig) pow;
	}
	}
	}

	static void bc_num_printNum(BcNum *restrict n, BcBigDig base,
	size_t len, BcNumDigitOp print)
	{
	BcVec stack;
	BcNum intp, fracp1, fracp2, digit, flen1, flen2, n1, n2, *temp;
	BcBigDig dig = 0, *ptr, acc, exp;
	size_t i, j, nrdx;
	bool radix;
	BcDig digit_digs[BC_NUM_BIGDIG_LOG10 + 1];

	assert(base > 1);

	if (BC_NUM_ZERO(n)) {
	print(0, len, false);
	return;
	}

	// This function uses an algorithm that Stefan Esser <se@freebsd.org> came
	// up with to print the integer part of a number. What it does is convert
	// intp into a number of the specified base, but it does it directly,
	// instead of just doing a series of divisions and printing the remainders
	// in reverse order.
	//
	// Let me explain in a bit more detail:
	//
	// The algorithm takes the current least significant digit (after intp has
	// been converted to an integer) and the next to least significant digit,
	// and it converts the least significant digit into one of the specified
	// base, putting any overflow into the next to least significant digit. It
	// iterates through the whole number, from least significant to most
	// significant, doing this conversion. At the end of that iteration, the
	// least significant digit is converted, but the others are not, so it
	// iterates again, starting at the next to least significant digit. It keeps
	// doing that conversion, skipping one more digit than the last time, until
	// all digits have been converted. Then it prints them in reverse order.
	//
	// That is the gist of the algorithm. It leaves out several things, such as
	// the fact that digits are not always converted into the specified base,
	// but into something close, basically a power of the specified base. In
	// Stefan's words, "You could consider BcDigs to be of base 10^BC_BASE_DIGS
	// in the normal case and obase^N for the largest value of N that satisfies
	// obase^N <= 10^BC_BASE_DIGS. [This means that] the result is not in base
	// "obase", but in base "obase^N", which happens to be printable as a number
	// of base "obase" without consideration for neighbouring BcDigs." This fact
	// is what necessitates the existence of the loop later in this function.
	//
	// The conversion happens in bc_num_printPrepare() where the outer loop
	// happens and bc_num_printFixup() where the inner loop, or actual
	// conversion, happens.

	nrdx = BC_NUM_RDX_VAL(n);

	BC_SIG_LOCK;

	bc_vec_init(&stack, sizeof(BcBigDig), NULL);
	bc_num_init(&fracp1, nrdx);

	bc_num_createCopy(&intp, n);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_truncate(&intp, intp.scale);

	bc_num_sub(n, &intp, &fracp1, 0);

	if (base != vm.last_base) {

	vm.last_pow = 1;
	vm.last_exp = 0;

	while (vm.last_pow * base <= BC_BASE_POW) {
	vm.last_pow *= base;
	vm.last_exp += 1;
	}

	vm.last_rem = BC_BASE_POW - vm.last_pow;
	vm.last_base = base;
	}

	exp = vm.last_exp;

	if (vm.last_rem != 0) bc_num_printPrepare(&intp, vm.last_rem, vm.last_pow);

	for (i = 0; i < intp.len; ++i) {

	acc = (BcBigDig) intp.num[i];

	for (j = 0; j < exp && (i < intp.len - 1 \|\| acc != 0); ++j)
	{
	if (j != exp - 1) {
	dig = acc % base;
	acc /= base;
	}
	else {
	dig = acc;
	acc = 0;
	}

	assert(dig < base);

	bc_vec_push(&stack, &dig);
	}

	assert(acc == 0);
	}

	for (i = 0; i < stack.len; ++i) {
	ptr = bc_vec_item_rev(&stack, i);
	assert(ptr != NULL);
	print(*ptr, len, false);
	}

	if (!n->scale) goto err;

	BC_SIG_LOCK;

	BC_UNSETJMP;

	bc_num_init(&fracp2, nrdx);
	bc_num_setup(&digit, digit_digs, sizeof(digit_digs) / sizeof(BcDig));
	bc_num_init(&flen1, BC_NUM_BIGDIG_LOG10);
	bc_num_init(&flen2, BC_NUM_BIGDIG_LOG10);

	BC_SETJMP_LOCKED(frac_err);

	BC_SIG_UNLOCK;

	bc_num_one(&flen1);

	radix = true;
	n1 = &flen1;
	n2 = &flen2;

	fracp2.scale = n->scale;
	BC_NUM_RDX_SET_NP(fracp2, BC_NUM_RDX(fracp2.scale));

	while (bc_num_intDigits(n1) < n->scale + 1) {

	bc_num_expand(&fracp2, fracp1.len + 1);
	bc_num_mulArray(&fracp1, base, &fracp2);

	nrdx = BC_NUM_RDX_VAL_NP(fracp2);

	if (fracp2.len < nrdx) fracp2.len = nrdx;

	// fracp is guaranteed to be non-negative and small enough.
	bc_num_bigdig2(&fracp2, &dig);

	bc_num_bigdig2num(&digit, dig);
	bc_num_sub(&fracp2, &digit, &fracp1, 0);

	print(dig, len, radix);
	bc_num_mulArray(n1, base, n2);

	radix = false;
	temp = n1;
	n1 = n2;
	n2 = temp;
	}

	frac_err:
	BC_SIG_MAYLOCK;
	bc_num_free(&flen2);
	bc_num_free(&flen1);
	bc_num_free(&fracp2);
	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&fracp1);
	bc_num_free(&intp);
	bc_vec_free(&stack);
	BC_LONGJMP_CONT;
	}

	static void bc_num_printBase(BcNum *restrict n, BcBigDig base) {

	size_t width;
	BcNumDigitOp print;
	bool neg = BC_NUM_NEG(n);

	if (neg) bc_num_putchar('-');

	BC_NUM_NEG_CLR(n);

	if (base <= BC_NUM_MAX_POSIX_IBASE) {
	width = 1;
	print = bc_num_printHex;
	}
	else {
	assert(base <= BC_BASE_POW);
	width = bc_num_log10(base - 1);
	print = bc_num_printDigits;
	}

	bc_num_printNum(n, base, width, print);
	n->rdx = BC_NUM_NEG_VAL(n, neg);
	}

	#if DC_ENABLED && !BC_ENABLE_LIBRARY
	void bc_num_stream(BcNum *restrict n, BcBigDig base) {
	bc_num_printNum(n, base, 1, bc_num_printChar);
	}
	#endif // DC_ENABLED && !BC_ENABLE_LIBRARY

	void bc_num_setup(BcNum restrict n, BcDig restrict num, size_t cap) {
	assert(n != NULL);
	n->num = num;
	n->cap = cap;
	bc_num_zero(n);
	}

	void bc_num_init(BcNum *restrict n, size_t req) {

	BcDig *num;

	BC_SIG_ASSERT_LOCKED;

	assert(n != NULL);

	req = req >= BC_NUM_DEF_SIZE ? req : BC_NUM_DEF_SIZE;

	if (req == BC_NUM_DEF_SIZE && vm.temps.len) {
	BcNum *nptr = bc_vec_top(&vm.temps);
	num = nptr->num;
	bc_vec_pop(&vm.temps);
	}
	else num = bc_vm_malloc(BC_NUM_SIZE(req));

	bc_num_setup(n, num, req);
	}

	void bc_num_clear(BcNum *restrict n) {
	n->num = NULL;
	n->cap = 0;
	}

	void bc_num_free(void *num) {

	BcNum n = (BcNum) num;

	BC_SIG_ASSERT_LOCKED;

	assert(n != NULL);

	if (n->cap == BC_NUM_DEF_SIZE) bc_vec_push(&vm.temps, n);
	else free(n->num);
	}

	void bc_num_copy(BcNum d, const BcNum s) {
	assert(d != NULL && s != NULL);
	if (d == s) return;
	bc_num_expand(d, s->len);
	d->len = s->len;
	// I can just copy directly here.
	d->rdx = s->rdx;
	d->scale = s->scale;
	memcpy(d->num, s->num, BC_NUM_SIZE(d->len));
	}

	void bc_num_createCopy(BcNum d, const BcNum s) {
	BC_SIG_ASSERT_LOCKED;
	bc_num_init(d, s->len);
	bc_num_copy(d, s);
	}

	void bc_num_createFromBigdig(BcNum *n, BcBigDig val) {
	BC_SIG_ASSERT_LOCKED;
	bc_num_init(n, BC_NUM_BIGDIG_LOG10);
	bc_num_bigdig2num(n, val);
	}

	size_t bc_num_scale(const BcNum *restrict n) {
	return n->scale;
	}

	size_t bc_num_len(const BcNum *restrict n) {

	size_t len = n->len;

	if (BC_NUM_ZERO(n)) return n->scale ? n->scale : 1;

	if (BC_NUM_RDX_VAL(n) == len) {

	size_t zero, scale;

	len = bc_num_nonzeroLen(n);

	scale = n->scale % BC_BASE_DIGS;
	scale = scale ? scale : BC_BASE_DIGS;

	zero = bc_num_zeroDigits(n->num + len - 1);

	len = len * BC_BASE_DIGS - zero - (BC_BASE_DIGS - scale);
	}
	else len = bc_num_intDigits(n) + n->scale;

	return len;
	}

	void bc_num_parse(BcNum restrict n, const char restrict val, BcBigDig base) {

	assert(n != NULL && val != NULL && base);
	assert(base >= BC_NUM_MIN_BASE && base <= vm.maxes[BC_PROG_GLOBALS_IBASE]);
	assert(bc_num_strValid(val));

	if (!val[1]) {
	BcBigDig dig = bc_num_parseChar(val[0], BC_NUM_MAX_LBASE);
	bc_num_bigdig2num(n, dig);
	}
	else if (base == BC_BASE) bc_num_parseDecimal(n, val);
	else bc_num_parseBase(n, val, base);

	assert(BC_NUM_RDX_VALID(n));
	}

	void bc_num_print(BcNum *restrict n, BcBigDig base, bool newline) {

	assert(n != NULL);
	assert(BC_ENABLE_EXTRA_MATH \|\| base >= BC_NUM_MIN_BASE);

	bc_num_printNewline();

	if (BC_NUM_ZERO(n)) bc_num_printHex(0, 1, false);
	else if (base == BC_BASE) bc_num_printDecimal(n);
	#if BC_ENABLE_EXTRA_MATH
	else if (base == 0 \|\| base == 1) bc_num_printExponent(n, base != 0);
	#endif // BC_ENABLE_EXTRA_MATH
	else bc_num_printBase(n, base);

	if (newline) bc_num_putchar('\n');
	}

	void bc_num_bigdig2(const BcNum restrict n, BcBigDig result) {

	// This function returns no errors because it's guaranteed to succeed if
	// its preconditions are met. Those preconditions include both parameters
	// being non-NULL, n being non-negative, and n being less than vm.max. If
	// all of that is true, then we can just convert without worrying about
	// negative errors or overflow.

	BcBigDig r = 0;
	size_t nrdx = BC_NUM_RDX_VAL(n);

	assert(n != NULL && result != NULL);
	assert(!BC_NUM_NEG(n));
	assert(bc_num_cmp(n, &vm.max) < 0);
	assert(n->len - nrdx <= 3);

	// There is a small speed win from unrolling the loop here, and since it
	// only adds 53 bytes, I decided that it was worth it.
	switch (n->len - nrdx) {

	case 3:
	{
	r = (BcBigDig) n->num[nrdx + 2];
	}
	// Fallthrough.
	BC_FALLTHROUGH

	case 2:
	{
	r = r * BC_BASE_POW + (BcBigDig) n->num[nrdx + 1];
	}
	// Fallthrough.
	BC_FALLTHROUGH

	case 1:
	{
	r = r * BC_BASE_POW + (BcBigDig) n->num[nrdx];
	}
	}

	*result = r;
	}

	void bc_num_bigdig(const BcNum restrict n, BcBigDig result) {

	assert(n != NULL && result != NULL);

	if (BC_ERR(BC_NUM_NEG(n))) bc_vm_err(BC_ERR_MATH_NEGATIVE);
	if (BC_ERR(bc_num_cmp(n, &vm.max) >= 0))
	bc_vm_err(BC_ERR_MATH_OVERFLOW);

	bc_num_bigdig2(n, result);
	}

	void bc_num_bigdig2num(BcNum *restrict n, BcBigDig val) {

	BcDig *ptr;
	size_t i;

	assert(n != NULL);

	bc_num_zero(n);

	if (!val) return;

	bc_num_expand(n, BC_NUM_BIGDIG_LOG10);

	for (ptr = n->num, i = 0; val; ++i, val /= BC_BASE_POW)
	ptr[i] = val % BC_BASE_POW;

	n->len = i;
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	void bc_num_rng(const BcNum restrict n, BcRNG rng) {

	BcNum temp, temp2, intn, frac;
	BcRand state1, state2, inc1, inc2;
	size_t nrdx = BC_NUM_RDX_VAL(n);

	BC_SIG_LOCK;

	bc_num_init(&temp, n->len);
	bc_num_init(&temp2, n->len);
	bc_num_init(&frac, nrdx);
	bc_num_init(&intn, bc_num_int(n));

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	assert(BC_NUM_RDX_VALID_NP(vm.max));

	memcpy(frac.num, n->num, BC_NUM_SIZE(nrdx));
	frac.len = nrdx;
	BC_NUM_RDX_SET_NP(frac, nrdx);
	frac.scale = n->scale;

	assert(BC_NUM_RDX_VALID_NP(frac));
	assert(BC_NUM_RDX_VALID_NP(vm.max2));

	bc_num_mul(&frac, &vm.max2, &temp, 0);

	bc_num_truncate(&temp, temp.scale);
	bc_num_copy(&frac, &temp);

	memcpy(intn.num, n->num + nrdx, BC_NUM_SIZE(bc_num_int(n)));
	intn.len = bc_num_int(n);

	// This assert is here because it has to be true. It is also here to justify
	// the use of BC_ERR_SIGNAL_ONLY() on each of the divmod's and mod's below.
	assert(BC_NUM_NONZERO(&vm.max));

	if (BC_NUM_NONZERO(&frac)) {

	bc_num_divmod(&frac, &vm.max, &temp, &temp2, 0);

	// frac is guaranteed to be smaller than vm.max * vm.max (pow).
	// This means that when dividing frac by vm.max, as above, the
	// quotient and remainder are both guaranteed to be less than vm.max,
	// which means we can use bc_num_bigdig2() here and not worry about
	// overflow.
	bc_num_bigdig2(&temp2, (BcBigDig*) &state1);
	bc_num_bigdig2(&temp, (BcBigDig*) &state2);
	}
	else state1 = state2 = 0;

	if (BC_NUM_NONZERO(&intn)) {

	bc_num_divmod(&intn, &vm.max, &temp, &temp2, 0);

	// Because temp2 is the mod of vm.max, from above, it is guaranteed
	// to be small enough to use bc_num_bigdig2().
	bc_num_bigdig2(&temp2, (BcBigDig*) &inc1);

	if (bc_num_cmp(&temp, &vm.max) >= 0) {
	bc_num_copy(&temp2, &temp);
	bc_num_mod(&temp2, &vm.max, &temp, 0);
	}

	// The if statement above ensures that temp is less than vm.max, which
	// means that we can use bc_num_bigdig2() here.
	bc_num_bigdig2(&temp, (BcBigDig*) &inc2);
	}
	else inc1 = inc2 = 0;

	bc_rand_seed(rng, state1, state2, inc1, inc2);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&intn);
	bc_num_free(&frac);
	bc_num_free(&temp2);
	bc_num_free(&temp);
	BC_LONGJMP_CONT;
	}

	void bc_num_createFromRNG(BcNum restrict n, BcRNG rng) {

	BcRand s1, s2, i1, i2;
	BcNum conv, temp1, temp2, temp3;
	BcDig temp1_num[BC_RAND_NUM_SIZE], temp2_num[BC_RAND_NUM_SIZE];
	BcDig conv_num[BC_NUM_BIGDIG_LOG10];

	BC_SIG_LOCK;

	bc_num_init(&temp3, 2 * BC_RAND_NUM_SIZE);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_setup(&temp1, temp1_num, sizeof(temp1_num) / sizeof(BcDig));
	bc_num_setup(&temp2, temp2_num, sizeof(temp2_num) / sizeof(BcDig));
	bc_num_setup(&conv, conv_num, sizeof(conv_num) / sizeof(BcDig));

	// This assert is here because it has to be true. It is also here to justify
	// the assumption that vm.max2 is not zero.
	assert(BC_NUM_NONZERO(&vm.max));

	// Because this is true, we can just use BC_ERR_SIGNAL_ONLY() below when
	// dividing by vm.max2.
	assert(BC_NUM_NONZERO(&vm.max2));

	bc_rand_getRands(rng, &s1, &s2, &i1, &i2);

	bc_num_bigdig2num(&conv, (BcBigDig) s2);

	assert(BC_NUM_RDX_VALID_NP(conv));

	bc_num_mul(&conv, &vm.max, &temp1, 0);

	bc_num_bigdig2num(&conv, (BcBigDig) s1);

	bc_num_add(&conv, &temp1, &temp2, 0);

	bc_num_div(&temp2, &vm.max2, &temp3, BC_RAND_STATE_BITS);

	bc_num_bigdig2num(&conv, (BcBigDig) i2);

	assert(BC_NUM_RDX_VALID_NP(conv));

	bc_num_mul(&conv, &vm.max, &temp1, 0);

	bc_num_bigdig2num(&conv, (BcBigDig) i1);

	bc_num_add(&conv, &temp1, &temp2, 0);

	bc_num_add(&temp2, &temp3, n, 0);

	assert(BC_NUM_RDX_VALID(n));

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&temp3);
	BC_LONGJMP_CONT;
	}

	void bc_num_irand(const BcNum restrict a, BcNum restrict b,
	BcRNG *restrict rng)
	{
	BcRand r;
	BcBigDig modl;
	BcNum pow, pow2, cp, cp2, mod, temp1, temp2, rand;
	BcNum p1, p2, t1, t2, c1, c2, *tmp;
	BcDig rand_num[BC_NUM_BIGDIG_LOG10];
	bool carry;
	ssize_t cmp;

	assert(a != b);

	if (BC_ERR(BC_NUM_NEG(a))) bc_vm_err(BC_ERR_MATH_NEGATIVE);
	if (BC_ERR(BC_NUM_RDX_VAL(a))) bc_vm_err(BC_ERR_MATH_NON_INTEGER);
	if (BC_NUM_ZERO(a) \|\| BC_NUM_ONE(a)) return;

	cmp = bc_num_cmp(a, &vm.max);

	if (cmp <= 0) {

	BcRand bits = 0;

	if (cmp < 0) bc_num_bigdig2(a, (BcBigDig*) &bits);

	// This condition means that bits is a power of 2. In that case, we
	// can just grab a full-size int and mask out the unneeded bits.
	// Also, this condition says that 0 is a power of 2, which works for
	// us, since a value of 0 means a == rng->max. The bitmask will mask
	// nothing in that case as well.
	if (!(bits & (bits - 1))) r = bc_rand_int(rng) & (bits - 1);
	else r = bc_rand_bounded(rng, bits);

	// We made sure that r is less than vm.max,
	// so we can use bc_num_bigdig2() here.
	bc_num_bigdig2num(b, r);

	return;
	}

	// In the case where a is less than rng->max, we have to make sure we have
	// an exclusive bound. This ensures that it happens. (See below.)
	carry = (cmp < 0);

	BC_SIG_LOCK;

	bc_num_createCopy(&cp, a);

	bc_num_init(&cp2, cp.len);
	bc_num_init(&mod, BC_NUM_BIGDIG_LOG10);
	bc_num_init(&temp1, BC_NUM_DEF_SIZE);
	bc_num_init(&temp2, BC_NUM_DEF_SIZE);
	bc_num_init(&pow2, BC_NUM_DEF_SIZE);
	bc_num_init(&pow, BC_NUM_DEF_SIZE);
	bc_num_one(&pow);
	bc_num_setup(&rand, rand_num, sizeof(rand_num) / sizeof(BcDig));

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	p1 = &pow;
	p2 = &pow2;
	t1 = &temp1;
	t2 = &temp2;
	c1 = &cp;
	c2 = &cp2;

	// This assert is here because it has to be true. It is also here to justify
	// the use of BC_ERR_SIGNAL_ONLY() on each of the divmod's and mod's below.
	assert(BC_NUM_NONZERO(&vm.max));

	while (BC_NUM_NONZERO(c1)) {

	bc_num_divmod(c1, &vm.max, c2, &mod, 0);

	// Because mod is the mod of vm.max, it is guaranteed to be smaller,
	// which means we can use bc_num_bigdig2() here.
	bc_num_bigdig(&mod, &modl);

	if (bc_num_cmp(c1, &vm.max) < 0) {

	// In this case, if there is no carry, then we know we can generate
	// an integer equal to modl. Thus, we add one if there is no
	// carry. Otherwise, we add zero, and we are still bounded properly.
	// Since the last portion is guaranteed to be greater than 1, we
	// know modl isn't 0 unless there is no carry.
	modl += !carry;

	if (modl == 1) r = 0;
	else if (!modl) r = bc_rand_int(rng);
	else r = bc_rand_bounded(rng, (BcRand) modl);
	}
	else {
	if (modl) modl -= carry;
	r = bc_rand_int(rng);
	carry = (r >= (BcRand) modl);
	}

	bc_num_bigdig2num(&rand, r);

	assert(BC_NUM_RDX_VALID_NP(rand));
	assert(BC_NUM_RDX_VALID(p1));

	bc_num_mul(&rand, p1, p2, 0);
	bc_num_add(p2, t1, t2, 0);

	if (BC_NUM_NONZERO(c2)) {

	assert(BC_NUM_RDX_VALID_NP(vm.max));
	assert(BC_NUM_RDX_VALID(p1));

	bc_num_mul(&vm.max, p1, p2, 0);

	tmp = p1;
	p1 = p2;
	p2 = tmp;

	tmp = c1;
	c1 = c2;
	c2 = tmp;
	}
	else c1 = c2;

	tmp = t1;
	t1 = t2;
	t2 = tmp;
	}

	bc_num_copy(b, t1);
	bc_num_clean(b);

	assert(BC_NUM_RDX_VALID(b));

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&pow);
	bc_num_free(&pow2);
	bc_num_free(&temp2);
	bc_num_free(&temp1);
	bc_num_free(&mod);
	bc_num_free(&cp2);
	bc_num_free(&cp);
	BC_LONGJMP_CONT;
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	size_t bc_num_addReq(const BcNum a, const BcNum b, size_t scale) {

	size_t aint, bint, ardx, brdx;

	BC_UNUSED(scale);

	ardx = BC_NUM_RDX_VAL(a);
	aint = bc_num_int(a);
	assert(aint <= a->len && ardx <= a->len);

	brdx = BC_NUM_RDX_VAL(b);
	bint = bc_num_int(b);
	assert(bint <= b->len && brdx <= b->len);

	ardx = BC_MAX(ardx, brdx);
	aint = BC_MAX(aint, bint);

	return bc_vm_growSize(bc_vm_growSize(ardx, aint), 1);
	}

	size_t bc_num_mulReq(const BcNum a, const BcNum b, size_t scale) {
	size_t max, rdx;
	rdx = bc_vm_growSize(BC_NUM_RDX_VAL(a), BC_NUM_RDX_VAL(b));
	max = BC_NUM_RDX(scale);
	max = bc_vm_growSize(BC_MAX(max, rdx), 1);
	rdx = bc_vm_growSize(bc_vm_growSize(bc_num_int(a), bc_num_int(b)), max);
	return rdx;
	}

	size_t bc_num_divReq(const BcNum a, const BcNum b, size_t scale) {
	size_t max, rdx;
	rdx = bc_vm_growSize(BC_NUM_RDX_VAL(a), BC_NUM_RDX_VAL(b));
	max = BC_NUM_RDX(scale);
	max = bc_vm_growSize(BC_MAX(max, rdx), 1);
	rdx = bc_vm_growSize(bc_num_int(a), max);
	return rdx;
	}

	size_t bc_num_powReq(const BcNum a, const BcNum b, size_t scale) {
	BC_UNUSED(scale);
	return bc_vm_growSize(bc_vm_growSize(a->len, b->len), 1);
	}

	#if BC_ENABLE_EXTRA_MATH
	size_t bc_num_placesReq(const BcNum a, const BcNum b, size_t scale) {
	BC_UNUSED(scale);
	return a->len + b->len - BC_NUM_RDX_VAL(a) - BC_NUM_RDX_VAL(b);
	}
	#endif // BC_ENABLE_EXTRA_MATH

	void bc_num_add(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, false, bc_num_as, bc_num_addReq(a, b, scale));
	}

	void bc_num_sub(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, true, bc_num_as, bc_num_addReq(a, b, scale));
	}

	void bc_num_mul(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_m, bc_num_mulReq(a, b, scale));
	}

	void bc_num_div(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_d, bc_num_divReq(a, b, scale));
	}

	void bc_num_mod(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_rem, bc_num_divReq(a, b, scale));
	}

	void bc_num_pow(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_p, bc_num_powReq(a, b, scale));
	}

	#if BC_ENABLE_EXTRA_MATH
	void bc_num_places(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_place, bc_num_placesReq(a, b, scale));
	}

	void bc_num_lshift(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_left, bc_num_placesReq(a, b, scale));
	}

	void bc_num_rshift(BcNum a, BcNum b, BcNum *c, size_t scale) {
	assert(BC_NUM_RDX_VALID(a));
	assert(BC_NUM_RDX_VALID(b));
	bc_num_binary(a, b, c, scale, bc_num_right, bc_num_placesReq(a, b, scale));
	}
	#endif // BC_ENABLE_EXTRA_MATH

	void bc_num_sqrt(BcNum restrict a, BcNum restrict b, size_t scale) {

	BcNum num1, num2, half, f, fprime, x0, x1, *temp;
	size_t pow, len, rdx, req, resscale;
	BcDig half_digs[1];

	assert(a != NULL && b != NULL && a != b);

	if (BC_ERR(BC_NUM_NEG(a))) bc_vm_err(BC_ERR_MATH_NEGATIVE);

	if (a->scale > scale) scale = a->scale;

	len = bc_vm_growSize(bc_num_intDigits(a), 1);
	rdx = BC_NUM_RDX(scale);
	req = bc_vm_growSize(BC_MAX(rdx, BC_NUM_RDX_VAL(a)), len >> 1);

	BC_SIG_LOCK;

	bc_num_init(b, bc_vm_growSize(req, 1));

	BC_SIG_UNLOCK;

	assert(a != NULL && b != NULL && a != b);
	assert(a->num != NULL && b->num != NULL);

	if (BC_NUM_ZERO(a)) {
	bc_num_setToZero(b, scale);
	return;
	}
	if (BC_NUM_ONE(a)) {
	bc_num_one(b);
	bc_num_extend(b, scale);
	return;
	}

	rdx = BC_NUM_RDX(scale);
	rdx = BC_MAX(rdx, BC_NUM_RDX_VAL(a));
	len = bc_vm_growSize(a->len, rdx);

	BC_SIG_LOCK;

	bc_num_init(&num1, len);
	bc_num_init(&num2, len);
	bc_num_setup(&half, half_digs, sizeof(half_digs) / sizeof(BcDig));

	bc_num_one(&half);
	half.num[0] = BC_BASE_POW / 2;
	half.len = 1;
	BC_NUM_RDX_SET_NP(half, 1);
	half.scale = 1;

	bc_num_init(&f, len);
	bc_num_init(&fprime, len);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	x0 = &num1;
	x1 = &num2;

	bc_num_one(x0);
	pow = bc_num_intDigits(a);

	if (pow) {

	if (pow & 1) x0->num[0] = 2;
	else x0->num[0] = 6;

	pow -= 2 - (pow & 1);
	bc_num_shiftLeft(x0, pow / 2);
	}

	// I can set the rdx here directly because neg should be false.
	x0->scale = x0->rdx = 0;
	resscale = (scale + BC_BASE_DIGS) + 2;

	while (bc_num_cmp(x1, x0)) {

	assert(BC_NUM_NONZERO(x0));

	bc_num_div(a, x0, &f, resscale);
	bc_num_add(x0, &f, &fprime, resscale);

	assert(BC_NUM_RDX_VALID_NP(fprime));
	assert(BC_NUM_RDX_VALID_NP(half));

	bc_num_mul(&fprime, &half, x1, resscale);

	temp = x0;
	x0 = x1;
	x1 = temp;
	}

	bc_num_copy(b, x0);
	if (b->scale > scale) bc_num_truncate(b, b->scale - scale);

	assert(!BC_NUM_NEG(b) \|\| BC_NUM_NONZERO(b));
	assert(BC_NUM_RDX_VALID(b));
	assert(BC_NUM_RDX_VAL(b) <= b->len \|\| !b->len);
	assert(!b->len \|\| b->num[b->len - 1] \|\| BC_NUM_RDX_VAL(b) == b->len);

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&fprime);
	bc_num_free(&f);
	bc_num_free(&num2);
	bc_num_free(&num1);
	BC_LONGJMP_CONT;
	}

	void bc_num_divmod(BcNum a, BcNum b, BcNum c, BcNum d, size_t scale) {

	size_t ts, len;
	BcNum *ptr_a, num2;
	bool init = false;

	ts = BC_MAX(scale + b->scale, a->scale);
	len = bc_num_mulReq(a, b, ts);

	assert(a != NULL && b != NULL && c != NULL && d != NULL);
	assert(c != d && a != d && b != d && b != c);

	if (c == a) {

	memcpy(&num2, c, sizeof(BcNum));
	ptr_a = &num2;

	BC_SIG_LOCK;

	bc_num_init(c, len);

	init = true;

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;
	}
	else {
	ptr_a = a;
	bc_num_expand(c, len);
	}

	if (BC_NUM_NONZERO(a) && !BC_NUM_RDX_VAL(a) &&
	!BC_NUM_RDX_VAL(b) && b->len == 1 && !scale)
	{
	BcBigDig rem;

	bc_num_divArray(ptr_a, (BcBigDig) b->num[0], c, &rem);

	assert(rem < BC_BASE_POW);

	d->num[0] = (BcDig) rem;
	d->len = (rem != 0);
	}
	else bc_num_r(ptr_a, b, c, d, scale, ts);

	assert(!BC_NUM_NEG(c) \|\| BC_NUM_NONZERO(c));
	assert(BC_NUM_RDX_VALID(c));
	assert(BC_NUM_RDX_VAL(c) <= c->len \|\| !c->len);
	assert(!c->len \|\| c->num[c->len - 1] \|\| BC_NUM_RDX_VAL(c) == c->len);
	assert(!BC_NUM_NEG(d) \|\| BC_NUM_NONZERO(d));
	assert(BC_NUM_RDX_VALID(d));
	assert(BC_NUM_RDX_VAL(d) <= d->len \|\| !d->len);
	assert(!d->len \|\| d->num[d->len - 1] \|\| BC_NUM_RDX_VAL(d) == d->len);

	err:
	if (init) {
	BC_SIG_MAYLOCK;
	bc_num_free(&num2);
	BC_LONGJMP_CONT;
	}
	}

	#if DC_ENABLED
	void bc_num_modexp(BcNum a, BcNum b, BcNum c, BcNum restrict d) {

	BcNum base, exp, two, temp;
	BcDig two_digs[2];

	assert(a != NULL && b != NULL && c != NULL && d != NULL);
	assert(a != d && b != d && c != d);

	if (BC_ERR(BC_NUM_ZERO(c))) bc_vm_err(BC_ERR_MATH_DIVIDE_BY_ZERO);
	if (BC_ERR(BC_NUM_NEG(b))) bc_vm_err(BC_ERR_MATH_NEGATIVE);
	if (BC_ERR(BC_NUM_RDX_VAL(a) \|\| BC_NUM_RDX_VAL(b) \|\| BC_NUM_RDX_VAL(c)))
	bc_vm_err(BC_ERR_MATH_NON_INTEGER);

	bc_num_expand(d, c->len);

	BC_SIG_LOCK;

	bc_num_init(&base, c->len);
	bc_num_setup(&two, two_digs, sizeof(two_digs) / sizeof(BcDig));
	bc_num_init(&temp, b->len + 1);
	bc_num_createCopy(&exp, b);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_num_one(&two);
	two.num[0] = 2;
	bc_num_one(d);

	// We already checked for 0.
	bc_num_rem(a, c, &base, 0);

	while (BC_NUM_NONZERO(&exp)) {

	// Num two cannot be 0, so no errors.
	bc_num_divmod(&exp, &two, &exp, &temp, 0);

	if (BC_NUM_ONE(&temp) && !BC_NUM_NEG_NP(temp)) {

	assert(BC_NUM_RDX_VALID(d));
	assert(BC_NUM_RDX_VALID_NP(base));

	bc_num_mul(d, &base, &temp, 0);

	// We already checked for 0.
	bc_num_rem(&temp, c, d, 0);
	}

	assert(BC_NUM_RDX_VALID_NP(base));

	bc_num_mul(&base, &base, &temp, 0);

	// We already checked for 0.
	bc_num_rem(&temp, c, &base, 0);
	}

	err:
	BC_SIG_MAYLOCK;
	bc_num_free(&exp);
	bc_num_free(&temp);
	bc_num_free(&base);
	BC_LONGJMP_CONT;
	assert(!BC_NUM_NEG(d) \|\| d->len);
	assert(BC_NUM_RDX_VALID(d));
	assert(!d->len \|\| d->num[d->len - 1] \|\| BC_NUM_RDX_VAL(d) == d->len);
	}
	#endif // DC_ENABLED

	#if BC_DEBUG_CODE
	void bc_num_printDebug(const BcNum n, const char name, bool emptyline) {
	- bc_file_puts(&vm.fout, name);
	- bc_file_puts(&vm.fout, ": ");
	+ bc_file_puts(&vm.fout, bc_flush_none, name);
	+ bc_file_puts(&vm.fout, bc_flush_none, ": ");
	bc_num_printDecimal(n);
	- bc_file_putchar(&vm.fout, '\n');
	- if (emptyline) bc_file_putchar(&vm.fout, '\n');
	+ bc_file_putchar(&vm.fout, bc_flush_err, '\n');
	+ if (emptyline) bc_file_putchar(&vm.fout, bc_flush_err, '\n');
	vm.nchars = 0;
	}

	void bc_num_printDigs(const BcDig *n, size_t len, bool emptyline) {

	size_t i;

	for (i = len - 1; i < len; --i)
	bc_file_printf(&vm.fout, " %lu", (unsigned long) n[i]);

	- bc_file_putchar(&vm.fout, '\n');
	- if (emptyline) bc_file_putchar(&vm.fout, '\n');
	+ bc_file_putchar(&vm.fout, bc_flush_err, '\n');
	+ if (emptyline) bc_file_putchar(&vm.fout, bc_flush_err, '\n');
	vm.nchars = 0;
	}

	void bc_num_printWithDigs(const BcNum n, const char name, bool emptyline) {
	- bc_file_puts(&vm.fout, name);
	+ bc_file_puts(&vm.fout, bc_flush_none, name);
	bc_file_printf(&vm.fout, " len: %zu, rdx: %zu, scale: %zu\n",
	name, n->len, BC_NUM_RDX_VAL(n), n->scale);
	bc_num_printDigs(n->num, n->len, emptyline);
	}

	void bc_num_dump(const char varname, const BcNum n) {

	ulong i, scale = n->scale;

	bc_file_printf(&vm.ferr, "\n%s = %s", varname,
	n->len ? (BC_NUM_NEG(n) ? "-" : "+") : "0 ");

	for (i = n->len - 1; i < n->len; --i) {

	- if (i + 1 == BC_NUM_RDX_VAL(n)) bc_file_puts(&vm.ferr, ". ");
	+ if (i + 1 == BC_NUM_RDX_VAL(n))
	+ bc_file_puts(&vm.ferr, bc_flush_none, ". ");

	if (scale / BC_BASE_DIGS != BC_NUM_RDX_VAL(n) - i - 1)
	bc_file_printf(&vm.ferr, "%lu ", (unsigned long) n->num[i]);
	else {

	int mod = scale % BC_BASE_DIGS;
	int d = BC_BASE_DIGS - mod;
	BcDig div;

	if (mod != 0) {
	div = n->num[i] / ((BcDig) bc_num_pow10[(ulong) d]);
	bc_file_printf(&vm.ferr, "%lu", (unsigned long) div);
	}

	div = n->num[i] % ((BcDig) bc_num_pow10[(ulong) d]);
	bc_file_printf(&vm.ferr, " ' %lu ", (unsigned long) div);
	}
	}

	bc_file_printf(&vm.ferr, "(%zu \| %zu.%zu / %zu) %lu\n",
	n->scale, n->len, BC_NUM_RDX_VAL(n), n->cap,
	(unsigned long) (void*) n->num);
	+
	+ bc_file_flush(&vm.ferr, bc_flush_err);
	}
	#endif // BC_DEBUG_CODE
	diff --git a/contrib/bc/src/program.c b/contrib/bc/src/program.c
	index 6ab794736f79..82735083bd03 100644
	--- a/contrib/bc/src/program.c
	+++ b/contrib/bc/src/program.c
	@@ -1,2347 +1,2353 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code to execute bc programs.
	*
	*/

	#include <assert.h>
	#include <stdbool.h>
	#include <string.h>

	#include <setjmp.h>

	#include <signal.h>

	#include <time.h>

	#include <read.h>
	#include <parse.h>
	#include <program.h>
	#include <vm.h>

	static void bc_program_addFunc(BcProgram p, BcFunc f, BcId *id_ptr);

	static inline void bc_program_setVecs(BcProgram p, BcFunc f) {
	p->consts = &f->consts;
	if (BC_IS_BC) p->strs = &f->strs;
	}

	static inline void bc_program_type_num(BcResult r, BcNum n) {

	#if BC_ENABLED
	assert(r->t != BC_RESULT_VOID);
	#endif // BC_ENABLED

	if (BC_ERR(!BC_PROG_NUM(r, n))) bc_vm_err(BC_ERR_EXEC_TYPE);
	}

	#if BC_ENABLED
	static void bc_program_type_match(BcResult *r, BcType t) {

	#if DC_ENABLED
	assert(BC_IS_DC \|\| BC_NO_ERR(r->t != BC_RESULT_STR));
	#endif // DC_ENABLED

	if (BC_ERR((r->t != BC_RESULT_ARRAY) != (!t)))
	bc_vm_err(BC_ERR_EXEC_TYPE);
	}
	#endif // BC_ENABLED

	static size_t bc_program_index(const char restrict code, size_t restrict bgn)
	{
	uchar amt = (uchar) code[(*bgn)++], i = 0;
	size_t res = 0;

	for (; i < amt; ++i, ++(*bgn)) {
	size_t temp = ((size_t) ((int) (uchar) code[*bgn]) & UCHAR_MAX);
	res \|= (temp << (i * CHAR_BIT));
	}

	return res;
	}

	#if BC_ENABLED
	static void bc_program_prepGlobals(BcProgram *p) {

	size_t i;

	for (i = 0; i < BC_PROG_GLOBALS_LEN; ++i)
	bc_vec_push(p->globals_v + i, p->globals + i);

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	bc_rand_push(&p->rng);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	}

	static void bc_program_popGlobals(BcProgram *p, bool reset) {

	size_t i;

	for (i = 0; i < BC_PROG_GLOBALS_LEN; ++i) {
	BcVec *v = p->globals_v + i;
	bc_vec_npop(v, reset ? v->len - 1 : 1);
	p->globals[i] = BC_PROG_GLOBAL(v);
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	bc_rand_pop(&p->rng, reset);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	}
	#endif // BC_ENABLED

	static void bc_program_pushBigdig(BcProgram *p, BcBigDig dig, BcResultType type)
	{
	BcResult res;

	res.t = type;

	BC_SIG_LOCK;

	bc_num_createFromBigdig(&res.d.n, dig);
	bc_vec_push(&p->results, &res);

	BC_SIG_UNLOCK;
	}

	#if BC_ENABLED
	static BcVec* bc_program_dereference(const BcProgram p, BcVec vec) {

	BcVec *v;
	size_t vidx, nidx, i = 0;

	assert(vec->size == sizeof(uchar));

	vidx = bc_program_index(vec->v, &i);
	nidx = bc_program_index(vec->v, &i);

	v = bc_vec_item(bc_vec_item(&p->arrs, vidx), nidx);

	assert(v->size != sizeof(uchar));

	return v;
	}
	#endif // BC_ENABLED

	size_t bc_program_search(BcProgram p, const char id, bool var) {

	BcVec v, map;
	size_t i;
	BcResultData data;

	v = var ? &p->vars : &p->arrs;
	map = var ? &p->var_map : &p->arr_map;

	BC_SIG_LOCK;

	if (bc_map_insert(map, id, v->len, &i)) {
	bc_array_init(&data.v, var);
	bc_vec_push(v, &data.v);
	}

	BC_SIG_UNLOCK;

	return ((BcId*) bc_vec_item(map, i))->idx;
	}

	static inline BcVec* bc_program_vec(const BcProgram *p, size_t idx, BcType type)
	{
	const BcVec *v = (type == BC_TYPE_VAR) ? &p->vars : &p->arrs;
	return bc_vec_item(v, idx);
	}

	static BcNum* bc_program_num(BcProgram p, BcResult r) {

	BcNum *n;

	switch (r->t) {

	case BC_RESULT_STR:
	case BC_RESULT_TEMP:
	case BC_RESULT_IBASE:
	case BC_RESULT_SCALE:
	case BC_RESULT_OBASE:
	#if BC_ENABLE_EXTRA_MATH
	case BC_RESULT_SEED:
	#endif // BC_ENABLE_EXTRA_MATH
	{
	n = &r->d.n;
	break;
	}

	case BC_RESULT_VAR:
	#if BC_ENABLED
	case BC_RESULT_ARRAY:
	#endif // BC_ENABLED
	case BC_RESULT_ARRAY_ELEM:
	{
	BcVec *v;
	BcType type = (r->t == BC_RESULT_VAR) ? BC_TYPE_VAR : BC_TYPE_ARRAY;

	v = bc_program_vec(p, r->d.loc.loc, type);

	if (r->t == BC_RESULT_ARRAY_ELEM) {

	size_t idx = r->d.loc.idx;

	v = bc_vec_top(v);

	#if BC_ENABLED
	if (v->size == sizeof(uchar)) v = bc_program_dereference(p, v);
	#endif // BC_ENABLED

	assert(v->size == sizeof(BcNum));

	if (v->len <= idx) {
	BC_SIG_LOCK;
	bc_array_expand(v, bc_vm_growSize(idx, 1));
	BC_SIG_UNLOCK;
	}

	n = bc_vec_item(v, idx);
	}
	else n = bc_vec_top(v);

	break;
	}

	case BC_RESULT_ZERO:
	{
	n = &p->zero;
	break;
	}

	case BC_RESULT_ONE:
	{
	n = &p->one;
	break;
	}

	#if BC_ENABLED
	case BC_RESULT_VOID:
	#ifndef NDEBUG
	{
	abort();
	}
	#endif // NDEBUG
	// Fallthrough
	case BC_RESULT_LAST:
	{
	n = &p->last;
	break;
	}
	#endif // BC_ENABLED
	}

	return n;
	}

	static void bc_program_operand(BcProgram p, BcResult *r,
	BcNum **n, size_t idx)
	{
	*r = bc_vec_item_rev(&p->results, idx);

	#if BC_ENABLED
	if (BC_ERR((*r)->t == BC_RESULT_VOID)) bc_vm_err(BC_ERR_EXEC_VOID_VAL);
	#endif // BC_ENABLED

	n = bc_program_num(p, r);
	}

	static void bc_program_binPrep(BcProgram p, BcResult l, BcNum *ln,
	BcResult r, BcNum rn, size_t idx)
	{
	BcResultType lt;

	assert(p != NULL && l != NULL && ln != NULL && r != NULL && rn != NULL);

	#ifndef BC_PROG_NO_STACK_CHECK
	if (BC_IS_DC) {
	if (BC_ERR(!BC_PROG_STACK(&p->results, idx + 2)))
	bc_vm_err(BC_ERR_EXEC_STACK);
	}
	#endif // BC_PROG_NO_STACK_CHECK

	assert(BC_PROG_STACK(&p->results, idx + 2));

	bc_program_operand(p, l, ln, idx + 1);
	bc_program_operand(p, r, rn, idx);

	lt = (*l)->t;

	#if BC_ENABLED
	assert(lt != BC_RESULT_VOID && (*r)->t != BC_RESULT_VOID);
	#endif // BC_ENABLED

	// We run this again under these conditions in case any vector has been
	// reallocated out from under the BcNums or arrays we had.
	if (lt == (*r)->t && (lt == BC_RESULT_VAR \|\| lt == BC_RESULT_ARRAY_ELEM))
	ln = bc_program_num(p, l);

	if (BC_ERR(lt == BC_RESULT_STR)) bc_vm_err(BC_ERR_EXEC_TYPE);
	}

	static void bc_program_binOpPrep(BcProgram p, BcResult l, BcNum *ln,
	BcResult r, BcNum rn, size_t idx)
	{
	bc_program_binPrep(p, l, ln, r, rn, idx);
	bc_program_type_num(l, ln);
	bc_program_type_num(r, rn);
	}

	static void bc_program_assignPrep(BcProgram p, BcResult l, BcNum *ln,
	BcResult r, BcNum rn)
	{
	BcResultType lt, min;

	min = BC_RESULT_TEMP - ((unsigned int) (BC_IS_BC));

	bc_program_binPrep(p, l, ln, r, rn, 0);

	lt = (*l)->t;

	if (BC_ERR(lt >= min && lt <= BC_RESULT_ONE))
	bc_vm_err(BC_ERR_EXEC_TYPE);

	#if DC_ENABLED
	if(BC_IS_DC) {

	bool good = (((r)->t == BC_RESULT_STR \|\| BC_PROG_STR(rn)) &&
	lt <= BC_RESULT_ARRAY_ELEM);

	if (!good) bc_program_type_num(r, rn);
	}
	#else
	assert((*r)->t != BC_RESULT_STR);
	#endif // DC_ENABLED
	}

	static void bc_program_prep(BcProgram p, BcResult r, BcNum *n, size_t idx) {

	assert(p != NULL && r != NULL && n != NULL);

	#ifndef BC_PROG_NO_STACK_CHECK
	if (BC_IS_DC) {
	if (BC_ERR(!BC_PROG_STACK(&p->results, idx + 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);
	}
	#endif // BC_PROG_NO_STACK_CHECK

	assert(BC_PROG_STACK(&p->results, idx + 1));

	bc_program_operand(p, r, n, idx);

	#if DC_ENABLED
	assert((r)->t != BC_RESULT_VAR \|\| !BC_PROG_STR(n));
	#endif // DC_ENABLED

	bc_program_type_num(r, n);
	}

	static BcResult* bc_program_prepResult(BcProgram *p) {

	BcResult res;

	bc_result_clear(&res);
	bc_vec_push(&p->results, &res);

	return bc_vec_top(&p->results);
	}

	static void bc_program_const(BcProgram p, const char code, size_t *bgn) {

	BcResult *r = bc_program_prepResult(p);
	BcConst *c = bc_vec_item(p->consts, bc_program_index(code, bgn));
	BcBigDig base = BC_PROG_IBASE(p);

	if (c->base != base) {

	if (c->num.num == NULL) {
	BC_SIG_LOCK;
	bc_num_init(&c->num, BC_NUM_RDX(strlen(c->val)));
	BC_SIG_UNLOCK;
	}

	// bc_num_parse() should only do operations that cannot fail.
	bc_num_parse(&c->num, c->val, base);

	c->base = base;
	}

	BC_SIG_LOCK;

	bc_num_createCopy(&r->d.n, &c->num);

	BC_SIG_UNLOCK;
	}

	static void bc_program_op(BcProgram *p, uchar inst) {

	BcResult opd1, opd2, *res;
	BcNum n1, n2;
	size_t idx = inst - BC_INST_POWER;

	res = bc_program_prepResult(p);

	bc_program_binOpPrep(p, &opd1, &n1, &opd2, &n2, 1);

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, bc_program_opReqs[idx](n1, n2, BC_PROG_SCALE(p)));

	BC_SIG_UNLOCK;

	assert(BC_NUM_RDX_VALID(n1));
	assert(BC_NUM_RDX_VALID(n2));

	bc_program_ops[idx](n1, n2, &res->d.n, BC_PROG_SCALE(p));

	bc_program_retire(p, 1, 2);
	}

	static void bc_program_read(BcProgram *p) {

	BcStatus s;
	BcParse parse;
	BcVec buf;
	BcInstPtr ip;
	size_t i;
	const char* file;
	BcFunc *f = bc_vec_item(&p->fns, BC_PROG_READ);

	for (i = 0; i < p->stack.len; ++i) {
	BcInstPtr *ip_ptr = bc_vec_item(&p->stack, i);
	if (ip_ptr->func == BC_PROG_READ)
	bc_vm_err(BC_ERR_EXEC_REC_READ);
	}

	BC_SIG_LOCK;

	file = vm.file;
	bc_parse_init(&parse, p, BC_PROG_READ);
	bc_vec_init(&buf, sizeof(char), NULL);

	BC_SETJMP_LOCKED(exec_err);

	BC_SIG_UNLOCK;

	bc_lex_file(&parse.l, bc_program_stdin_name);
	bc_vec_popAll(&f->code);

	- s = bc_read_line(&buf, BC_IS_BC ? "read> " : "?> ");
	+ if (BC_R) s = bc_read_line(&buf, "");
	+ else s = bc_read_line(&buf, BC_IS_BC ? "read> " : "?> ");
	+
	if (s == BC_STATUS_EOF) bc_vm_err(BC_ERR_EXEC_READ_EXPR);

	bc_parse_text(&parse, buf.v);
	vm.expr(&parse, BC_PARSE_NOREAD \| BC_PARSE_NEEDVAL);

	if (BC_ERR(parse.l.t != BC_LEX_NLINE && parse.l.t != BC_LEX_EOF))
	bc_vm_err(BC_ERR_EXEC_READ_EXPR);

	#if BC_ENABLED
	if (BC_G) bc_program_prepGlobals(p);
	#endif // BC_ENABLED

	ip.func = BC_PROG_READ;
	ip.idx = 0;
	ip.len = p->results.len;

	// Update this pointer, just in case.
	f = bc_vec_item(&p->fns, BC_PROG_READ);

	bc_vec_pushByte(&f->code, vm.read_ret);
	bc_vec_push(&p->stack, &ip);

	#if DC_ENABLED
	if (BC_IS_DC) {
	size_t temp = 0;
	bc_vec_push(&p->tail_calls, &temp);
	}
	#endif // DC_ENABLED

	exec_err:
	BC_SIG_MAYLOCK;
	bc_parse_free(&parse);
	bc_vec_free(&buf);
	vm.file = file;
	BC_LONGJMP_CONT;
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	static void bc_program_rand(BcProgram *p) {
	BcRand rand = bc_rand_int(&p->rng);
	bc_program_pushBigdig(p, (BcBigDig) rand, BC_RESULT_TEMP);
	#ifndef NDEBUG
	{
	BcResult *r = bc_vec_top(&p->results);
	assert(BC_NUM_RDX_VALID_NP(r->d.n));
	}
	#endif // NDEBUG
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	static void bc_program_printChars(const char *str) {

	const char *nl;
	size_t len = vm.nchars + strlen(str);

	- bc_file_puts(&vm.fout, str);
	+ bc_file_puts(&vm.fout, bc_flush_save, str);
	nl = strrchr(str, '\n');

	if (nl != NULL) len = strlen(nl + 1);

	vm.nchars = len > UINT16_MAX ? UINT16_MAX : (uint16_t) len;
	}

	static void bc_program_printString(const char *restrict str) {

	size_t i, len = strlen(str);

	#if DC_ENABLED
	if (!len && BC_IS_DC) {
	- bc_vm_putchar('\0');
	+ bc_vm_putchar('\0', bc_flush_save);
	return;
	}
	#endif // DC_ENABLED

	for (i = 0; i < len; ++i) {

	int c = str[i];

	if (c == '\\' && i != len - 1) {

	const char *ptr;

	c = str[++i];
	ptr = strchr(bc_program_esc_chars, c);

	if (ptr != NULL) {
	if (c == 'n') vm.nchars = UINT16_MAX;
	c = bc_program_esc_seqs[(size_t) (ptr - bc_program_esc_chars)];
	}
	else {
	// Just print the backslash. The following
	// character will be printed later.
	- bc_vm_putchar('\\');
	+ bc_vm_putchar('\\', bc_flush_save);
	}
	}

	- bc_vm_putchar(c);
	+ bc_vm_putchar(c, bc_flush_save);
	}
	}

	static void bc_program_print(BcProgram *p, uchar inst, size_t idx) {

	BcResult *r;
	char *str;
	BcNum *n;
	bool pop = (inst != BC_INST_PRINT);

	assert(p != NULL);

	#ifndef BC_PROG_NO_STACK_CHECK
	if (BC_IS_DC) {
	if (BC_ERR(!BC_PROG_STACK(&p->results, idx + 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);
	}
	#endif // BC_PROG_NO_STACK_CHECK

	assert(BC_PROG_STACK(&p->results, idx + 1));

	r = bc_vec_item_rev(&p->results, idx);

	#if BC_ENABLED
	if (r->t == BC_RESULT_VOID) {
	if (BC_ERR(pop)) bc_vm_err(BC_ERR_EXEC_VOID_VAL);
	bc_vec_pop(&p->results);
	return;
	}
	#endif // BC_ENABLED

	n = bc_program_num(p, r);

	if (BC_PROG_NUM(r, n)) {
	assert(inst != BC_INST_PRINT_STR);
	bc_num_print(n, BC_PROG_OBASE(p), !pop);
	#if BC_ENABLED
	if (BC_IS_BC) bc_num_copy(&p->last, n);
	#endif // BC_ENABLED
	}
	else {

	size_t i = (r->t == BC_RESULT_STR) ? r->d.loc.loc : n->scale;

	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_save);
	str = ((char*) bc_vec_item(p->strs, i));

	if (inst == BC_INST_PRINT_STR) bc_program_printChars(str);
	else {
	bc_program_printString(str);
	- if (inst == BC_INST_PRINT) bc_vm_putchar('\n');
	+ if (inst == BC_INST_PRINT)
	+ bc_vm_putchar('\n', bc_flush_err);
	}
	}

	if (BC_IS_BC \|\| pop) bc_vec_pop(&p->results);
	}

	void bc_program_negate(BcResult r, BcNum n) {
	bc_num_copy(&r->d.n, n);
	if (BC_NUM_NONZERO(&r->d.n)) BC_NUM_NEG_TGL_NP(r->d.n);
	}

	void bc_program_not(BcResult r, BcNum n) {
	if (!bc_num_cmpZero(n)) bc_num_one(&r->d.n);
	}

	#if BC_ENABLE_EXTRA_MATH
	void bc_program_trunc(BcResult r, BcNum n) {
	bc_num_copy(&r->d.n, n);
	bc_num_truncate(&r->d.n, n->scale);
	}
	#endif // BC_ENABLE_EXTRA_MATH

	static void bc_program_unary(BcProgram *p, uchar inst) {

	BcResult res, ptr;
	BcNum *num;

	res = bc_program_prepResult(p);

	bc_program_prep(p, &ptr, &num, 1);

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, num->len);

	BC_SIG_UNLOCK;

	bc_program_unarys[inst - BC_INST_NEG](res, num);
	bc_program_retire(p, 1, 1);
	}

	static void bc_program_logical(BcProgram *p, uchar inst) {

	BcResult opd1, opd2, *res;
	BcNum n1, n2;
	bool cond = 0;
	ssize_t cmp;

	res = bc_program_prepResult(p);

	bc_program_binOpPrep(p, &opd1, &n1, &opd2, &n2, 1);

	if (inst == BC_INST_BOOL_AND)
	cond = (bc_num_cmpZero(n1) && bc_num_cmpZero(n2));
	else if (inst == BC_INST_BOOL_OR)
	cond = (bc_num_cmpZero(n1) \|\| bc_num_cmpZero(n2));
	else {

	cmp = bc_num_cmp(n1, n2);

	switch (inst) {

	case BC_INST_REL_EQ:
	{
	cond = (cmp == 0);
	break;
	}

	case BC_INST_REL_LE:
	{
	cond = (cmp <= 0);
	break;
	}

	case BC_INST_REL_GE:
	{
	cond = (cmp >= 0);
	break;
	}

	case BC_INST_REL_NE:
	{
	cond = (cmp != 0);
	break;
	}

	case BC_INST_REL_LT:
	{
	cond = (cmp < 0);
	break;
	}

	case BC_INST_REL_GT:
	{
	cond = (cmp > 0);
	break;
	}
	#ifndef NDEBUG
	default:
	{
	abort();
	}
	#endif // NDEBUG
	}
	}

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, BC_NUM_DEF_SIZE);

	BC_SIG_UNLOCK;

	if (cond) bc_num_one(&res->d.n);

	bc_program_retire(p, 1, 2);
	}

	#if DC_ENABLED
	static void bc_program_assignStr(BcProgram *p, size_t idx,
	BcVec *v, bool push)
	{
	BcNum n2;

	bc_num_clear(&n2);
	n2.scale = idx;

	assert(BC_PROG_STACK(&p->results, 1 + !push));

	if (!push) bc_vec_pop(v);

	bc_vec_npop(&p->results, 1 + !push);
	bc_vec_push(v, &n2);
	}
	#endif // DC_ENABLED

	static void bc_program_copyToVar(BcProgram *p, size_t idx,
	BcType t, bool last)
	{
	BcResult *ptr = NULL, r;
	BcVec *vec;
	BcNum *n = NULL;
	bool var = (t == BC_TYPE_VAR);

	#if DC_ENABLED
	if (BC_IS_DC) {

	if (BC_ERR(!BC_PROG_STACK(&p->results, 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 1));

	bc_program_operand(p, &ptr, &n, 0);
	}
	#endif

	#if BC_ENABLED
	if (BC_IS_BC)
	{
	ptr = bc_vec_top(&p->results);

	bc_program_type_match(ptr, t);

	if (last) n = bc_program_num(p, ptr);
	else if (var)
	n = bc_vec_item_rev(bc_program_vec(p, ptr->d.loc.loc, t), 1);
	}
	#endif // BC_ENABLED

	vec = bc_program_vec(p, idx, t);

	#if DC_ENABLED
	if (BC_IS_DC && (ptr->t == BC_RESULT_STR \|\| BC_PROG_STR(n))) {

	size_t str_idx = ptr->t == BC_RESULT_STR ? ptr->d.loc.loc : n->scale;

	if (BC_ERR(!var)) bc_vm_err(BC_ERR_EXEC_TYPE);

	bc_program_assignStr(p, str_idx, vec, true);

	return;
	}
	#endif // DC_ENABLED

	BC_SIG_LOCK;

	if (var) bc_num_createCopy(&r.d.n, n);
	else {

	BcVec v = (BcVec) n, *rv = &r.d.v;
	#if BC_ENABLED
	BcVec *parent;
	bool ref, ref_size;

	parent = bc_program_vec(p, ptr->d.loc.loc, t);
	assert(parent != NULL);

	if (!last) v = bc_vec_item_rev(parent, !last);
	assert(v != NULL);

	ref = (v->size == sizeof(BcNum) && t == BC_TYPE_REF);
	ref_size = (v->size == sizeof(uchar));

	if (ref \|\| (ref_size && t == BC_TYPE_REF)) {

	bc_vec_init(rv, sizeof(uchar), NULL);

	if (ref) {

	assert(parent->len >= (size_t) (!last + 1));

	// Make sure the pointer was not invalidated.
	vec = bc_program_vec(p, idx, t);

	bc_vec_pushIndex(rv, ptr->d.loc.loc);
	bc_vec_pushIndex(rv, parent->len - !last - 1);
	}
	// If we get here, we are copying a ref to a ref.
	else bc_vec_npush(rv, v->len * sizeof(uchar), v->v);

	// We need to return early.
	bc_vec_push(vec, &r.d);
	bc_vec_pop(&p->results);

	BC_SIG_UNLOCK;
	return;
	}
	else if (ref_size && t != BC_TYPE_REF) v = bc_program_dereference(p, v);
	#endif // BC_ENABLED

	bc_array_init(rv, true);
	bc_array_copy(rv, v);
	}

	bc_vec_push(vec, &r.d);
	bc_vec_pop(&p->results);

	BC_SIG_UNLOCK;
	}

	static void bc_program_assign(BcProgram *p, uchar inst) {

	BcResult left, right, res;
	BcNum l, r;
	bool ob, sc, use_val = BC_INST_USE_VAL(inst);

	bc_program_assignPrep(p, &left, &l, &right, &r);

	#if DC_ENABLED
	assert(left->t != BC_RESULT_STR);

	if (right->t == BC_RESULT_STR \|\| BC_PROG_STR(r)) {

	size_t idx = right->t == BC_RESULT_STR ? right->d.loc.loc : r->scale;

	if (left->t == BC_RESULT_ARRAY_ELEM) {
	BC_SIG_LOCK;
	bc_num_free(l);
	bc_num_clear(l);
	l->scale = idx;
	bc_vec_npop(&p->results, 2);
	BC_SIG_UNLOCK;
	}
	else {
	BcVec *v = bc_program_vec(p, left->d.loc.loc, BC_TYPE_VAR);
	bc_program_assignStr(p, idx, v, false);
	}

	return;
	}
	#endif // DC_ENABLED

	if (BC_INST_IS_ASSIGN(inst)) bc_num_copy(l, r);
	#if BC_ENABLED
	else {

	BcBigDig scale = BC_PROG_SCALE(p);

	if (!use_val)
	inst -= (BC_INST_ASSIGN_POWER_NO_VAL - BC_INST_ASSIGN_POWER);

	assert(BC_NUM_RDX_VALID(l));
	assert(BC_NUM_RDX_VALID(r));

	bc_program_ops[inst - BC_INST_ASSIGN_POWER](l, r, l, scale);
	}
	#endif // BC_ENABLED

	ob = (left->t == BC_RESULT_OBASE);
	sc = (left->t == BC_RESULT_SCALE);

	if (ob \|\| sc \|\| left->t == BC_RESULT_IBASE) {

	BcVec *v;
	BcBigDig ptr, ptr_t, val, max, min;
	BcErr e;

	bc_num_bigdig(l, &val);
	e = left->t - BC_RESULT_IBASE + BC_ERR_EXEC_IBASE;

	if (sc) {
	min = 0;
	max = vm.maxes[BC_PROG_GLOBALS_SCALE];
	v = p->globals_v + BC_PROG_GLOBALS_SCALE;
	ptr_t = p->globals + BC_PROG_GLOBALS_SCALE;
	}
	else {
	min = BC_NUM_MIN_BASE;
	if (BC_ENABLE_EXTRA_MATH && ob && (BC_IS_DC \|\| !BC_IS_POSIX))
	min = 0;
	max = vm.maxes[ob + BC_PROG_GLOBALS_IBASE];
	v = p->globals_v + BC_PROG_GLOBALS_IBASE + ob;
	ptr_t = p->globals + BC_PROG_GLOBALS_IBASE + ob;
	}

	if (BC_ERR(val > max \|\| val < min)) bc_vm_verr(e, min, max);

	ptr = bc_vec_top(v);
	*ptr = val;
	*ptr_t = val;
	}
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	else if (left->t == BC_RESULT_SEED) bc_num_rng(l, &p->rng);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	BC_SIG_LOCK;

	if (use_val) {
	bc_num_createCopy(&res.d.n, l);
	res.t = BC_RESULT_TEMP;
	bc_vec_npop(&p->results, 2);
	bc_vec_push(&p->results, &res);
	}
	else bc_vec_npop(&p->results, 2);

	BC_SIG_UNLOCK;
	}

	static void bc_program_pushVar(BcProgram p, const char restrict code,
	size_t *restrict bgn, bool pop, bool copy)
	{
	BcResult r;
	size_t idx = bc_program_index(code, bgn);

	r.t = BC_RESULT_VAR;
	r.d.loc.loc = idx;

	#if DC_ENABLED
	if (BC_IS_DC && (pop \|\| copy)) {

	BcVec *v = bc_program_vec(p, idx, BC_TYPE_VAR);
	BcNum *num = bc_vec_top(v);

	if (BC_ERR(!BC_PROG_STACK(v, 2 - copy))) bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(v, 2 - copy));

	if (!BC_PROG_STR(num)) {

	BC_SIG_LOCK;

	r.t = BC_RESULT_TEMP;
	bc_num_createCopy(&r.d.n, num);

	if (!copy) bc_vec_pop(v);

	bc_vec_push(&p->results, &r);

	BC_SIG_UNLOCK;

	return;
	}
	else {
	r.d.loc.loc = num->scale;
	r.t = BC_RESULT_STR;
	}

	if (!copy) bc_vec_pop(v);
	}
	#endif // DC_ENABLED

	bc_vec_push(&p->results, &r);
	}

	static void bc_program_pushArray(BcProgram p, const char restrict code,
	size_t *restrict bgn, uchar inst)
	{
	BcResult r, *operand;
	BcNum *num;
	BcBigDig temp;

	r.d.loc.loc = bc_program_index(code, bgn);

	#if BC_ENABLED
	if (inst == BC_INST_ARRAY) {
	r.t = BC_RESULT_ARRAY;
	bc_vec_push(&p->results, &r);
	return;
	}
	#endif // BC_ENABLED

	bc_program_prep(p, &operand, &num, 0);
	bc_num_bigdig(num, &temp);

	r.t = BC_RESULT_ARRAY_ELEM;
	r.d.loc.idx = (size_t) temp;

	BC_SIG_LOCK;

	bc_vec_pop(&p->results);
	bc_vec_push(&p->results, &r);

	BC_SIG_UNLOCK;
	}

	#if BC_ENABLED
	static void bc_program_incdec(BcProgram *p, uchar inst) {

	BcResult *ptr, res, copy;
	BcNum *num;
	uchar inst2;

	bc_program_prep(p, &ptr, &num, 0);

	BC_SIG_LOCK;

	copy.t = BC_RESULT_TEMP;
	bc_num_createCopy(&copy.d.n, num);

	BC_SETJMP_LOCKED(exit);

	BC_SIG_UNLOCK;

	res.t = BC_RESULT_ONE;
	inst2 = BC_INST_ASSIGN_PLUS + (inst & 0x01);

	bc_vec_push(&p->results, &res);
	bc_program_assign(p, inst2);

	BC_SIG_LOCK;

	bc_vec_pop(&p->results);
	bc_vec_push(&p->results, &copy);

	BC_UNSETJMP;

	BC_SIG_UNLOCK;

	return;

	exit:
	BC_SIG_MAYLOCK;
	bc_num_free(&copy.d.n);
	BC_LONGJMP_CONT;
	}

	static void bc_program_call(BcProgram p, const char restrict code,
	size_t *restrict idx)
	{
	BcInstPtr ip;
	size_t i, nparams = bc_program_index(code, idx);
	BcFunc *f;
	BcVec *v;
	BcLoc *a;
	BcResultData param;
	BcResult *arg;

	ip.idx = 0;
	ip.func = bc_program_index(code, idx);
	f = bc_vec_item(&p->fns, ip.func);

	if (BC_ERR(!f->code.len)) bc_vm_verr(BC_ERR_EXEC_UNDEF_FUNC, f->name);
	if (BC_ERR(nparams != f->nparams))
	bc_vm_verr(BC_ERR_EXEC_PARAMS, f->nparams, nparams);
	ip.len = p->results.len - nparams;

	assert(BC_PROG_STACK(&p->results, nparams));

	if (BC_G) bc_program_prepGlobals(p);

	for (i = 0; i < nparams; ++i) {

	size_t j;
	bool last = true;

	arg = bc_vec_top(&p->results);
	if (BC_ERR(arg->t == BC_RESULT_VOID)) bc_vm_err(BC_ERR_EXEC_VOID_VAL);

	a = bc_vec_item(&f->autos, nparams - 1 - i);

	// If I have already pushed to a var, I need to make sure I
	// get the previous version, not the already pushed one.
	if (arg->t == BC_RESULT_VAR \|\| arg->t == BC_RESULT_ARRAY) {
	for (j = 0; j < i && last; ++j) {
	BcLoc *loc = bc_vec_item(&f->autos, nparams - 1 - j);
	last = (arg->d.loc.loc != loc->loc \|\|
	(!loc->idx) != (arg->t == BC_RESULT_VAR));
	}
	}

	bc_program_copyToVar(p, a->loc, (BcType) a->idx, last);
	}

	BC_SIG_LOCK;

	for (; i < f->autos.len; ++i) {

	a = bc_vec_item(&f->autos, i);
	v = bc_program_vec(p, a->loc, (BcType) a->idx);

	if (a->idx == BC_TYPE_VAR) {
	bc_num_init(&param.n, BC_NUM_DEF_SIZE);
	bc_vec_push(v, &param.n);
	}
	else {
	assert(a->idx == BC_TYPE_ARRAY);
	bc_array_init(&param.v, true);
	bc_vec_push(v, &param.v);
	}
	}

	bc_vec_push(&p->stack, &ip);

	BC_SIG_UNLOCK;
	}

	static void bc_program_return(BcProgram *p, uchar inst) {

	BcResult *res;
	BcFunc *f;
	BcInstPtr *ip = bc_vec_top(&p->stack);
	size_t i, nops = p->results.len - ip->len;

	assert(BC_PROG_STACK(&p->stack, 2));
	assert(BC_PROG_STACK(&p->results, ip->len + (inst == BC_INST_RET)));

	f = bc_vec_item(&p->fns, ip->func);
	res = bc_program_prepResult(p);

	if (inst == BC_INST_RET) {

	BcNum *num;
	BcResult *operand;

	bc_program_operand(p, &operand, &num, 1);

	BC_SIG_LOCK;

	bc_num_createCopy(&res->d.n, num);
	}
	else if (inst == BC_INST_RET_VOID) res->t = BC_RESULT_VOID;
	else {
	BC_SIG_LOCK;
	bc_num_init(&res->d.n, BC_NUM_DEF_SIZE);
	}

	BC_SIG_MAYUNLOCK;

	// We need to pop arguments as well, so this takes that into account.
	for (i = 0; i < f->autos.len; ++i) {

	BcLoc *a = bc_vec_item(&f->autos, i);
	BcVec *v = bc_program_vec(p, a->loc, (BcType) a->idx);

	bc_vec_pop(v);
	}

	bc_program_retire(p, 1, nops);

	if (BC_G) bc_program_popGlobals(p, false);

	bc_vec_pop(&p->stack);
	}
	#endif // BC_ENABLED

	static void bc_program_builtin(BcProgram *p, uchar inst) {

	BcResult opd, res;
	BcNum *num;
	bool len = (inst == BC_INST_LENGTH);

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	assert(inst >= BC_INST_LENGTH && inst <= BC_INST_IRAND);
	#else // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	assert(inst >= BC_INST_LENGTH && inst <= BC_INST_ABS);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	#ifndef BC_PROG_NO_STACK_CHECK
	if (BC_IS_DC) {
	if (BC_ERR(!BC_PROG_STACK(&p->results, 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);
	}
	#endif // BC_PROG_NO_STACK_CHECK

	assert(BC_PROG_STACK(&p->results, 1));

	res = bc_program_prepResult(p);

	bc_program_operand(p, &opd, &num, 1);

	assert(num != NULL);

	#if DC_ENABLED
	if (!len && inst != BC_INST_SCALE_FUNC) bc_program_type_num(opd, num);
	#endif // DC_ENABLED

	if (inst == BC_INST_SQRT) bc_num_sqrt(num, &res->d.n, BC_PROG_SCALE(p));
	else if (inst == BC_INST_ABS) {

	BC_SIG_LOCK;

	bc_num_createCopy(&res->d.n, num);

	BC_SIG_UNLOCK;

	BC_NUM_NEG_CLR_NP(res->d.n);
	}
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	else if (inst == BC_INST_IRAND) {

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, num->len - num->rdx);

	BC_SIG_UNLOCK;

	bc_num_irand(num, &res->d.n, &p->rng);
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	else {

	BcBigDig val = 0;

	if (len) {
	#if BC_ENABLED
	if (BC_IS_BC && opd->t == BC_RESULT_ARRAY) {

	BcVec v = (BcVec) num;

	if (v->size == sizeof(uchar)) v = bc_program_dereference(p, v);

	assert(v->size == sizeof(BcNum));

	val = (BcBigDig) v->len;
	}
	else
	#endif // BC_ENABLED
	{
	#if DC_ENABLED
	if (!BC_PROG_NUM(opd, num)) {

	size_t idx;
	char *str;

	idx = opd->t == BC_RESULT_STR ? opd->d.loc.loc : num->scale;
	str = ((char*) bc_vec_item(p->strs, idx));
	val = (BcBigDig) strlen(str);
	}
	else
	#endif // DC_ENABLED
	{
	val = (BcBigDig) bc_num_len(num);
	}
	}
	}
	else if (BC_IS_BC \|\| BC_PROG_NUM(opd, num))
	val = (BcBigDig) bc_num_scale(num);

	BC_SIG_LOCK;

	bc_num_createFromBigdig(&res->d.n, val);

	BC_SIG_UNLOCK;
	}

	bc_program_retire(p, 1, 1);
	}

	#if DC_ENABLED
	static void bc_program_divmod(BcProgram *p) {

	BcResult opd1, opd2, res, res2;
	BcNum n1, n2;
	size_t req;

	bc_vec_grow(&p->results, 2);

	// We don't need to update the pointer because
	// the capacity is enough due to the line above.
	res2 = bc_program_prepResult(p);
	res = bc_program_prepResult(p);

	bc_program_binOpPrep(p, &opd1, &n1, &opd2, &n2, 2);

	req = bc_num_mulReq(n1, n2, BC_PROG_SCALE(p));

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, req);
	bc_num_init(&res2->d.n, req);

	BC_SIG_UNLOCK;

	bc_num_divmod(n1, n2, &res2->d.n, &res->d.n, BC_PROG_SCALE(p));

	bc_program_retire(p, 2, 2);
	}

	static void bc_program_modexp(BcProgram *p) {

	BcResult r1, r2, r3, res;
	BcNum n1, n2, *n3;

	if (BC_ERR(!BC_PROG_STACK(&p->results, 3))) bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 3));

	res = bc_program_prepResult(p);

	bc_program_operand(p, &r1, &n1, 3);
	bc_program_type_num(r1, n1);

	bc_program_binOpPrep(p, &r2, &n2, &r3, &n3, 1);

	// Make sure that the values have their pointers updated, if necessary.
	// Only array elements are possible.
	if (r1->t == BC_RESULT_ARRAY_ELEM && (r1->t == r2->t \|\| r1->t == r3->t))
	n1 = bc_program_num(p, r1);

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, n3->len);

	BC_SIG_UNLOCK;

	bc_num_modexp(n1, n2, n3, &res->d.n);

	bc_program_retire(p, 1, 3);
	}

	static void bc_program_stackLen(BcProgram *p) {
	bc_program_pushBigdig(p, (BcBigDig) p->results.len, BC_RESULT_TEMP);
	}

	static uchar bc_program_asciifyNum(BcProgram p, BcNum n) {

	BcNum num;
	BcBigDig val = 0;

	bc_num_clear(&num);

	BC_SETJMP(num_err);

	BC_SIG_LOCK;

	bc_num_createCopy(&num, n);

	BC_SIG_UNLOCK;

	bc_num_truncate(&num, num.scale);
	BC_NUM_NEG_CLR_NP(num);

	// This is guaranteed to not have a divide by 0
	// because strmb is equal to UCHAR_MAX + 1.
	bc_num_mod(&num, &p->strmb, &num, 0);

	// This is also guaranteed to not error because num is in the range
	// [0, UCHAR_MAX], which is definitely in range for a BcBigDig. And
	// it is not negative.
	bc_num_bigdig2(&num, &val);

	num_err:
	BC_SIG_MAYLOCK;
	bc_num_free(&num);
	BC_LONGJMP_CONT;
	return (uchar) val;
	}

	static void bc_program_asciify(BcProgram *p) {

	BcResult *r, res;
	BcNum *n;
	char str[2], *str2;
	uchar c;
	size_t idx;

	if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 1));

	bc_program_operand(p, &r, &n, 0);

	assert(n != NULL);

	assert(p->strs->len + BC_PROG_REQ_FUNCS == p->fns.len);

	if (BC_PROG_NUM(r, n)) c = bc_program_asciifyNum(p, n);
	else {
	size_t index = r->t == BC_RESULT_STR ? r->d.loc.loc : n->scale;
	str2 = ((char*) bc_vec_item(p->strs, index));
	c = (uchar) str2[0];
	}

	str[0] = (char) c;
	str[1] = '\0';

	BC_SIG_LOCK;

	idx = bc_program_insertFunc(p, str) - BC_PROG_REQ_FUNCS;

	BC_SIG_UNLOCK;

	res.t = BC_RESULT_STR;
	res.d.loc.loc = idx;
	bc_vec_pop(&p->results);
	bc_vec_push(&p->results, &res);
	}

	static void bc_program_printStream(BcProgram *p) {

	BcResult *r;
	BcNum *n;

	if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 1));

	bc_program_operand(p, &r, &n, 0);

	assert(n != NULL);

	if (BC_PROG_NUM(r, n)) bc_num_stream(n, p->strm);
	else {
	size_t idx = (r->t == BC_RESULT_STR) ? r->d.loc.loc : n->scale;
	bc_program_printChars(((char*) bc_vec_item(p->strs, idx)));
	}
	+
	+ bc_vec_pop(&p->results);
	}

	static void bc_program_nquit(BcProgram *p, uchar inst) {

	BcResult *opnd;
	BcNum *num;
	BcBigDig val;
	size_t i;

	assert(p->stack.len == p->tail_calls.len);

	if (inst == BC_INST_QUIT) val = 2;
	else {

	bc_program_prep(p, &opnd, &num, 0);
	bc_num_bigdig(num, &val);

	bc_vec_pop(&p->results);
	}

	for (i = 0; val && i < p->tail_calls.len; ++i) {
	size_t calls = ((size_t) bc_vec_item_rev(&p->tail_calls, i)) + 1;
	if (calls >= val) val = 0;
	- else val -= calls;
	+ else val -= (BcBigDig) calls;
	}

	if (i == p->stack.len) {
	vm.status = BC_STATUS_QUIT;
	BC_VM_JMP;
	}
	else {
	bc_vec_npop(&p->stack, i);
	bc_vec_npop(&p->tail_calls, i);
	}
	}

	static void bc_program_execStr(BcProgram p, const char restrict code,
	size_t *restrict bgn, bool cond, size_t len)
	{
	BcResult *r;
	char *str;
	BcFunc *f;
	BcParse prs;
	BcInstPtr ip;
	size_t fidx, sidx;
	BcNum *n;

	assert(p->stack.len == p->tail_calls.len);

	if (BC_ERR(!BC_PROG_STACK(&p->results, 1))) bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 1));

	bc_program_operand(p, &r, &n, 0);

	if (cond) {

	bool exec;
	size_t idx, then_idx, else_idx;

	then_idx = bc_program_index(code, bgn);
	else_idx = bc_program_index(code, bgn);

	exec = (r->d.n.len != 0);

	idx = exec ? then_idx : else_idx;

	BC_SIG_LOCK;
	BC_SETJMP_LOCKED(exit);

	if (exec \|\| (else_idx != SIZE_MAX))
	n = bc_vec_top(bc_program_vec(p, idx, BC_TYPE_VAR));
	else goto exit;

	if (BC_ERR(!BC_PROG_STR(n))) bc_vm_err(BC_ERR_EXEC_TYPE);

	BC_UNSETJMP;
	BC_SIG_UNLOCK;

	sidx = n->scale;
	}
	else {

	// In non-conditional situations, only the top of stack can be executed,
	// and in those cases, variables are not allowed to be "on the stack";
	// they are only put on the stack to be assigned to.
	assert(r->t != BC_RESULT_VAR);

	if (r->t == BC_RESULT_STR) sidx = r->d.loc.loc;
	else return;
	}

	fidx = sidx + BC_PROG_REQ_FUNCS;
	str = ((char*) bc_vec_item(p->strs, sidx));
	f = bc_vec_item(&p->fns, fidx);

	if (!f->code.len) {

	BC_SIG_LOCK;

	bc_parse_init(&prs, p, fidx);
	bc_lex_file(&prs.l, vm.file);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_parse_text(&prs, str);
	vm.expr(&prs, BC_PARSE_NOCALL);

	BC_SIG_LOCK;

	BC_UNSETJMP;

	// We can just assert this here because
	// dc should parse everything until EOF.
	assert(prs.l.t == BC_LEX_EOF);

	bc_parse_free(&prs);

	BC_SIG_UNLOCK;
	}

	ip.idx = 0;
	ip.len = p->results.len;
	ip.func = fidx;

	bc_vec_pop(&p->results);

	// Tail call.
	if (p->stack.len > 1 && bgn == len - 1 && code[bgn] == BC_INST_POP_EXEC) {
	size_t *call_ptr = bc_vec_top(&p->tail_calls);
	*call_ptr += 1;
	bc_vec_pop(&p->stack);
	}
	else bc_vec_push(&p->tail_calls, &ip.idx);

	bc_vec_push(&p->stack, &ip);

	return;

	err:
	BC_SIG_MAYLOCK;
	bc_parse_free(&prs);
	f = bc_vec_item(&p->fns, fidx);
	bc_vec_popAll(&f->code);
	exit:
	bc_vec_pop(&p->results);
	BC_LONGJMP_CONT;
	}

	static void bc_program_printStack(BcProgram *p) {

	size_t idx;

	for (idx = 0; idx < p->results.len; ++idx)
	bc_program_print(p, BC_INST_PRINT, idx);
	}
	#endif // DC_ENABLED

	static void bc_program_pushGlobal(BcProgram *p, uchar inst) {

	BcResultType t;

	assert(inst >= BC_INST_IBASE && inst <= BC_INST_SCALE);

	t = inst - BC_INST_IBASE + BC_RESULT_IBASE;
	bc_program_pushBigdig(p, p->globals[inst - BC_INST_IBASE], t);
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	static void bc_program_pushSeed(BcProgram *p) {

	BcResult *res;

	res = bc_program_prepResult(p);
	res->t = BC_RESULT_SEED;

	BC_SIG_LOCK;

	bc_num_init(&res->d.n, 2 * BC_RAND_NUM_SIZE);

	BC_SIG_UNLOCK;

	bc_num_createFromRNG(&res->d.n, &p->rng);
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	static void bc_program_addFunc(BcProgram p, BcFunc f, BcId *id_ptr) {

	BcInstPtr *ip;

	BC_SIG_ASSERT_LOCKED;

	bc_func_init(f, id_ptr->name);
	bc_vec_push(&p->fns, f);

	// This is to make sure pointers are updated if the array was moved.
	if (p->stack.len) {
	ip = bc_vec_top(&p->stack);
	bc_program_setVecs(p, (BcFunc*) bc_vec_item(&p->fns, ip->func));
	}
	}

	size_t bc_program_insertFunc(BcProgram p, const char name) {

	BcId *id_ptr;
	BcFunc f;
	bool new;
	size_t idx;

	BC_SIG_ASSERT_LOCKED;

	assert(p != NULL && name != NULL);

	new = bc_map_insert(&p->fn_map, name, p->fns.len, &idx);
	id_ptr = (BcId*) bc_vec_item(&p->fn_map, idx);
	idx = id_ptr->idx;

	if (!new) {
	if (BC_IS_BC) {
	BcFunc *func = bc_vec_item(&p->fns, idx);
	bc_func_reset(func);
	}
	}
	else {

	bc_program_addFunc(p, &f, id_ptr);

	#if DC_ENABLED
	if (BC_IS_DC && idx >= BC_PROG_REQ_FUNCS) {
	bc_vec_push(p->strs, &id_ptr->name);
	assert(p->strs->len == p->fns.len - BC_PROG_REQ_FUNCS);
	}
	#endif // DC_ENABLED
	}

	return idx;
	}

	#ifndef NDEBUG
	void bc_program_free(BcProgram *p) {

	size_t i;

	BC_SIG_ASSERT_LOCKED;

	assert(p != NULL);

	for (i = 0; i < BC_PROG_GLOBALS_LEN; ++i) bc_vec_free(p->globals_v + i);

	bc_vec_free(&p->fns);
	bc_vec_free(&p->fn_map);
	bc_vec_free(&p->vars);
	bc_vec_free(&p->var_map);
	bc_vec_free(&p->arrs);
	bc_vec_free(&p->arr_map);
	bc_vec_free(&p->results);
	bc_vec_free(&p->stack);

	#if BC_ENABLED
	if (BC_IS_BC) bc_num_free(&p->last);
	#endif // BC_ENABLED

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	bc_rand_free(&p->rng);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	#if DC_ENABLED
	if (BC_IS_DC) {
	bc_vec_free(&p->tail_calls);
	bc_vec_free(&p->strs_v);
	}
	#endif // DC_ENABLED
	}
	#endif // NDEBUG

	void bc_program_init(BcProgram *p) {

	BcInstPtr ip;
	size_t i;

	BC_SIG_ASSERT_LOCKED;

	assert(p != NULL);

	memset(p, 0, sizeof(BcProgram));
	memset(&ip, 0, sizeof(BcInstPtr));

	for (i = 0; i < BC_PROG_GLOBALS_LEN; ++i) {
	BcBigDig val = i == BC_PROG_GLOBALS_SCALE ? 0 : BC_BASE;
	bc_vec_init(p->globals_v + i, sizeof(BcBigDig), NULL);
	bc_vec_push(p->globals_v + i, &val);
	p->globals[i] = val;
	}

	#if DC_ENABLED
	if (BC_IS_DC) {

	bc_vec_init(&p->strs_v, sizeof(char*), bc_string_free);
	p->strs = &p->strs_v;

	bc_vec_init(&p->tail_calls, sizeof(size_t), NULL);
	i = 0;
	bc_vec_push(&p->tail_calls, &i);

	p->strm = UCHAR_MAX + 1;
	bc_num_setup(&p->strmb, p->strmb_num, BC_NUM_BIGDIG_LOG10);
	bc_num_bigdig2num(&p->strmb, p->strm);
	}
	#endif // DC_ENABLED

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	srand((unsigned int) time(NULL));
	bc_rand_init(&p->rng);
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	bc_num_setup(&p->zero, p->zero_num, BC_PROG_ONE_CAP);

	bc_num_setup(&p->one, p->one_num, BC_PROG_ONE_CAP);
	bc_num_one(&p->one);

	#if BC_ENABLED
	if (BC_IS_BC) bc_num_init(&p->last, BC_NUM_DEF_SIZE);
	#endif // BC_ENABLED

	bc_vec_init(&p->fns, sizeof(BcFunc), bc_func_free);
	bc_map_init(&p->fn_map);
	bc_program_insertFunc(p, bc_func_main);
	bc_program_insertFunc(p, bc_func_read);

	bc_vec_init(&p->vars, sizeof(BcVec), bc_vec_free);
	bc_map_init(&p->var_map);

	bc_vec_init(&p->arrs, sizeof(BcVec), bc_vec_free);
	bc_map_init(&p->arr_map);

	bc_vec_init(&p->results, sizeof(BcResult), bc_result_free);
	bc_vec_init(&p->stack, sizeof(BcInstPtr), NULL);
	bc_vec_push(&p->stack, &ip);

	bc_program_setVecs(p, (BcFunc*) bc_vec_item(&p->fns, BC_PROG_MAIN));

	assert(p->consts != NULL && p->strs != NULL);
	}

	void bc_program_reset(BcProgram *p) {

	BcFunc *f;
	BcInstPtr *ip;

	BC_SIG_ASSERT_LOCKED;

	bc_vec_npop(&p->stack, p->stack.len - 1);
	bc_vec_popAll(&p->results);

	#if BC_ENABLED
	if (BC_G) bc_program_popGlobals(p, true);
	#endif // BC_ENABLED

	f = bc_vec_item(&p->fns, BC_PROG_MAIN);
	bc_vec_npop(&f->code, f->code.len);
	ip = bc_vec_top(&p->stack);
	bc_program_setVecs(p, f);
	memset(ip, 0, sizeof(BcInstPtr));

	if (vm.sig) {
	- bc_file_write(&vm.fout, bc_program_ready_msg, bc_program_ready_msg_len);
	- bc_file_flush(&vm.fout);
	+ bc_file_write(&vm.fout, bc_flush_none, bc_program_ready_msg,
	+ bc_program_ready_msg_len);
	+ bc_file_flush(&vm.fout, bc_flush_err);
	vm.sig = 0;
	}
	}

	void bc_program_exec(BcProgram *p) {

	size_t idx;
	BcResult r, *ptr;
	BcInstPtr *ip = bc_vec_top(&p->stack);
	BcFunc func = (BcFunc) bc_vec_item(&p->fns, ip->func);
	char *code = func->code.v;
	bool cond = false;
	#if BC_ENABLED
	BcNum *num;
	#endif // BC_ENABLED
	#ifndef NDEBUG
	size_t jmp_bufs_len;
	#endif // NDEBUG

	#ifndef NDEBUG
	jmp_bufs_len = vm.jmp_bufs.len;
	#endif // NDEBUG

	bc_program_setVecs(p, func);

	while (ip->idx < func->code.len) {

	BC_SIG_ASSERT_NOT_LOCKED;

	uchar inst = (uchar) code[(ip->idx)++];

	switch (inst) {

	#if BC_ENABLED
	case BC_INST_JUMP_ZERO:
	{
	bc_program_prep(p, &ptr, &num, 0);
	cond = !bc_num_cmpZero(num);
	bc_vec_pop(&p->results);
	}
	// Fallthrough.
	BC_FALLTHROUGH

	case BC_INST_JUMP:
	{
	idx = bc_program_index(code, &ip->idx);

	if (inst == BC_INST_JUMP \|\| cond) {

	size_t *addr = bc_vec_item(&func->labels, idx);

	assert(*addr != SIZE_MAX);

	ip->idx = *addr;
	}

	break;
	}

	case BC_INST_CALL:
	{
	assert(BC_IS_BC);

	bc_program_call(p, code, &ip->idx);

	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;

	bc_program_setVecs(p, func);

	break;
	}

	case BC_INST_INC:
	case BC_INST_DEC:
	{
	bc_program_incdec(p, inst);
	break;
	}

	case BC_INST_HALT:
	{
	vm.status = BC_STATUS_QUIT;
	BC_VM_JMP;
	break;
	}

	case BC_INST_RET:
	case BC_INST_RET0:
	case BC_INST_RET_VOID:
	{
	bc_program_return(p, inst);

	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;

	bc_program_setVecs(p, func);

	break;
	}
	#endif // BC_ENABLED

	case BC_INST_BOOL_OR:
	case BC_INST_BOOL_AND:
	case BC_INST_REL_EQ:
	case BC_INST_REL_LE:
	case BC_INST_REL_GE:
	case BC_INST_REL_NE:
	case BC_INST_REL_LT:
	case BC_INST_REL_GT:
	{
	bc_program_logical(p, inst);
	break;
	}

	case BC_INST_READ:
	{
	// We want to flush output before
	// this in case there is a prompt.
	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_save);

	bc_program_read(p);

	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;

	bc_program_setVecs(p, func);

	break;
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	case BC_INST_RAND:
	{
	bc_program_rand(p);
	break;
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	case BC_INST_MAXIBASE:
	case BC_INST_MAXOBASE:
	case BC_INST_MAXSCALE:
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	case BC_INST_MAXRAND:
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	{
	BcBigDig dig = vm.maxes[inst - BC_INST_MAXIBASE];
	bc_program_pushBigdig(p, dig, BC_RESULT_TEMP);
	break;
	}

	case BC_INST_VAR:
	{
	bc_program_pushVar(p, code, &ip->idx, false, false);
	break;
	}

	case BC_INST_ARRAY_ELEM:
	#if BC_ENABLED
	case BC_INST_ARRAY:
	#endif // BC_ENABLED
	{
	bc_program_pushArray(p, code, &ip->idx, inst);
	break;
	}

	case BC_INST_IBASE:
	case BC_INST_SCALE:
	case BC_INST_OBASE:
	{
	bc_program_pushGlobal(p, inst);
	break;
	}

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	case BC_INST_SEED:
	{
	bc_program_pushSeed(p);
	break;
	}
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	case BC_INST_LENGTH:
	case BC_INST_SCALE_FUNC:
	case BC_INST_SQRT:
	case BC_INST_ABS:
	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	case BC_INST_IRAND:
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	{
	bc_program_builtin(p, inst);
	break;
	}

	case BC_INST_NUM:
	{
	bc_program_const(p, code, &ip->idx);
	break;
	}

	case BC_INST_ZERO:
	case BC_INST_ONE:
	#if BC_ENABLED
	case BC_INST_LAST:
	#endif // BC_ENABLED
	{
	r.t = BC_RESULT_ZERO + (inst - BC_INST_ZERO);
	bc_vec_push(&p->results, &r);
	break;
	}

	case BC_INST_PRINT:
	case BC_INST_PRINT_POP:
	case BC_INST_PRINT_STR:
	{
	bc_program_print(p, inst, 0);
	break;
	}

	case BC_INST_STR:
	{
	r.t = BC_RESULT_STR;
	r.d.loc.loc = bc_program_index(code, &ip->idx);
	bc_vec_push(&p->results, &r);
	break;
	}

	case BC_INST_POWER:
	case BC_INST_MULTIPLY:
	case BC_INST_DIVIDE:
	case BC_INST_MODULUS:
	case BC_INST_PLUS:
	case BC_INST_MINUS:
	#if BC_ENABLE_EXTRA_MATH
	case BC_INST_PLACES:
	case BC_INST_LSHIFT:
	case BC_INST_RSHIFT:
	#endif // BC_ENABLE_EXTRA_MATH
	{
	bc_program_op(p, inst);
	break;
	}

	case BC_INST_NEG:
	case BC_INST_BOOL_NOT:
	#if BC_ENABLE_EXTRA_MATH
	case BC_INST_TRUNC:
	#endif // BC_ENABLE_EXTRA_MATH
	{
	bc_program_unary(p, inst);
	break;
	}

	#if BC_ENABLED
	case BC_INST_ASSIGN_POWER:
	case BC_INST_ASSIGN_MULTIPLY:
	case BC_INST_ASSIGN_DIVIDE:
	case BC_INST_ASSIGN_MODULUS:
	case BC_INST_ASSIGN_PLUS:
	case BC_INST_ASSIGN_MINUS:
	#if BC_ENABLE_EXTRA_MATH
	case BC_INST_ASSIGN_PLACES:
	case BC_INST_ASSIGN_LSHIFT:
	case BC_INST_ASSIGN_RSHIFT:
	#endif // BC_ENABLE_EXTRA_MATH
	case BC_INST_ASSIGN:
	case BC_INST_ASSIGN_POWER_NO_VAL:
	case BC_INST_ASSIGN_MULTIPLY_NO_VAL:
	case BC_INST_ASSIGN_DIVIDE_NO_VAL:
	case BC_INST_ASSIGN_MODULUS_NO_VAL:
	case BC_INST_ASSIGN_PLUS_NO_VAL:
	case BC_INST_ASSIGN_MINUS_NO_VAL:
	#if BC_ENABLE_EXTRA_MATH
	case BC_INST_ASSIGN_PLACES_NO_VAL:
	case BC_INST_ASSIGN_LSHIFT_NO_VAL:
	case BC_INST_ASSIGN_RSHIFT_NO_VAL:
	#endif // BC_ENABLE_EXTRA_MATH
	#endif // BC_ENABLED
	case BC_INST_ASSIGN_NO_VAL:
	{
	bc_program_assign(p, inst);
	break;
	}

	case BC_INST_POP:
	{
	#ifndef BC_PROG_NO_STACK_CHECK
	if (!BC_IS_BC) {
	if (BC_ERR(!BC_PROG_STACK(&p->results, 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);
	}
	#endif // BC_PROG_NO_STACK_CHECK

	assert(BC_PROG_STACK(&p->results, 1));

	bc_vec_pop(&p->results);
	break;
	}

	#if DC_ENABLED
	case BC_INST_POP_EXEC:
	{
	assert(BC_PROG_STACK(&p->stack, 2));
	bc_vec_pop(&p->stack);
	bc_vec_pop(&p->tail_calls);
	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;
	bc_program_setVecs(p, func);
	break;
	}

	case BC_INST_MODEXP:
	{
	bc_program_modexp(p);
	break;
	}

	case BC_INST_DIVMOD:
	{
	bc_program_divmod(p);
	break;
	}

	case BC_INST_EXECUTE:
	case BC_INST_EXEC_COND:
	{
	cond = (inst == BC_INST_EXEC_COND);
	bc_program_execStr(p, code, &ip->idx, cond, func->code.len);
	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;
	bc_program_setVecs(p, func);
	break;
	}

	case BC_INST_PRINT_STACK:
	{
	bc_program_printStack(p);
	break;
	}

	case BC_INST_CLEAR_STACK:
	{
	bc_vec_popAll(&p->results);
	break;
	}

	case BC_INST_STACK_LEN:
	{
	bc_program_stackLen(p);
	break;
	}

	case BC_INST_DUPLICATE:
	{
	if (BC_ERR(!BC_PROG_STACK(&p->results, 1)))
	bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 1));

	ptr = bc_vec_top(&p->results);

	BC_SIG_LOCK;

	bc_result_copy(&r, ptr);
	bc_vec_push(&p->results, &r);

	BC_SIG_UNLOCK;

	break;
	}

	case BC_INST_SWAP:
	{
	BcResult *ptr2;

	if (BC_ERR(!BC_PROG_STACK(&p->results, 2)))
	bc_vm_err(BC_ERR_EXEC_STACK);

	assert(BC_PROG_STACK(&p->results, 2));

	ptr = bc_vec_item_rev(&p->results, 0);
	ptr2 = bc_vec_item_rev(&p->results, 1);
	memcpy(&r, ptr, sizeof(BcResult));
	memcpy(ptr, ptr2, sizeof(BcResult));
	memcpy(ptr2, &r, sizeof(BcResult));

	break;
	}

	case BC_INST_ASCIIFY:
	{
	bc_program_asciify(p);
	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;
	bc_program_setVecs(p, func);
	break;
	}

	case BC_INST_PRINT_STREAM:
	{
	bc_program_printStream(p);
	break;
	}

	case BC_INST_LOAD:
	case BC_INST_PUSH_VAR:
	{
	bool copy = (inst == BC_INST_LOAD);
	bc_program_pushVar(p, code, &ip->idx, true, copy);
	break;
	}

	case BC_INST_PUSH_TO_VAR:
	{
	idx = bc_program_index(code, &ip->idx);
	bc_program_copyToVar(p, idx, BC_TYPE_VAR, true);
	break;
	}

	case BC_INST_QUIT:
	case BC_INST_NQUIT:
	{
	bc_program_nquit(p, inst);
	ip = bc_vec_top(&p->stack);
	func = bc_vec_item(&p->fns, ip->func);
	code = func->code.v;
	bc_program_setVecs(p, func);
	break;
	}
	#endif // DC_ENABLED
	#ifndef NDEBUG
	default:
	{
	abort();
	}
	#endif // NDEBUG
	}

	#ifndef NDEBUG
	// This is to allow me to use a debugger to see the last instruction,
	// which will point to which function was the problem.
	assert(jmp_bufs_len == vm.jmp_bufs.len);
	#endif // NDEBUG
	}
	}

	#if BC_DEBUG_CODE
	#if BC_ENABLED && DC_ENABLED
	void bc_program_printStackDebug(BcProgram *p) {
	- bc_file_puts(&vm.fout, "-------------- Stack ----------\n");
	+ bc_file_puts(&vm.fout, bc_flush_err, "-------------- Stack ----------\n");
	bc_program_printStack(p);
	- bc_file_puts(&vm.fout, "-------------- Stack End ------\n");
	+ bc_file_puts(&vm.fout, bc_flush_err, "-------------- Stack End ------\n");
	}

	static void bc_program_printIndex(const char *restrict code,
	size_t *restrict bgn)
	{
	uchar byte, i, bytes = (uchar) code[(*bgn)++];
	ulong val = 0;

	for (byte = 1, i = 0; byte && i < bytes; ++i) {
	byte = (uchar) code[(*bgn)++];
	if (byte) val \|= ((ulong) byte) << (CHAR_BIT * i);
	}

	bc_vm_printf(" (%lu) ", val);
	}

	static void bc_program_printStr(const BcProgram p, const char restrict code,
	size_t *restrict bgn)
	{
	size_t idx = bc_program_index(code, bgn);
	char *s;

	s = ((char*) bc_vec_item(p->strs, idx));

	bc_vm_printf(" (\"%s\") ", s);
	}

	void bc_program_printInst(const BcProgram p, const char restrict code,
	size_t *restrict bgn)
	{
	uchar inst = (uchar) code[(*bgn)++];

	bc_vm_printf("Inst[%zu]: %s [%lu]; ", *bgn - 1,
	bc_inst_names[inst], (unsigned long) inst);

	if (inst == BC_INST_VAR \|\| inst == BC_INST_ARRAY_ELEM \|\|
	inst == BC_INST_ARRAY)
	{
	bc_program_printIndex(code, bgn);
	}
	else if (inst == BC_INST_STR) bc_program_printStr(p, code, bgn);
	else if (inst == BC_INST_NUM) {
	size_t idx = bc_program_index(code, bgn);
	BcConst *c = bc_vec_item(p->consts, idx);
	bc_vm_printf("(%s)", c->val);
	}
	else if (inst == BC_INST_CALL \|\|
	(inst > BC_INST_STR && inst <= BC_INST_JUMP_ZERO))
	{
	bc_program_printIndex(code, bgn);
	if (inst == BC_INST_CALL) bc_program_printIndex(code, bgn);
	}

	- bc_vm_putchar('\n');
	+ bc_vm_putchar('\n', bc_flush_err);
	}

	void bc_program_code(const BcProgram* p) {

	BcFunc *f;
	char *code;
	BcInstPtr ip;
	size_t i;

	for (i = 0; i < p->fns.len; ++i) {

	ip.idx = ip.len = 0;
	ip.func = i;

	f = bc_vec_item(&p->fns, ip.func);
	code = f->code.v;

	bc_vm_printf("func[%zu]:\n", ip.func);
	while (ip.idx < f->code.len) bc_program_printInst(p, code, &ip.idx);
	- bc_file_puts(&vm.fout, "\n\n");
	+ bc_file_puts(&vm.fout, bc_flush_err, "\n\n");
	}
	}
	#endif // BC_ENABLED && DC_ENABLED
	#endif // BC_DEBUG_CODE
	diff --git a/contrib/bc/src/rand.c b/contrib/bc/src/rand.c
	index 6b2ec7bdb30f..886f7a6bd471 100644
	--- a/contrib/bc/src/rand.c
	+++ b/contrib/bc/src/rand.c
	@@ -1,396 +1,424 @@
	/*
	* *****************************************************************************
	*
	* Parts of this code are adapted from the following:
	*
	* PCG, A Family of Better Random Number Generators.
	*
	* You can find the original source code at:
	* https://github.com/imneme/pcg-c
	*
	* -----------------------------------------------------------------------------
	*
	* This code is under the following license:
	*
	* Copyright (c) 2014-2017 Melissa O'Neill and PCG Project contributors
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Permission is hereby granted, free of charge, to any person obtaining a copy
	* of this software and associated documentation files (the "Software"), to deal
	* in the Software without restriction, including without limitation the rights
	* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
	* copies of the Software, and to permit persons to whom the Software is
	* furnished to do so, subject to the following conditions:
	*
	* The above copyright notice and this permission notice shall be included in
	* all copies or substantial portions of the Software.
	*
	* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
	* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
	* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
	* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
	* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
	* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
	* SOFTWARE.
	*
	* *****************************************************************************
	*
	* Code for the RNG.
	*
	*/

	#include <assert.h>
	#include <stdlib.h>
	#include <string.h>
	#include <time.h>
	#include <fcntl.h>
	+
	+#ifndef _WIN32
	#include <unistd.h>
	+#else // _WIN32
	+#include <Windows.h>
	+#include <bcrypt.h>
	+#endif // _WIN32

	#include <status.h>
	#include <rand.h>
	#include <vm.h>

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	#if !BC_RAND_BUILTIN

	static BcRandState bc_rand_addition(uint_fast64_t a, uint_fast64_t b) {

	BcRandState res;

	res.lo = a + b;
	res.hi = (res.lo < a);

	return res;
	}

	static BcRandState bc_rand_addition2(BcRandState a, BcRandState b) {

	BcRandState temp, res;

	res = bc_rand_addition(a.lo, b.lo);
	temp = bc_rand_addition(a.hi, b.hi);
	res.hi += temp.lo;

	return res;
	}

	static BcRandState bc_rand_multiply(uint_fast64_t a, uint_fast64_t b) {

	uint_fast64_t al, ah, bl, bh, c0, c1, c2, c3;
	BcRandState carry, res;

	al = BC_RAND_TRUNC32(a);
	ah = BC_RAND_CHOP32(a);
	bl = BC_RAND_TRUNC32(b);
	bh = BC_RAND_CHOP32(b);

	c0 = al * bl;
	c1 = al * bh;
	c2 = ah * bl;
	c3 = ah * bh;

	carry = bc_rand_addition(c1, c2);

	res = bc_rand_addition(c0, (BC_RAND_TRUNC32(carry.lo)) << 32);
	res.hi += BC_RAND_CHOP32(carry.lo) + c3 + (carry.hi << 32);

	return res;
	}

	static BcRandState bc_rand_multiply2(BcRandState a, BcRandState b) {

	BcRandState c0, c1, c2, carry;

	c0 = bc_rand_multiply(a.lo, b.lo);
	c1 = bc_rand_multiply(a.lo, b.hi);
	c2 = bc_rand_multiply(a.hi, b.lo);

	carry = bc_rand_addition2(c1, c2);
	carry.hi = carry.lo;
	carry.lo = 0;

	return bc_rand_addition2(c0, carry);
	}

	#endif // BC_RAND_BUILTIN

	static void bc_rand_setModified(BcRNGData *r) {

	#if BC_RAND_BUILTIN
	r->inc \|= (BcRandState) 1UL;
	#else // BC_RAND_BUILTIN
	r->inc.lo \|= (uint_fast64_t) 1UL;
	#endif // BC_RAND_BUILTIN
	}

	static void bc_rand_clearModified(BcRNGData *r) {

	#if BC_RAND_BUILTIN
	r->inc &= ~((BcRandState) 1UL);
	#else // BC_RAND_BUILTIN
	r->inc.lo &= ~(1UL);
	#endif // BC_RAND_BUILTIN
	}

	static void bc_rand_copy(BcRNGData d, BcRNGData s) {
	bool unmod = BC_RAND_NOTMODIFIED(d);
	memcpy(d, s, sizeof(BcRNGData));
	if (!unmod) bc_rand_setModified(d);
	else if (!BC_RAND_NOTMODIFIED(s)) bc_rand_clearModified(d);
	}

	-static ulong bc_rand_frand(void *ptr) {
	+#ifndef _WIN32
	+static ulong bc_rand_frand(void* ptr) {

	ulong buf[1];
	int fd;
	ssize_t nread;

	assert(ptr != NULL);

	- fd = ((int) ptr);
	+ fd = ((int)ptr);

	nread = read(fd, buf, sizeof(ulong));

	if (BC_ERR(nread != sizeof(ulong))) bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);

	- return ((ulong) buf);
	+ return ((ulong)buf);
	}
	+#else // _WIN32
	+static ulong bc_rand_winrand(void* ptr) {
	+
	+ ulong buf[1];
	+ NTSTATUS s;
	+
	+ BC_UNUSED(ptr);
	+
	+ buf[0] = 0;
	+
	+ s = BCryptGenRandom(NULL, (char*) buf, sizeof(ulong), BCRYPT_USE_SYSTEM_PREFERRED_RNG);
	+
	+ if (BC_ERR(!BCRYPT_SUCCESS(s))) buf[0] = 0;
	+
	+ return buf[0];
	+}
	+#endif // _WIN32

	static ulong bc_rand_rand(void *ptr) {

	size_t i;
	ulong res = 0;

	BC_UNUSED(ptr);

	for (i = 0; i < sizeof(ulong); ++i)
	res \|= ((ulong) (rand() & BC_RAND_SRAND_BITS)) << (i * CHAR_BIT);

	return res;
	}

	static BcRandState bc_rand_inc(BcRNGData *r) {

	BcRandState inc;

	#if BC_RAND_BUILTIN
	inc = r->inc \| 1;
	#else // BC_RAND_BUILTIN
	inc.lo = r->inc.lo \| 1;
	inc.hi = r->inc.hi;
	#endif // BC_RAND_BUILTIN

	return inc;
	}

	static void bc_rand_setInc(BcRNGData *r) {

	#if BC_RAND_BUILTIN
	r->inc <<= 1UL;
	#else // BC_RAND_BUILTIN
	r->inc.hi <<= 1UL;
	r->inc.hi \|= (r->inc.lo & (1UL << (BC_LONG_BIT - 1))) >> (BC_LONG_BIT - 1);
	r->inc.lo <<= 1UL;
	#endif // BC_RAND_BUILTIN
	}

	static void bc_rand_seedState(BcRandState *state, ulong val1, ulong val2) {

	#if BC_RAND_BUILTIN
	*state = ((BcRandState) val1) \| ((BcRandState) val2) << (BC_LONG_BIT);
	#else // BC_RAND_BUILTIN
	state->lo = val1;
	state->hi = val2;
	#endif // BC_RAND_BUILTIN
	}

	static void bc_rand_seedRNG(BcRNGData *r, ulong state1, ulong state2,
	ulong inc1, ulong inc2)
	{
	bc_rand_seedState(&r->state, state1, state2);
	bc_rand_seedState(&r->inc, inc1, inc2);
	bc_rand_setInc(r);
	}

	static void bc_rand_fill(BcRNGData r, BcRandUlong fulong, void ptr) {

	ulong state1, state2, inc1, inc2;

	state1 = fulong(ptr);
	state2 = fulong(ptr);

	inc1 = fulong(ptr);
	inc2 = fulong(ptr);

	bc_rand_seedRNG(r, state1, state2, inc1, inc2);
	}

	static void bc_rand_step(BcRNGData *r) {
	BcRandState temp = bc_rand_mul2(r->state, bc_rand_multiplier);
	r->state = bc_rand_add2(temp, bc_rand_inc(r));
	}

	static BcRand bc_rand_output(BcRNGData *r) {
	return BC_RAND_ROT(BC_RAND_FOLD(r->state), BC_RAND_ROTAMT(r->state));
	}

	static void bc_rand_seedZeroes(BcRNG r, BcRNGData rng, size_t idx) {

	BcRNGData *rng2;

	if (r->v.len <= idx) return;

	rng2 = bc_vec_item_rev(&r->v, idx);

	if (BC_RAND_ZERO(rng2)) {
	size_t i;
	for (i = 1; i < r->v.len; ++i)
	bc_rand_copy(bc_vec_item_rev(&r->v, i), rng);
	}
	}

	void bc_rand_srand(BcRNGData *rng) {

	- int fd;
	+ int fd = 0;

	BC_SIG_LOCK;

	+#ifndef _WIN32
	fd = open("/dev/urandom", O_RDONLY);

	if (BC_NO_ERR(fd >= 0)) {
	bc_rand_fill(rng, bc_rand_frand, &fd);
	close(fd);
	}
	else {

	fd = open("/dev/random", O_RDONLY);

	if (BC_NO_ERR(fd >= 0)) {
	bc_rand_fill(rng, bc_rand_frand, &fd);
	close(fd);
	}
	}
	+#else // _WIN32
	+ bc_rand_fill(rng, bc_rand_winrand, NULL);
	+#endif // _WIN32

	while (BC_ERR(BC_RAND_ZERO(rng))) bc_rand_fill(rng, bc_rand_rand, NULL);

	BC_SIG_UNLOCK;
	}

	static void bc_rand_propagate(BcRNG r, BcRNGData rng) {

	if (r->v.len <= 1) return;

	if (BC_RAND_NOTMODIFIED(rng)) {

	size_t i;
	bool go = true;

	for (i = 1; go && i < r->v.len; ++i) {
	BcRNGData *rng2 = bc_vec_item_rev(&r->v, i);
	go = BC_RAND_NOTMODIFIED(rng2);
	bc_rand_copy(rng2, rng);
	}

	bc_rand_seedZeroes(r, rng, i);
	}
	else bc_rand_seedZeroes(r, rng, 1);
	}

	BcRand bc_rand_int(BcRNG *r) {

	BcRNGData *rng = bc_vec_top(&r->v);

	if (BC_ERR(BC_RAND_ZERO(rng))) bc_rand_srand(rng);

	bc_rand_step(rng);
	bc_rand_propagate(r, rng);

	return bc_rand_output(rng);
	}

	BcRand bc_rand_bounded(BcRNG *r, BcRand bound) {

	BcRand rand, threshold = (0 - bound) % bound;

	do {
	rand = bc_rand_int(r);
	} while (rand < threshold);

	return rand % bound;
	}

	void bc_rand_seed(BcRNG *r, ulong state1, ulong state2, ulong inc1, ulong inc2)
	{
	BcRNGData *rng = bc_vec_top(&r->v);

	bc_rand_seedState(&rng->inc, inc1, inc2);
	bc_rand_setInc(rng);
	bc_rand_setModified(rng);

	if (!state1 && !state2) {
	memcpy(&rng->state, &rng->inc, sizeof(BcRandState));
	bc_rand_step(rng);
	}
	else bc_rand_seedState(&rng->state, state1, state2);

	bc_rand_propagate(r, rng);
	}

	static BcRandState bc_rand_getInc(BcRNGData *r) {

	BcRandState res;

	#if BC_RAND_BUILTIN
	res = r->inc >> 1;
	#else // BC_RAND_BUILTIN
	res = r->inc;
	res.lo >>= 1;
	res.lo \|= (res.hi & 1) << (BC_LONG_BIT - 1);
	res.hi >>= 1;
	#endif // BC_RAND_BUILTIN

	return res;
	}

	void bc_rand_getRands(BcRNG r, BcRand s1, BcRand s2, BcRand i1, BcRand *i2)
	{
	BcRandState inc;
	BcRNGData *rng = bc_vec_top(&r->v);

	if (BC_ERR(BC_RAND_ZERO(rng))) bc_rand_srand(rng);

	inc = bc_rand_getInc(rng);

	*s1 = BC_RAND_TRUNC(rng->state);
	*s2 = BC_RAND_CHOP(rng->state);

	*i1 = BC_RAND_TRUNC(inc);
	*i2 = BC_RAND_CHOP(inc);
	}

	void bc_rand_push(BcRNG *r) {
	BcRNGData rng;
	memset(&rng, 0, sizeof(BcRNGData));
	if (r->v.len > 0) bc_rand_copy(&rng, bc_vec_top(&r->v));
	bc_vec_push(&r->v, &rng);
	}

	void bc_rand_pop(BcRNG *r, bool reset) {
	bc_vec_npop(&r->v, reset ? r->v.len - 1 : 1);
	}

	void bc_rand_init(BcRNG *r) {
	BC_SIG_ASSERT_LOCKED;
	bc_vec_init(&r->v, sizeof(BcRNGData), NULL);
	bc_rand_push(r);
	}

	#ifndef NDEBUG
	void bc_rand_free(BcRNG *r) {
	BC_SIG_ASSERT_LOCKED;
	bc_vec_free(&r->v);
	}
	#endif // NDEBUG

	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	diff --git a/contrib/bc/src/read.c b/contrib/bc/src/read.c
	index e593b3c2dedd..43e65b65b345 100644
	--- a/contrib/bc/src/read.c
	+++ b/contrib/bc/src/read.c
	@@ -1,227 +1,246 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code to handle special I/O for bc.
	*
	*/

	#include <assert.h>
	#include <ctype.h>
	#include <errno.h>
	#include <stdlib.h>
	#include <string.h>

	#include <signal.h>

	#include <fcntl.h>
	#include <sys/stat.h>
	+
	+#ifndef _WIN32
	#include <unistd.h>
	+#endif // _WIN32

	#include <read.h>
	#include <history.h>
	#include <program.h>
	#include <vm.h>

	+static int bc_read_open(const char* path, int mode) {
	+
	+ int fd;
	+
	+#ifndef _WIN32
	+ fd = open(path, mode);
	+#else // _WIN32
	+ fd = -1;
	+ open(&fd, path, mode);
	+#endif
	+
	+ return fd;
	+}
	+
	static bool bc_read_binary(const char *buf, size_t size) {

	size_t i;

	for (i = 0; i < size; ++i) {
	if (BC_ERR(BC_READ_BIN_CHAR(buf[i]))) return true;
	}

	return false;
	}

	bool bc_read_buf(BcVec vec, char buf, size_t *buf_len) {

	char *nl;

	if (!*buf_len) return false;

	nl = strchr(buf, '\n');

	if (nl != NULL) {

	size_t nllen = (size_t) ((nl + 1) - buf);

	nllen = buf_len >= nllen ? nllen : buf_len;

	bc_vec_npush(vec, nllen, buf);
	*buf_len -= nllen;
	memmove(buf, nl + 1, *buf_len + 1);

	return true;
	}

	bc_vec_npush(vec, *buf_len, buf);
	*buf_len = 0;

	return false;
	}

	BcStatus bc_read_chars(BcVec vec, const char prompt) {

	bool done = false;

	assert(vec != NULL && vec->size == sizeof(char));

	BC_SIG_ASSERT_NOT_LOCKED;

	bc_vec_popAll(vec);

	#if BC_ENABLE_PROMPT
	if (BC_USE_PROMPT) {
	- bc_file_puts(&vm.fout, prompt);
	- bc_file_flush(&vm.fout);
	+ bc_file_puts(&vm.fout, bc_flush_none, prompt);
	+ bc_file_flush(&vm.fout, bc_flush_none);
	}
	#endif // BC_ENABLE_PROMPT

	if (bc_read_buf(vec, vm.buf, &vm.buf_len)) {
	bc_vec_pushByte(vec, '\0');
	return BC_STATUS_SUCCESS;
	}

	while (!done) {

	ssize_t r;

	BC_SIG_LOCK;

	r = read(STDIN_FILENO, vm.buf + vm.buf_len,
	BC_VM_STDIN_BUF_SIZE - vm.buf_len);

	if (BC_UNLIKELY(r < 0)) {

	if (errno == EINTR) {

	if (vm.status == (sig_atomic_t) BC_STATUS_QUIT) {
	BC_SIG_UNLOCK;
	return BC_STATUS_QUIT;
	}

	assert(vm.sig);

	vm.status = (sig_atomic_t) BC_STATUS_SUCCESS;
	#if BC_ENABLE_PROMPT
	- if (BC_USE_PROMPT) bc_file_puts(&vm.fout, prompt);
	+ if (BC_USE_PROMPT)
	+ bc_file_puts(&vm.fout, bc_flush_none, prompt);
	#endif // BC_ENABLE_PROMPT
	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_none);

	BC_SIG_UNLOCK;

	continue;
	}

	BC_SIG_UNLOCK;

	bc_vm_fatalError(BC_ERR_FATAL_IO_ERR);
	}

	BC_SIG_UNLOCK;

	if (r == 0) {
	bc_vec_pushByte(vec, '\0');
	return BC_STATUS_EOF;
	}

	vm.buf_len += (size_t) r;
	vm.buf[vm.buf_len] = '\0';

	done = bc_read_buf(vec, vm.buf, &vm.buf_len);
	}

	bc_vec_pushByte(vec, '\0');

	return BC_STATUS_SUCCESS;
	}

	BcStatus bc_read_line(BcVec vec, const char prompt) {

	BcStatus s;

	#if BC_ENABLE_HISTORY
	if (BC_TTY && !vm.history.badTerm)
	s = bc_history_line(&vm.history, vec, prompt);
	else s = bc_read_chars(vec, prompt);
	#else // BC_ENABLE_HISTORY
	s = bc_read_chars(vec, prompt);
	#endif // BC_ENABLE_HISTORY

	if (BC_ERR(bc_read_binary(vec->v, vec->len - 1)))
	bc_vm_verr(BC_ERR_FATAL_BIN_FILE, bc_program_stdin_name);

	return s;
	}

	void bc_read_file(const char path, char *buf) {

	BcErr e = BC_ERR_FATAL_IO_ERR;
	size_t size, r;
	struct stat pstat;
	int fd;

	BC_SIG_ASSERT_LOCKED;

	assert(path != NULL);

	- fd = open(path, O_RDONLY);
	+ fd = bc_read_open(path, O_RDONLY);
	+
	if (BC_ERR(fd < 0)) bc_vm_verr(BC_ERR_FATAL_FILE_ERR, path);
	if (BC_ERR(fstat(fd, &pstat) == -1)) goto malloc_err;

	if (BC_ERR(S_ISDIR(pstat.st_mode))) {
	e = BC_ERR_FATAL_PATH_DIR;
	goto malloc_err;
	}

	size = (size_t) pstat.st_size;
	*buf = bc_vm_malloc(size + 1);

	r = (size_t) read(fd, *buf, size);
	if (BC_ERR(r != size)) goto read_err;

	(*buf)[size] = '\0';

	if (BC_ERR(bc_read_binary(*buf, size))) {
	e = BC_ERR_FATAL_BIN_FILE;
	goto read_err;
	}

	close(fd);

	return;

	read_err:
	free(*buf);
	malloc_err:
	close(fd);
	bc_vm_verr(e, path);
	}
	diff --git a/contrib/bc/src/vm.c b/contrib/bc/src/vm.c
	index 87036c7b5c91..e7ee8d35ba54 100644
	--- a/contrib/bc/src/vm.c
	+++ b/contrib/bc/src/vm.c
	@@ -1,975 +1,1021 @@
	/*
	* *****************************************************************************
	*
	* SPDX-License-Identifier: BSD-2-Clause
	*
	* Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	*
	* Redistribution and use in source and binary forms, with or without
	* modification, are permitted provided that the following conditions are met:
	*
	* * Redistributions of source code must retain the above copyright notice, this
	* list of conditions and the following disclaimer.
	*
	* * 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.
	*
	* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	*
	* *****************************************************************************
	*
	* Code common to all of bc and dc.
	*
	*/

	#include <assert.h>
	#include <ctype.h>
	#include <errno.h>
	#include <stdarg.h>
	#include <string.h>

	#include <signal.h>

	#include <setjmp.h>

	#ifndef _WIN32

	#include <sys/types.h>
	#include <unistd.h>

	#else // _WIN32

	#define WIN32_LEAN_AND_MEAN
	#include <windows.h>
	#include <io.h>

	#endif // _WIN32

	+#include <status.h>
	#include <vector.h>
	#include <args.h>
	#include <vm.h>
	#include <read.h>
	#include <bc.h>

	char output_bufs[BC_VM_BUF_SIZE];
	BcVm vm;

	#if BC_DEBUG_CODE
	BC_NORETURN void bc_vm_jmp(const char* f) {
	#else // BC_DEBUG_CODE
	BC_NORETURN void bc_vm_jmp(void) {
	#endif

	assert(BC_SIG_EXC);

	BC_SIG_MAYLOCK;

	#if BC_DEBUG_CODE
	- bc_file_puts(&vm.ferr, "Longjmp: ");
	- bc_file_puts(&vm.ferr, f);
	- bc_file_putchar(&vm.ferr, '\n');
	- bc_file_flush(&vm.ferr);
	+ bc_file_puts(&vm.ferr, bc_flush_none, "Longjmp: ");
	+ bc_file_puts(&vm.ferr, bc_flush_none, f);
	+ bc_file_putchar(&vm.ferr, bc_flush_none, '\n');
	+ bc_file_flush(&vm.ferr, bc_flush_none);
	#endif // BC_DEBUG_CODE

	#ifndef NDEBUG
	assert(vm.jmp_bufs.len - (size_t) vm.sig_pop);
	#endif // NDEBUG

	if (vm.jmp_bufs.len == 0) abort();
	if (vm.sig_pop) bc_vec_pop(&vm.jmp_bufs);
	else vm.sig_pop = 1;

	siglongjmp(((sigjmp_buf) bc_vec_top(&vm.jmp_bufs)), 1);
	}

	#if !BC_ENABLE_LIBRARY
	static void bc_vm_sig(int sig) {

	// There is already a signal in flight.
	if (vm.status == (sig_atomic_t) BC_STATUS_QUIT \|\| vm.sig) {
	if (!BC_TTY \|\| sig != SIGINT) vm.status = BC_STATUS_QUIT;
	return;
	}

	if (BC_TTY && sig == SIGINT) {

	int err = errno;

	if (write(STDOUT_FILENO, vm.sigmsg, vm.siglen) != (ssize_t) vm.siglen)
	vm.status = BC_STATUS_ERROR_FATAL;
	else vm.sig = 1;

	errno = err;
	}
	else vm.status = BC_STATUS_QUIT;

	assert(vm.jmp_bufs.len);

	if (!vm.sig_lock) BC_VM_JMP;
	}

	+static void bc_vm_sigaction(void) {
	+#ifndef _WIN32
	+
	+ struct sigaction sa;
	+
	+ sigemptyset(&sa.sa_mask);
	+ sa.sa_handler = bc_vm_sig;
	+ sa.sa_flags = SA_NODEFER;
	+
	+ sigaction(SIGTERM, &sa, NULL);
	+ sigaction(SIGQUIT, &sa, NULL);
	+ sigaction(SIGINT, &sa, NULL);
	+
	+#if BC_ENABLE_HISTORY
	+ if (BC_TTY) sigaction(SIGHUP, &sa, NULL);
	+#endif // BC_ENABLE_HISTORY
	+
	+#else // _WIN32
	+
	+ signal(SIGTERM, bc_vm_sig);
	+
	+#endif // _WIN32
	+}
	+
	void bc_vm_info(const char* const help) {

	BC_SIG_ASSERT_LOCKED;

	- bc_file_puts(&vm.fout, vm.name);
	- bc_file_putchar(&vm.fout, ' ');
	- bc_file_puts(&vm.fout, BC_VERSION);
	- bc_file_putchar(&vm.fout, '\n');
	- bc_file_puts(&vm.fout, bc_copyright);
	+ bc_file_puts(&vm.fout, bc_flush_none, vm.name);
	+ bc_file_putchar(&vm.fout, bc_flush_none, ' ');
	+ bc_file_puts(&vm.fout, bc_flush_none, BC_VERSION);
	+ bc_file_putchar(&vm.fout, bc_flush_none, '\n');
	+ bc_file_puts(&vm.fout, bc_flush_none, bc_copyright);

	if (help) {
	- bc_file_putchar(&vm.fout, '\n');
	- bc_file_printf(&vm.fout, help, vm.name, vm.name);
	+ bc_file_putchar(&vm.fout, bc_flush_none, '\n');
	+ bc_file_printf(&vm.fout, help, vm.name, vm.name,
	+ BC_VERSION, BC_BUILD_TYPE);
	}

	- bc_file_flush(&vm.fout);
	+ bc_file_flush(&vm.fout, bc_flush_err);
	}
	#endif // !BC_ENABLE_LIBRARY

	#if !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	BC_NORETURN
	#endif // !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	void bc_vm_fatalError(BcErr e) {
	bc_vm_err(e);
	#if !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	abort();
	#endif // !BC_ENABLE_LIBRARY && !BC_ENABLE_MEMCHECK
	}

	#if BC_ENABLE_LIBRARY
	void bc_vm_handleError(BcErr e) {

	assert(e < BC_ERR_NELEMS);
	assert(!vm.sig_pop);

	BC_SIG_LOCK;

	if (e <= BC_ERR_MATH_DIVIDE_BY_ZERO) {
	vm.err = (BclError) (e - BC_ERR_MATH_NEGATIVE +
	BCL_ERROR_MATH_NEGATIVE);
	}
	else if (vm.abrt) abort();
	else if (e == BC_ERR_FATAL_ALLOC_ERR) vm.err = BCL_ERROR_FATAL_ALLOC_ERR;
	else vm.err = BCL_ERROR_FATAL_UNKNOWN_ERR;

	BC_VM_JMP;
	}
	#else // BC_ENABLE_LIBRARY
	void bc_vm_handleError(BcErr e, size_t line, ...) {

	BcStatus s;
	va_list args;
	uchar id = bc_err_ids[e];
	const char* err_type = vm.err_ids[id];
	sig_atomic_t lock;

	assert(e < BC_ERR_NELEMS);
	assert(!vm.sig_pop);

	#if BC_ENABLED
	if (!BC_S && e >= BC_ERR_POSIX_START) {
	if (BC_W) {
	// Make sure to not return an error.
	id = UCHAR_MAX;
	err_type = vm.err_ids[BC_ERR_IDX_WARN];
	}
	else return;
	}
	#endif // BC_ENABLED

	BC_SIG_TRYLOCK(lock);

	// Make sure all of stdout is written first.
	- s = bc_file_flushErr(&vm.fout);
	+ s = bc_file_flushErr(&vm.fout, bc_flush_err);

	if (BC_ERR(s == BC_STATUS_ERROR_FATAL)) {
	vm.status = (sig_atomic_t) s;
	BC_VM_JMP;
	}

	va_start(args, line);
	- bc_file_putchar(&vm.ferr, '\n');
	- bc_file_puts(&vm.ferr, err_type);
	- bc_file_putchar(&vm.ferr, ' ');
	+ bc_file_putchar(&vm.ferr, bc_flush_none, '\n');
	+ bc_file_puts(&vm.ferr, bc_flush_none, err_type);
	+ bc_file_putchar(&vm.ferr, bc_flush_none, ' ');
	bc_file_vprintf(&vm.ferr, vm.err_msgs[e], args);
	va_end(args);

	if (BC_NO_ERR(vm.file)) {

	// This is the condition for parsing vs runtime.
	// If line is not 0, it is parsing.
	if (line) {
	- bc_file_puts(&vm.ferr, "\n ");
	- bc_file_puts(&vm.ferr, vm.file);
	+ bc_file_puts(&vm.ferr, bc_flush_none, "\n ");
	+ bc_file_puts(&vm.ferr, bc_flush_none, vm.file);
	bc_file_printf(&vm.ferr, bc_err_line, line);
	}
	else {

	BcInstPtr *ip = bc_vec_item_rev(&vm.prog.stack, 0);
	BcFunc *f = bc_vec_item(&vm.prog.fns, ip->func);

	- bc_file_puts(&vm.ferr, "\n ");
	- bc_file_puts(&vm.ferr, vm.func_header);
	- bc_file_putchar(&vm.ferr, ' ');
	- bc_file_puts(&vm.ferr, f->name);
	+ bc_file_puts(&vm.ferr, bc_flush_none, "\n ");
	+ bc_file_puts(&vm.ferr, bc_flush_none, vm.func_header);
	+ bc_file_putchar(&vm.ferr, bc_flush_none, ' ');
	+ bc_file_puts(&vm.ferr, bc_flush_none, f->name);

	#if BC_ENABLED
	if (BC_IS_BC && ip->func != BC_PROG_MAIN &&
	ip->func != BC_PROG_READ)
	{
	- bc_file_puts(&vm.ferr, "()");
	+ bc_file_puts(&vm.ferr, bc_flush_none, "()");
	}
	#endif // BC_ENABLED
	}
	}

	- bc_file_puts(&vm.ferr, "\n\n");
	+ bc_file_puts(&vm.ferr, bc_flush_none, "\n\n");

	- s = bc_file_flushErr(&vm.ferr);
	+ s = bc_file_flushErr(&vm.ferr, bc_flush_err);

	#if !BC_ENABLE_MEMCHECK
	// Because this function is called by a BC_NORETURN function when fatal
	// errors happen, we need to make sure to exit on fatal errors. This will
	// be faster anyway. This function cannot jump when a fatal error occurs!
	if (BC_ERR(id == BC_ERR_IDX_FATAL \|\| s == BC_STATUS_ERROR_FATAL))
	exit(bc_vm_atexit((int) BC_STATUS_ERROR_FATAL));
	#else // !BC_ENABLE_MEMCHECK
	if (BC_ERR(s == BC_STATUS_ERROR_FATAL)) vm.status = (sig_atomic_t) s;
	else
	#endif // !BC_ENABLE_MEMCHECK
	{
	vm.status = (sig_atomic_t) (uchar) (id + 1);
	}

	if (BC_ERR(vm.status)) BC_VM_JMP;

	BC_SIG_TRYUNLOCK(lock);
	}

	static void bc_vm_envArgs(const char* const env_args_name) {

	- char env_args = getenv(env_args_name), buf, *start;
	+ char env_args = bc_vm_getenv(env_args_name), buf, *start;
	char instr = '\0';

	BC_SIG_ASSERT_LOCKED;

	if (env_args == NULL) return;

	+ // Windows already allocates, so we don't need to.
	+#ifndef _WIN32
	start = buf = vm.env_args_buffer = bc_vm_strdup(env_args);
	+#else // _WIN32
	+ start = buf = vm.env_args_buffer = env_args;
	+#endif // _WIN32

	assert(buf != NULL);

	bc_vec_init(&vm.env_args, sizeof(char*), NULL);
	bc_vec_push(&vm.env_args, &env_args_name);

	while (*buf) {

	if (!isspace(*buf)) {

	if (buf == '"' \|\| buf == '\'') {

	instr = *buf;
	buf += 1;

	if (*buf == instr) {
	instr = '\0';
	buf += 1;
	continue;
	}
	}

	bc_vec_push(&vm.env_args, &buf);

	while (buf && ((!instr && !isspace(buf)) \|\|
	(instr && *buf != instr)))
	{
	buf += 1;
	}

	if (*buf) {

	if (instr) instr = '\0';

	*buf = '\0';
	buf += 1;
	start = buf;
	}
	else if (instr) bc_vm_error(BC_ERR_FATAL_OPTION, 0, start);
	}
	else buf += 1;
	}

	// Make sure to push a NULL pointer at the end.
	buf = NULL;
	bc_vec_push(&vm.env_args, &buf);

	bc_args((int) vm.env_args.len - 1, bc_vec_item(&vm.env_args, 0), false);
	}

	static size_t bc_vm_envLen(const char *var) {

	- char *lenv = getenv(var);
	+ char *lenv = bc_vm_getenv(var);
	size_t i, len = BC_NUM_PRINT_WIDTH;
	int num;

	if (lenv == NULL) return len;

	len = strlen(lenv);

	for (num = 1, i = 0; num && i < len; ++i) num = isdigit(lenv[i]);

	if (num) {
	len = (size_t) atoi(lenv) - 1;
	if (len < 2 \|\| len >= UINT16_MAX) len = BC_NUM_PRINT_WIDTH;
	}
	else len = BC_NUM_PRINT_WIDTH;

	+ bc_vm_getenvFree(lenv);
	+
	return len;
	}
	#endif // BC_ENABLE_LIBRARY

	void bc_vm_shutdown(void) {

	BC_SIG_ASSERT_LOCKED;

	#if BC_ENABLE_NLS
	if (vm.catalog != BC_VM_INVALID_CATALOG) catclose(vm.catalog);
	#endif // BC_ENABLE_NLS

	#if BC_ENABLE_HISTORY
	// This must always run to ensure that the terminal is back to normal.
	if (BC_TTY) bc_history_free(&vm.history);
	#endif // BC_ENABLE_HISTORY

	#ifndef NDEBUG
	#if !BC_ENABLE_LIBRARY
	bc_vec_free(&vm.env_args);
	free(vm.env_args_buffer);
	bc_vec_free(&vm.files);
	bc_vec_free(&vm.exprs);

	bc_program_free(&vm.prog);
	bc_parse_free(&vm.prs);
	#endif // !BC_ENABLE_LIBRARY

	bc_vm_freeTemps();
	bc_vec_free(&vm.temps);
	#endif // NDEBUG

	#if !BC_ENABLE_LIBRARY
	bc_file_free(&vm.fout);
	bc_file_free(&vm.ferr);
	#endif // !BC_ENABLE_LIBRARY
	}

	#if !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY
	void bc_vm_freeTemps(void) {

	size_t i;

	for (i = 0; i < vm.temps.len; ++i) {
	free(((BcNum*) bc_vec_item(&vm.temps, i))->num);
	}
	}
	#endif // !defined(NDEBUG) \|\| BC_ENABLE_LIBRARY

	inline size_t bc_vm_arraySize(size_t n, size_t size) {
	size_t res = n * size;
	if (BC_ERR(res >= SIZE_MAX \|\| (n != 0 && res / n != size)))
	bc_vm_fatalError(BC_ERR_FATAL_ALLOC_ERR);
	return res;
	}

	inline size_t bc_vm_growSize(size_t a, size_t b) {
	size_t res = a + b;
	if (BC_ERR(res >= SIZE_MAX \|\| res < a \|\| res < b))
	bc_vm_fatalError(BC_ERR_FATAL_ALLOC_ERR);
	return res;
	}

	void* bc_vm_malloc(size_t n) {

	void* ptr;

	BC_SIG_ASSERT_LOCKED;

	ptr = malloc(n);

	if (BC_ERR(ptr == NULL)) bc_vm_fatalError(BC_ERR_FATAL_ALLOC_ERR);

	return ptr;
	}

	void* bc_vm_realloc(void *ptr, size_t n) {

	void* temp;

	BC_SIG_ASSERT_LOCKED;

	temp = realloc(ptr, n);

	if (BC_ERR(temp == NULL)) bc_vm_fatalError(BC_ERR_FATAL_ALLOC_ERR);

	return temp;
	}

	char* bc_vm_strdup(const char *str) {

	char *s;

	BC_SIG_ASSERT_LOCKED;

	s = strdup(str);

	if (BC_ERR(s == NULL)) bc_vm_fatalError(BC_ERR_FATAL_ALLOC_ERR);

	return s;
	}

	#if !BC_ENABLE_LIBRARY
	void bc_vm_printf(const char *fmt, ...) {

	va_list args;

	BC_SIG_LOCK;

	va_start(args, fmt);
	bc_file_vprintf(&vm.fout, fmt, args);
	va_end(args);

	vm.nchars = 0;

	BC_SIG_UNLOCK;
	}
	#endif // !BC_ENABLE_LIBRARY

	-void bc_vm_putchar(int c) {
	+void bc_vm_putchar(int c, BcFlushType type) {
	#if BC_ENABLE_LIBRARY
	bc_vec_pushByte(&vm.out, (uchar) c);
	#else // BC_ENABLE_LIBRARY
	- bc_file_putchar(&vm.fout, (uchar) c);
	+ bc_file_putchar(&vm.fout, type, (uchar) c);
	vm.nchars = (c == '\n' ? 0 : vm.nchars + 1);
	#endif // BC_ENABLE_LIBRARY
	}

	+char* bc_vm_getenv(const char* var) {
	+
	+ char* ret;
	+
	+#ifndef _WIN32
	+ ret = getenv(var);
	+#else // _WIN32
	+ _dupenv_s(&ret, NULL, var);
	+#endif // _WIN32
	+
	+ return ret;
	+}
	+
	+void bc_vm_getenvFree(char* var) {
	+ BC_UNUSED(var);
	+#ifdef _WIN32
	+ free(var);
	+#endif // _WIN32
	+}
	+
	#if !BC_ENABLE_LIBRARY
	static void bc_vm_clean(void) {

	BcVec *fns = &vm.prog.fns;
	BcFunc *f = bc_vec_item(fns, BC_PROG_MAIN);
	BcInstPtr *ip = bc_vec_item(&vm.prog.stack, 0);
	bool good = ((vm.status && vm.status != BC_STATUS_QUIT) \|\| vm.sig);

	if (good) bc_program_reset(&vm.prog);

	#if BC_ENABLED
	if (good && BC_IS_BC) good = !BC_PARSE_NO_EXEC(&vm.prs);
	#endif // BC_ENABLED

	#if DC_ENABLED
	if (BC_IS_DC) {

	size_t i;

	good = true;

	for (i = 0; good && i < vm.prog.results.len; ++i) {
	BcResult r = (BcResult) bc_vec_item(&vm.prog.results, i);
	good = BC_VM_SAFE_RESULT(r);
	}
	}
	#endif // DC_ENABLED

	// If this condition is true, we can get rid of strings,
	// constants, and code. This is an idea from busybox.
	if (good && vm.prog.stack.len == 1 && ip->idx == f->code.len) {

	#if BC_ENABLED
	if (BC_IS_BC) {
	bc_vec_popAll(&f->labels);
	bc_vec_popAll(&f->strs);
	bc_vec_popAll(&f->consts);
	}
	#endif // BC_ENABLED

	#if DC_ENABLED
	// Note to self: you cannot delete strings and functions. Deal with it.
	if (BC_IS_DC) bc_vec_popAll(vm.prog.consts);
	#endif // DC_ENABLED

	bc_vec_popAll(&f->code);

	ip->idx = 0;
	}
	}

	static void bc_vm_process(const char *text) {

	bc_parse_text(&vm.prs, text);

	do {

	#if BC_ENABLED
	if (vm.prs.l.t == BC_LEX_KW_DEFINE) vm.parse(&vm.prs);
	#endif // BC_ENABLED

	while (BC_PARSE_CAN_PARSE(vm.prs)) vm.parse(&vm.prs);

	if(BC_IS_DC \|\| !BC_PARSE_NO_EXEC(&vm.prs)) bc_program_exec(&vm.prog);

	assert(BC_IS_DC \|\| vm.prog.results.len == 0);

	- if (BC_I) bc_file_flush(&vm.fout);
	+ if (BC_I) bc_file_flush(&vm.fout, bc_flush_save);

	} while (vm.prs.l.t != BC_LEX_EOF);
	}

	#if BC_ENABLED
	static void bc_vm_endif(void) {

	size_t i;
	bool good;

	if (BC_NO_ERR(!BC_PARSE_NO_EXEC(&vm.prs))) return;

	good = true;

	for (i = 0; good && i < vm.prs.flags.len; ++i) {
	uint16_t flag = ((uint16_t) bc_vec_item(&vm.prs.flags, i));
	good = ((flag & BC_PARSE_FLAG_BRACE) != BC_PARSE_FLAG_BRACE);
	}

	if (good) {
	while (BC_PARSE_IF_END(&vm.prs)) bc_vm_process("else {}");
	}
	else bc_parse_err(&vm.prs, BC_ERR_PARSE_BLOCK);
	}
	#endif // BC_ENABLED

	static void bc_vm_file(const char *file) {

	char *data = NULL;

	assert(!vm.sig_pop);

	bc_lex_file(&vm.prs.l, file);

	BC_SIG_LOCK;

	bc_read_file(file, &data);

	BC_SETJMP_LOCKED(err);

	BC_SIG_UNLOCK;

	bc_vm_process(data);

	#if BC_ENABLED
	if (BC_IS_BC) bc_vm_endif();
	#endif // BC_ENABLED

	err:
	BC_SIG_MAYLOCK;

	free(data);
	bc_vm_clean();

	// bc_program_reset(), called by bc_vm_clean(), resets the status.
	// We want it to clear the sig_pop variable in case it was set.
	if (vm.status == (sig_atomic_t) BC_STATUS_SUCCESS) BC_LONGJMP_STOP;

	BC_LONGJMP_CONT;
	}

	static void bc_vm_stdin(void) {

	BcStatus s;
	BcVec buf, buffer;
	size_t string = 0;
	bool comment = false, hash = false;

	bc_lex_file(&vm.prs.l, bc_program_stdin_name);

	BC_SIG_LOCK;
	bc_vec_init(&buffer, sizeof(uchar), NULL);
	bc_vec_init(&buf, sizeof(uchar), NULL);
	bc_vec_pushByte(&buffer, '\0');
	BC_SETJMP_LOCKED(err);
	BC_SIG_UNLOCK;

	restart:

	// This loop is complex because the vm tries not to send any lines that end
	// with a backslash to the parser. The reason for that is because the parser
	// treats a backslash+newline combo as whitespace, per the bc spec. In that
	// case, and for strings and comments, the parser will expect more stuff.
	while ((!(s = bc_read_line(&buf, ">>> ")) \|\|
	(vm.eof = (s == BC_STATUS_EOF))) && buf.len > 1)
	{
	char c2, *str = buf.v;
	size_t i, len = buf.len - 1;

	for (i = 0; i < len; ++i) {

	bool notend = len > i + 1;
	uchar c = (uchar) str[i];

	hash = (!comment && !string && ((hash && c != '\n') \|\|
	(!hash && c == '#')));

	if (!hash && !comment && (i - 1 > len \|\| str[i - 1] != '\\')) {
	if (BC_IS_BC) string ^= (c == '"');
	else if (c == ']') string -= 1;
	else if (c == '[') string += 1;
	}

	if (BC_IS_BC && !hash && !string && notend) {

	c2 = str[i + 1];

	if (c == '/' && !comment && c2 == '*') {
	comment = true;
	i += 1;
	}
	else if (c == '*' && comment && c2 == '/') {
	comment = false;
	i += 1;
	}
	}
	}

	bc_vec_concat(&buffer, buf.v);

	if (string \|\| comment) continue;
	if (len >= 2 && str[len - 2] == '\\' && str[len - 1] == '\n') continue;
	#if BC_ENABLE_HISTORY
	if (vm.history.stdin_has_data) continue;
	#endif // BC_ENABLE_HISTORY

	bc_vm_process(buffer.v);
	bc_vec_empty(&buffer);

	if (vm.eof) break;
	else bc_vm_clean();
	}

	if (!BC_STATUS_IS_ERROR(s)) {
	if (BC_ERR(comment))
	bc_parse_err(&vm.prs, BC_ERR_PARSE_COMMENT);
	else if (BC_ERR(string))
	bc_parse_err(&vm.prs, BC_ERR_PARSE_STRING);
	#if BC_ENABLED
	else if (BC_IS_BC) bc_vm_endif();
	#endif // BC_ENABLED
	}

	err:
	BC_SIG_MAYLOCK;

	bc_vm_clean();

	#if !BC_ENABLE_MEMCHECK
	assert(vm.status != BC_STATUS_ERROR_FATAL);

	vm.status = vm.status == BC_STATUS_QUIT \|\| !BC_I ?
	vm.status : BC_STATUS_SUCCESS;
	#else // !BC_ENABLE_MEMCHECK
	vm.status = vm.status == BC_STATUS_ERROR_FATAL \|\|
	vm.status == BC_STATUS_QUIT \|\| !BC_I ?
	vm.status : BC_STATUS_SUCCESS;
	#endif // !BC_ENABLE_MEMCHECK

	if (!vm.status && !vm.eof) {
	bc_vec_empty(&buffer);
	BC_LONGJMP_STOP;
	BC_SIG_UNLOCK;
	goto restart;
	}

	bc_vec_free(&buf);
	bc_vec_free(&buffer);

	BC_LONGJMP_CONT;
	}

	#if BC_ENABLED
	static void bc_vm_load(const char name, const char text) {

	bc_lex_file(&vm.prs.l, name);
	bc_parse_text(&vm.prs, text);

	while (vm.prs.l.t != BC_LEX_EOF) vm.parse(&vm.prs);
	}
	#endif // BC_ENABLED

	static void bc_vm_defaultMsgs(void) {

	size_t i;

	vm.func_header = bc_err_func_header;

	for (i = 0; i < BC_ERR_IDX_NELEMS + BC_ENABLED; ++i)
	vm.err_ids[i] = bc_errs[i];
	for (i = 0; i < BC_ERR_NELEMS; ++i) vm.err_msgs[i] = bc_err_msgs[i];
	}

	static void bc_vm_gettext(void) {

	#if BC_ENABLE_NLS
	uchar id = 0;
	int set = 1, msg = 1;
	size_t i;

	if (vm.locale == NULL) {
	vm.catalog = BC_VM_INVALID_CATALOG;
	bc_vm_defaultMsgs();
	return;
	}

	vm.catalog = catopen(BC_MAINEXEC, NL_CAT_LOCALE);

	if (vm.catalog == BC_VM_INVALID_CATALOG) {
	bc_vm_defaultMsgs();
	return;
	}

	vm.func_header = catgets(vm.catalog, set, msg, bc_err_func_header);

	for (set += 1; msg <= BC_ERR_IDX_NELEMS + BC_ENABLED; ++msg)
	vm.err_ids[msg - 1] = catgets(vm.catalog, set, msg, bc_errs[msg - 1]);

	i = 0;
	id = bc_err_ids[i];

	for (set = id + 3, msg = 1; i < BC_ERR_NELEMS; ++i, ++msg) {

	if (id != bc_err_ids[i]) {
	msg = 1;
	id = bc_err_ids[i];
	set = id + 3;
	}

	vm.err_msgs[i] = catgets(vm.catalog, set, msg, bc_err_msgs[i]);
	}
	#else // BC_ENABLE_NLS
	bc_vm_defaultMsgs();
	#endif // BC_ENABLE_NLS
	}

	static void bc_vm_exec(void) {

	size_t i;
	bool has_file = false;
	BcVec buf;

	#if BC_ENABLED
	if (BC_IS_BC && (vm.flags & BC_FLAG_L)) {

	bc_vm_load(bc_lib_name, bc_lib);

	#if BC_ENABLE_EXTRA_MATH
	if (!BC_IS_POSIX) bc_vm_load(bc_lib2_name, bc_lib2);
	#endif // BC_ENABLE_EXTRA_MATH
	}
	#endif // BC_ENABLED

	if (vm.exprs.len) {

	size_t len = vm.exprs.len - 1;
	bool more;

	BC_SIG_LOCK;
	bc_vec_init(&buf, sizeof(uchar), NULL);

	#ifndef NDEBUG
	BC_SETJMP_LOCKED(err);
	#endif // NDEBUG

	BC_SIG_UNLOCK;

	bc_lex_file(&vm.prs.l, bc_program_exprs_name);

	do {

	more = bc_read_buf(&buf, vm.exprs.v, &len);
	bc_vec_pushByte(&buf, '\0');
	bc_vm_process(buf.v);

	bc_vec_popAll(&buf);

	} while (more);

	BC_SIG_LOCK;
	bc_vec_free(&buf);

	#ifndef NDEBUG
	BC_UNSETJMP;
	#endif // NDEBUG

	BC_SIG_UNLOCK;

	if (!vm.no_exit_exprs && vm.exit_exprs) return;
	}

	for (i = 0; i < vm.files.len; ++i) {
	char path = ((char**) bc_vec_item(&vm.files, i));
	if (!strcmp(path, "")) continue;
	has_file = true;
	bc_vm_file(path);
	}

	#if BC_ENABLE_AFL
	__AFL_INIT();
	#endif // BC_ENABLE_AFL

	if (BC_IS_BC \|\| !has_file) bc_vm_stdin();

	// These are all protected by ifndef NDEBUG because if these are needed, bc is
	// going to exit anyway, and I see no reason to include this code in a release
	// build when the OS is going to free all of the resources anyway.
	#ifndef NDEBUG
	return;

	err:
	BC_SIG_MAYLOCK;
	bc_vec_free(&buf);
	BC_LONGJMP_CONT;
	#endif // NDEBUG
	}

	void bc_vm_boot(int argc, char argv[], const char env_len,
	const char* const env_args)
	{
	int ttyin, ttyout, ttyerr;
	- struct sigaction sa;

	BC_SIG_ASSERT_LOCKED;

	ttyin = isatty(STDIN_FILENO);
	ttyout = isatty(STDOUT_FILENO);
	ttyerr = isatty(STDERR_FILENO);

	vm.flags \|= ttyin ? BC_FLAG_TTYIN : 0;
	vm.flags \|= (ttyin != 0 && ttyout != 0 && ttyerr != 0) ? BC_FLAG_TTY : 0;
	vm.flags \|= ttyin && ttyout ? BC_FLAG_I : 0;

	- sigemptyset(&sa.sa_mask);
	- sa.sa_handler = bc_vm_sig;
	- sa.sa_flags = SA_NODEFER;
	-
	- sigaction(SIGTERM, &sa, NULL);
	- sigaction(SIGQUIT, &sa, NULL);
	- sigaction(SIGINT, &sa, NULL);
	-
	-#if BC_ENABLE_HISTORY
	- if (BC_TTY) sigaction(SIGHUP, &sa, NULL);
	-#endif // BC_ENABLE_HISTORY
	+ bc_vm_sigaction();

	bc_vm_init();

	vm.file = NULL;

	bc_vm_gettext();

	bc_file_init(&vm.ferr, STDERR_FILENO, output_bufs + BC_VM_STDOUT_BUF_SIZE,
	BC_VM_STDERR_BUF_SIZE);
	bc_file_init(&vm.fout, STDOUT_FILENO, output_bufs, BC_VM_STDOUT_BUF_SIZE);
	vm.buf = output_bufs + BC_VM_STDOUT_BUF_SIZE + BC_VM_STDERR_BUF_SIZE;

	vm.line_len = (uint16_t) bc_vm_envLen(env_len);

	bc_vec_clear(&vm.files);
	bc_vec_clear(&vm.exprs);

	bc_program_init(&vm.prog);
	bc_parse_init(&vm.prs, &vm.prog, BC_PROG_MAIN);

	#if BC_ENABLE_HISTORY
	if (BC_TTY) bc_history_init(&vm.history);
	#endif // BC_ENABLE_HISTORY

	#if BC_ENABLED
	- if (BC_IS_BC) vm.flags \|= BC_FLAG_S * (getenv("POSIXLY_CORRECT") != NULL);
	+ if (BC_IS_BC) {
	+ char* var = bc_vm_getenv("POSIXLY_CORRECT");
	+ vm.flags \|= BC_FLAG_S * (var != NULL);
	+ bc_vm_getenvFree(var);
	+ }
	#endif // BC_ENABLED

	bc_vm_envArgs(env_args);
	bc_args(argc, argv, true);

	#if BC_ENABLED
	if (BC_IS_POSIX) vm.flags &= ~(BC_FLAG_G);
	#endif // BC_ENABLED

	BC_SIG_UNLOCK;

	bc_vm_exec();
	}
	#endif // !BC_ENABLE_LIBRARY

	void bc_vm_init(void) {

	BC_SIG_ASSERT_LOCKED;

	memcpy(vm.max_num, bc_num_bigdigMax,
	bc_num_bigdigMax_size * sizeof(BcDig));
	memcpy(vm.max2_num, bc_num_bigdigMax2,
	bc_num_bigdigMax2_size * sizeof(BcDig));
	bc_num_setup(&vm.max, vm.max_num, BC_NUM_BIGDIG_LOG10);
	bc_num_setup(&vm.max2, vm.max2_num, BC_NUM_BIGDIG_LOG10);
	vm.max.len = bc_num_bigdigMax_size;
	vm.max2.len = bc_num_bigdigMax2_size;

	bc_vec_init(&vm.temps, sizeof(BcNum), NULL);

	vm.maxes[BC_PROG_GLOBALS_IBASE] = BC_NUM_MAX_POSIX_IBASE;
	vm.maxes[BC_PROG_GLOBALS_OBASE] = BC_MAX_OBASE;
	vm.maxes[BC_PROG_GLOBALS_SCALE] = BC_MAX_SCALE;

	#if BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND
	vm.maxes[BC_PROG_MAX_RAND] = ((BcRand) 0) - 1;
	#endif // BC_ENABLE_EXTRA_MATH && BC_ENABLE_RAND

	#if BC_ENABLED
	#if !BC_ENABLE_LIBRARY
	if (BC_IS_BC && !BC_IS_POSIX)
	#endif // !BC_ENABLE_LIBRARY
	{
	vm.maxes[BC_PROG_GLOBALS_IBASE] = BC_NUM_MAX_IBASE;
	}
	#endif // BC_ENABLED
	}

	#if BC_ENABLE_LIBRARY
	void bc_vm_atexit(void) {

	bc_vm_shutdown();

	#ifndef NDEBUG
	bc_vec_free(&vm.jmp_bufs);
	#endif // NDEBUG
	}
	#else // BC_ENABLE_LIBRARY
	int bc_vm_atexit(int status) {

	int s = BC_STATUS_IS_ERROR(status) ? status : BC_STATUS_SUCCESS;

	bc_vm_shutdown();

	#ifndef NDEBUG
	bc_vec_free(&vm.jmp_bufs);
	#endif // NDEBUG

	return s;
	}
	#endif // BC_ENABLE_LIBRARY
	diff --git a/contrib/bc/tests/dc/scripts/easter.sh b/contrib/bc/tests/dc/scripts/easter.sh
	new file mode 100644
	index 000000000000..dd030e4024d0
	--- /dev/null
	+++ b/contrib/bc/tests/dc/scripts/easter.sh
	@@ -0,0 +1,47 @@
	+#!/bin/sh
	+
	+if test $# -lt 2
	+then
	+ echo usage: $0 dc_exec year
	+ exit 1
	+fi
	+
	+dc_exec="$1"
	+shift
	+
	+year="$1"
	+shift
	+
	+echo $year '
	+[
	+ ddsf
	+ [
	+ lfp
	+ [too early
	+ ]P
	+ q
	+ ]s@
	+ 1583>@
	+ ddd19%1+sg100/1+d34/12-sx85+25/5-sz54/lx-10-sdlg1120+lz+lx-30%
	+ d
	+ [30+]s@
	+ 0>@d
	+ [
	+ [1+]s@
	+ lg11<@
	+ ]s@
	+ 25=@d
	+ [1+]s@
	+ 24=@se44le-d
	+ [30+]s@
	+ 21>@dld+7%-7+
	+ [March ]sm
	+ d
	+ [
	+ 31-
	+ [April ]sm
	+ ]s@
	+ 31<@psnlmPpsn1z>p
	+]sp
	+lpx' \| "$dc_exec" \| tr '\012' ' '
	+echo ''
	diff --git a/contrib/bc/tests/other.sh b/contrib/bc/tests/other.sh
	index 8c56e25d2395..d2ef4f6d0694 100755
	--- a/contrib/bc/tests/other.sh
	+++ b/contrib/bc/tests/other.sh
	@@ -1,271 +1,304 @@
	#! /bin/sh
	#
	# SPDX-License-Identifier: BSD-2-Clause
	#
	# Copyright (c) 2018-2021 Gavin D. Howard and contributors.
	#
	# Redistribution and use in source and binary forms, with or without
	# modification, are permitted provided that the following conditions are met:
	#
	# * Redistributions of source code must retain the above copyright notice, this
	# list of conditions and the following disclaimer.
	#
	# * 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.
	#
	# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT HOLDER 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.
	#

	set -e

	script="$0"
	testdir=$(dirname "$script")

	. "$testdir/../functions.sh"

	if [ "$#" -ge 1 ]; then
	d="$1"
	shift
	else
	err_exit "usage: $script dir [exec args...]" 1
	fi

	if [ "$#" -lt 1 ]; then
	exe="$testdir/../bin/$d"
	else
	exe="$1"
	shift
	fi

	if [ "$d" = "bc" ]; then
	halt="quit"
	else
	halt="q"
	fi

	num=100000000000000000000000000000000000000000000000000000000000000000000000000000
	numres="$num"
	num70="10000000000000000000000000000000000000000000000000000000000000000000\\
	0000000000"

	if [ "$d" = "bc" ]; then
	halt="halt"
	opt="x"
	lopt="extended-register"
	line_var="BC_LINE_LENGTH"
	else
	halt="q"
	opt="l"
	lopt="mathlib"
	line_var="DC_LINE_LENGTH"
	num="$num pR"
	fi

	set +e

	printf '\nRunning %s quit test...' "$d"

	printf '%s\n' "$halt" \| "$exe" "$@" > /dev/null 2>&1

	checktest_retcode "$d" "$?" "quit"

	if [ "$d" = bc ]; then

	printf '%s\n' "quit" \| "$exe" "$@" > /dev/null 2>&1

	checktest_retcode "$d" "$?" quit

	two=$("$exe" "$@" -e 1+1 -e quit)

	checktest_retcode "$d" "$?" quit

	if [ "$two" != "2" ]; then
	err_exit "$d failed test quit" 1
	fi
	fi

	printf 'pass\n'

	base=$(basename "$exe")

	if [ "$base" != "bc" -a "$base" != "dc" ]; then
	exit 0
	fi

	printf 'Running %s environment var tests...' "$d"

	if [ "$d" = "bc" ]; then

	export BC_ENV_ARGS=" '-l' '' -q"
	export BC_EXPR_EXIT="1"

	printf 's(.02893)\n' \| "$exe" "$@" > /dev/null

	checktest_retcode "$d" "$?" "environment var"

	"$exe" -e 4 "$@" > /dev/null

	err="$?"
	checktest_retcode "$d" "$?" "environment var"
	+
	+ printf 'pass\n'
	+
	else

	export DC_ENV_ARGS="'-x'"
	export DC_EXPR_EXIT="1"

	printf '4s stuff\n' \| "$exe" "$@" > /dev/null

	checktest_retcode "$d" "$?" "environment var"

	"$exe" -e 4pR "$@" > /dev/null

	checktest_retcode "$d" "$?" "environment var"
	-fi

	-printf 'pass\n'
	+ printf 'pass\n'
	+
	+ set +e
	+
	+ printf 'three\n' \| head -c3 > /dev/null
	+ err=$?
	+
	+ if [ "$err" -eq 0 ]; then
	+
	+ printf 'Running dc Easter script...'
	+
	+ easter_res="$testdir/dc_outputs/easter.txt"
	+ easter_out="$testdir/dc_outputs/easter_results.txt"
	+
	+ outdir=$(dirname "$easter_out")
	+
	+ if [ ! -d "$outdir" ]; then
	+ mkdir -p "$outdir"
	+ fi
	+
	+ printf '4 April 2021\n' > "$easter_res"
	+
	+ "$testdir/dc/scripts/easter.sh" "$exe" 2021 \| head -c12 > "$easter_out"
	+ printf '\n' >> "$easter_out"
	+ err="$?"
	+
	+ checktest "$d" "$err" "Easter script" "$easter_res" "$easter_out"
	+
	+ printf 'pass\n'
	+ fi
	+
	+fi

	out1="$testdir/../.log_$d.txt"
	out2="$testdir/../.log_${d}_test.txt"

	printf 'Running %s line length tests...' "$d"

	printf '%s\n' "$numres" > "$out1"

	export "$line_var"=80
	printf '%s\n' "$num" \| "$exe" "$@" > "$out2"

	checktest "$d" "$?" "environment var" "$out1" "$out2"

	printf '%s\n' "$num70" > "$out1"

	export "$line_var"=2147483647
	printf '%s\n' "$num" \| "$exe" "$@" > "$out2"

	checktest "$d" "$?" "environment var" "$out1" "$out2"

	printf 'pass\n'

	printf 'Running %s arg tests...' "$d"

	f="$testdir/$d/add.txt"
	exprs=$(cat "$f")
	results=$(cat "$testdir/$d/add_results.txt")

	printf '%s\n%s\n%s\n%s\n' "$results" "$results" "$results" "$results" > "$out1"

	"$exe" "$@" -e "$exprs" -f "$f" --expression "$exprs" --file "$f" -e "$halt" > "$out2"

	checktest "$d" "$?" "arg" "$out1" "$out2"

	printf '%s\n' "$halt" \| "$exe" "$@" -- "$f" "$f" "$f" "$f" > "$out2"

	checktest "$d" "$?" "arg" "$out1" "$out2"

	if [ "$d" = "bc" ]; then
	printf '%s\n' "$halt" \| "$exe" "$@" -i > /dev/null 2>&1
	fi

	printf '%s\n' "$halt" \| "$exe" "$@" -h > /dev/null
	checktest_retcode "$d" "$?" "arg"
	printf '%s\n' "$halt" \| "$exe" "$@" -P > /dev/null
	checktest_retcode "$d" "$?" "arg"
	printf '%s\n' "$halt" \| "$exe" "$@" -v > /dev/null
	checktest_retcode "$d" "$?" "arg"
	printf '%s\n' "$halt" \| "$exe" "$@" -V > /dev/null
	checktest_retcode "$d" "$?" "arg"

	"$exe" "$@" -f "saotehasotnehasthistohntnsahxstnhalcrgxgrlpyasxtsaosysxsatnhoy.txt" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "invalid file argument" "$out2" "$d"

	"$exe" "$@" "-$opt" -e "$exprs" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "invalid option argument" "$out2" "$d"

	"$exe" "$@" "--$lopt" -e "$exprs" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "invalid long option argument" "$out2" "$d"

	"$exe" "$@" "-u" -e "$exprs" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "unrecognized option argument" "$out2" "$d"

	"$exe" "$@" "--uniform" -e "$exprs" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "unrecognized long option argument" "$out2" "$d"

	"$exe" "$@" -f > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "missing required argument to short option" "$out2" "$d"

	"$exe" "$@" --file > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "missing required argument to long option" "$out2" "$d"

	"$exe" "$@" --version=5 > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "given argument to long option with no argument" "$out2" "$d"

	printf 'pass\n'

	printf 'Running %s directory test...' "$d"

	"$exe" "$@" "$testdir" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "directory" "$out2" "$d"

	printf 'pass\n'

	printf 'Running %s binary file test...' "$d"

	bin="/bin/sh"

	"$exe" "$@" "$bin" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "binary file" "$out2" "$d"

	printf 'pass\n'

	printf 'Running %s binary stdin test...' "$d"

	cat "$bin" \| "$exe" "$@" > /dev/null 2> "$out2"
	err="$?"

	checkerrtest "$d" "$err" "binary stdin" "$out2" "$d"

	printf 'pass\n'

	if [ "$d" = "bc" ]; then

	printf 'Running %s limits tests...' "$d"
	printf 'limits\n' \| "$exe" "$@" > "$out2" /dev/null 2>&1

	checktest_retcode "$d" "$?" "limits"

	if [ ! -s "$out2" ]; then
	err_exit "$d did not produce output on the limits test" 1
	fi

	exec printf 'pass\n'

	fi
	diff --git a/usr.bin/gh-bc/Makefile b/usr.bin/gh-bc/Makefile
	index 79526628cf61..7b06f310a33c 100644
	--- a/usr.bin/gh-bc/Makefile
	+++ b/usr.bin/gh-bc/Makefile
	@@ -1,116 +1,114 @@
	# $FreeBSD$

	.include <src.opts.mk>

	PROG= gh-bc
	PROGNAME= bc

	BCDIR= ${SRCTOP}/contrib/${PROGNAME}
	-BCVERSION!= sed -n -e '/.VERSION = [0-9]/s/.VERSION = //p' ${BCDIR}/Makefile.in

	SRCS= args.c data.c file.c lang.c lex.c main.c num.c parse.c program.c read.c vector.c vm.c
	SRCS+= bc.c bc_lex.c bc_parse.c dc.c dc_lex.c dc_parse.c history.c library.c
	SRCS+= bc_help.c dc_help.c lib.c lib2.c opt.c rand.c
	MAN= bc.1 dc.1

	LINKS= ${BINDIR}/bc ${BINDIR}/dc

	.PATH: ${BCDIR}/src ${BCDIR}/gen ${BCDIR}/manuals ${.OBJDIR}

	CATALOGS= en_US.UTF-8
	CATALOGS+= de_DE.UTF-8 de_DE.ISO8859-1
	CATALOGS+= es_ES.UTF-8 es_ES.ISO8859-1
	CATALOGS+= fr_FR.UTF-8 fr_FR.ISO8859-1
	CATALOGS+= ja_JP.UTF-8 ja_JP.eucJP
	CATALOGS+= nl_NL.UTF-8 nl_NL.ISO8859-1
	CATALOGS+= pl_PL.UTF-8 pl_PL.ISO8859-2
	CATALOGS+= pt_PT.UTF-8 pt_PT.ISO8859-1
	CATALOGS+= ru_RU.UTF-8 ru_RU.ISO8859-5 ru_RU.CP1251 ru_RU.CP866 ru_RU.KOI8-R
	CATALOGS+= zh_CN.UTF-8 zh_CN.eucCN zh_CN.GB18030 zh_CN.GB2312 zh_CN.GBK

	NLSNAME= bc
	NLSSRCDIR= ${BCDIR}/locales

	CFLAGS+= -DMAINEXEC=${PROGNAME}
	CFLAGS+= -DNLSPATH=/usr/share/nls/%L/%N.cat
	CFLAGS+= -DBC_ENABLED
	CFLAGS+= -DBC_ENABLE_PROMPT
	CFLAGS+= -DBC_ENABLE_LONG_OPTIONS
	CFLAGS+= -DBC_ENABLE_EXTRA_MATH
	CFLAGS+= -DBC_ENABLE_HISTORY
	CFLAGS+= -DBC_ENABLE_RAND
	CFLAGS+= -DDC_ENABLED
	CFLAGS+= -DNDEBUG
	-CFLAGS+= -DVERSION=${BCVERSION}
	CFLAGS+= -I${BCDIR}/include

	.if ${MK_NLS_CATALOGS} == "no"
	CFLAGS+= -DBC_ENABLE_NLS=0
	MAN_SRC_BC= bc/N.1
	MAN_SRC_DC= dc/N.1
	.else
	CFLAGS+= -DBC_ENABLE_NLS=1
	MAN_SRC_BC= bc/A.1
	MAN_SRC_DC= dc/A.1

	# prevent floating point incompatibilities caused by -flto on some architectures
	.if ${MACHINE_ARCH} != mips && ${MACHINE_ARCH} != mips64 && \
	${MACHINE_ARCH} != powerpc64 && ${MACHINE_ARCH} != riscv64
	CFLAGS+= -flto
	.endif

	HAS_TESTS=
	SUBDIR.${MK_TESTS}+= tests

	.for catalog in ${CATALOGS}
	NLS+= ${catalog:C/.*://}
	NLSSRCFILES_${catalog:C/.://}= ${catalog:C/.://}.msg
	.endfor

	NLSLINKS_en_US.UTF-8+= en_AU.UTF-8 en_CA.UTF-8 en_GB.UTF-8 en_IE.UTF-8 \
	en_NZ.UTF-8 C
	NLSLINKS_en_US.UTF-8+= en_AU.US-ASCII en_CA.US-ASCII en_GB.US-ASCII \
	en_NZ.US-ASCII
	NLSLINKS_en_US.UTF-8+= en_AU.ISO8859-1 en_CA.ISO8859-1 en_GB.ISO8859-1 \
	en_NZ.ISO8859-1 en_US.ISO8859-1
	NLSLINKS_en_US.UTF-8+= en_AU.ISO8859-15 en_CA.ISO8859-15 en_GB.ISO8859-15 \
	en_NZ.ISO8859-15 en_US.ISO8859-15

	NLSLINKS_de_DE.UTF-8+= de_AT.UTF-8 de_CH.UTF-8
	NLSLINKS_de_DE.ISO8859-1+= de_AT.ISO8859-1 de_CH.ISO8859-1
	NLSLINKS_de_DE.ISO8859-1+= de_AT.ISO8859-15 de_CH.ISO8859-15 de_DE.ISO8859-15

	NLSLINKS_es_ES.ISO8859-1+= es_ES.ISO8859-15

	NLSLINKS_fr_FR.UTF-8+= fr_BE.UTF-8 fr_CA.UTF-8 fr_CH.UTF-8
	NLSLINKS_fr_FR.ISO8859-1+= fr_BE.ISO8859-1 fr_CA.ISO8859-1 fr_CH.ISO8859-1
	NLSLINKS_fr_FR.ISO8859-1+= fr_BE.ISO8859-15 fr_CA.ISO8859-15 fr_CH.ISO8859-15 \
	fr_FR.ISO8859-15

	NLSLINKS_nl_NL.ISO8859-1+= nl_BE.ISO8859-1
	NLSLINKS_nl_NL.ISO8859-1+= nl_BE.ISO8859-15 nl_NL.ISO8859-15

	NLSLINKS_pt_PT.UTF-8+= pt_BR.UTF-8
	NLSLINKS_pt_PT.ISO8859-1+= pt_BR.ISO8859-1
	NLSLINKS_pt_PT.ISO8859-1+= pt_PT.ISO8859-15
	.endif

	lib.c: lib.bc Makefile
	cd ${BCDIR} && sh gen/strgen.sh gen/lib.bc ${.OBJDIR}/lib.c bc_lib bc_lib_name 1 1

	lib2.c: lib2.bc Makefile
	cd ${BCDIR} && sh gen/strgen.sh gen/lib2.bc ${.OBJDIR}/lib2.c bc_lib2 bc_lib2_name 1 1

	bc_help.c: bc_help.txt Makefile
	cd ${BCDIR} && sh gen/strgen.sh gen/bc_help.txt ${.OBJDIR}/bc_help.c bc_help

	dc_help.c: dc_help.txt Makefile
	cd ${BCDIR} && sh gen/strgen.sh gen/dc_help.txt ${.OBJDIR}/dc_help.c dc_help

	bc.1:
	${CP} ${BCDIR}/manuals/${MAN_SRC_BC} ${.OBJDIR}/bc.1

	dc.1:
	${CP} ${BCDIR}/manuals/${MAN_SRC_DC} ${.OBJDIR}/dc.1

	.include <bsd.prog.mk>

File Metadata

Mime Type: application/octet-stream
Expires: Tue, May 21, 5:15 PM (1 d, 23 h)
Storage Engine: chunks
Storage Format: Chunks
Storage Handle: PfScbO6FXvs7
Default Alt Text: (4 MB)

Offset	End	Complete
0	4194304	Yes
4194304	4564452	Yes

No OneTemporaryActions

View Options

File Metadata

Event Timeline

No OneTemporary
Actions